This has happened multiple times on multiple occasions, but it has never been this bad. The following screenshots were taken within a minute of each other.

XX:15 ^

XX:16 ^

XX:17 ^

((My browser is Safari, and I recently got a new computer. The same thing that has happened here happened with my old computer too))

Is this only happening on the Lucky Draw page?

Does this happen randomly while playing? Or only after taking a certain action while playing? Can you reproduce this on demand? If so, what are the step to reproduce it?

Have you tried using a different browser to see if it's specific to Safari?

Are you using any type of popup blocker that may be tampering with the page? Can you try disabling it to see if that helps?

This happens to me all the time when I'm playing on my phone on Safari, but not on my laptop on Chrome.

It'll happen randomly, but I notice an increase when I'm trying to nurture pets. I believe repeated fast actions are what causes it, or at least makes it worse. Maybe that's why it happens the most when I nurture pets or when you draw cards.

I personally don't believe I have any blockers enabled.

1. No. It has happened in multiple pages. I took a few videos of me going through the Nurturing Grounds, as it seems to be happening in the spaces with lots of buttons.
(Admittedly, that is a lot of places-)

2. It happens randomly while playing. I never know when it will happen it just does.
The videos from me trying to make it pop up on the nurturing grounds can be found here. I will keep adding more to this if it occurs somewhere else. My theory is that it might have to do with server load and the amount of people on the site?

3. I have not yet tried a different browser. Once sending this post through, I will try on Google.

4. As far as I am aware, I dont have a popup blocker. However, the site where I view online versions of my text books will tell you otherwise:


Popup tabs work on other sites that I am on without an issue :)

Hm. Thank you for all of that information. That is very strange.

I am not seeing any PHP related errors, so it's not breaking on the backend.

Basically, whenever you see that popup "Something went wrong" error, it's from an AJAX request failing. I use AJAX requests all throughout the site to basically update a static page with something new without requiring the user to actually reload the page. You make an AJAX call to another page, get the results, then replace something on the loaded page with those results. That's how I can make pages feel like they are reactive, but it's essentially just all static HTML.

Since this seems to only be an issue with Safari, there must be some weird issue with how I run AJAX calls and with how Safari processes them. In one of your videos, you load the page and hit search and it immediately errors out. This should be completely impossible. Pressing that button just sends a simple AJAX request to another file to parse the search - there's nothing contingent on anything else. As soon as the page loads, you should be able to press that button w/o any issues.

So, my best guess, is that there's something with Safari where it literally cannot load an additional HTTP request if it's still in the middle of processing another HTTP request and for some reason, Safari is being very slow processing them at random times for random reasons. In other words, when you load the Nurturing Grounds page and click the search button, it's trying to create a new HTTP request via AJAX to load the pets to nurture. However, Safari is going, "Hey, we already have an open HTTP request with this site, I'm not going to allow another." Therefore, the AJAX call fails and then you get that "Something went wrong." error.

Without knowing more information or figuring out the exact mechanism, that is unfortunately my best guess of what's happening. I can try and dig deeper when I have time, but there's unfortunately nothing more specific I can gather that will tell me exactly what the problem is - I'm just gonna have to try and research it on the internet and see if it's a known issue with known solutions.