Description of the Bug: I tried to update to the most recent version 3.6.1 but in the Play Store it got stuck on the “installing” part. I restarted my tablet, tried updating again, it worked, hit open and then it closed immediately after startup (didn’t get an error message or anything at all). I proceeded then to uninstall and reinstall the game, opened it back up took a long time to get to the “Player initialization” screen and got stuck on 33%. Ever since I haven’t been able to get past that loading screen even after clearing cache, restarting the game multiple times and uninstalling/reinstalling it again.
Steps to Reproduce:
Open the game
Gets to the “Player initialization” screen and loads up to 17% then to 33% and stays like that forever.
Screenshots or Videos (if available): (I don’t see the option to upload a video)
Some context: Back when I played on iOS I also installed the game in my Windows laptop and logged in using my Google Play Games profile (but only played once and left it forgotten). I recently switched from iOS to an Android device (which has the same Google account I used on the Windows game) and I also had the same issue because I still had the game installed on my iPhone. I solved it by uninstalling it from there.
When I downloaded update 3.6.1 it logged me out for some reason, I tried to log back in and that’s when I got stuck in that loading screen, then I remembered about the Windows game using my Google Play Games profile, so I opened it there, unlinked the Play Games profile and then uninstalled it. That’s how I fixed it.
Long story short: I was using the same Google Play Games on two different devices for the same game.
I’ve seen similar loading issues after updates, especially when the game data doesn’t fully sync after installation. Since you already tried reinstalling and clearing cache, I’d suggest checking if Google Play Games is updated, make sure you have enough free storage, and try switching between Wi-Fi once during the initialization step. If it still freezes at 33%, it’s likely a server-side or compatibility issue with Android 16/Snapdragon 8 Gen 3, so reporting it with your device details would help the developers track it down.
Bug Report
