Alright, as a Google Play Games user, yep, I used my Google Play Games account to log in to the game (Shattered Pixel Dungeon v2.4.2), but I have encountered some errors related to the game and Google Play Games. Even though I have successfully fixed all of these errors, I am still writing this post in the hope that the cause can be found and fixed, so that they do not happen again in the future.

The first time the error occurred it was related to a synchronization (sync) issue. I can’t sync the game with my main Google Play Games account, I can only do this with my sub account, but at least when I successfully sync the game with a second device (using my sub account) and then log in to the main account, I can sync the game with the main account.

The second time the error occurred, the game keeps crashing whenever I open the game. It always happens if I log in to the game with my main account (but this didn’t happen with my sub account). To fix this error, I had to delete all game data on my main Google Play Games account and then log back into the game…

I don’t know if anyone else has had the same problem as me, but hopefully these errors can be fixed in the future…

  • NoHorizons@lemmy.worldOP
    link
    fedilink
    English
    arrow-up
    1
    ·
    11 days ago

    First, please note that the “accounts” I’m referring to in the article are Google Play Games accounts. I’m playing v2.4.2, and… no, this error is definitely not related to attempting to revert back to a non-beta version. I have reverted back, but nothing happened for a long time. This error happened in a random date later that. The game will and only crashes if I log in to the game with my main account, but this doesn’t happen with my sub account or when I log out. It seems like there is some kind of conflict between the game and Google Play Games.

    • 00-Evan@lemmy.worldM
      link
      fedilink
      English
      arrow-up
      2
      ·
      11 days ago

      From looking at my automated crash reports, I do see where this is happening and I’m afraid it is being caused by having sync data from a future version of the game. I’ll get this fixed in the next update, unfortunately there isn’t a way for me to retroactively fix v2.4.2