Starting about a week ago Chord Crush will not load. After the start screen it is just black on firefox. On chrome it will load but not let me log into my account. Also tried edge. None of them work.
I’ve also had this problem. If I open in a private tab and you’re not signed in chord crush loads, but as soon as I sign in, the screen goes blank, happening on mobile and desktop
Given there have been three minor releases in July, I’m guessing it’s related to that.
Sorry we are looking into why this is happening to certain users! Can you both provide some details on how you are logging in? One thing we are looking into is related to some changes Google made to Google Sign in. Are you using that?
Dave
I’m not using google sign in. Usually the start screen is there and it won’t let me click on the flashing click to start text. I logged out of hook theory and did the try chord crush for free, and it still won’t let me click on the start text. The start screen shows normal, the mouse doesn’t change when I hove over the start text.
Thanks for replying! I’m logging in with the normal “continue with hook theory” login.
Not a javascript dev, but in the debugger, just after a login, I think it’s just after the request to get-puzzle-user-notification-settings, the ion app in <div id="root"></div> div gets deleted.
The fact that it is happening after it tries to load puzzle user notification settings is a good hint.
Someone mentioned that if they are logged out and they go to one of the game screens (like crush or level up) and then log in they are are able to play. (still crashes when they go back to Home Screen at any point). Let me know if that is same behavior you are seeing (also potentially a temporary workaround while we dig into what could be happening).
If you see an error in dev console let me know. Usually white screen is related to js crash.
Dave
It looks like whatever changes that were made in 1.5.10 or 1.5.11 seems to have fixed this for me, tried on multiple devices.
No idea what caused it, but I’m not complaining that it now works!
Yep, finally was able to figure out the issue, and we pushed the fix last night. Thanks, your report greatly helped track it down!
Working again, thank you!