So today I set up Play Games services in the developer console and inside of my game.
I made sure all the SHA1 match, and I double-checked that I was using the SHA1 from the app signing certificate, instead of the one from the keystore I created.
However, when I call the sign in after starting the game, it loads for a second and then just automatically closes itself without signing in. The debug message says “Cancelled, saving this to a shared pref”.
Further attempts to sign in also fail in a similar way, with the SignInStatus being “Canceled” everytime.
Does anyone run into the same issues? I have been trying for hours and honestly I have no clue what’s going on.:(:(
Currently it’s in testing status. Is it only usable by me during this stage? The console shows that I need to do a bunch of things and wait for a few weeks before verifying and publishing the consent screen.
So I tried with a couple of different accounts and all of them sign in completely fine, even if they are not in the test users list of the OAuth consent. I think it’s weird since the play game service now sign in automatically, and the consent screen is not even shown during the process. But they still requires the developers to set it up in order for the service to work.
I totally get it. We have seen numerous cases where we were in a dilemma if really setting up OAuth consent worked or it took time for SHA fingerprint to propagate
Anyways, glad it’s working for you. Hope we find a proper answer for this or at-least a log message about consent missing makes sense too when signin fails!