Why Google Play Games Authentication So Inconsistent on 0.11.01 version?

I have been working on Authentication System like 2 months now. It is a complete nightmare. First i started to work with Google Play Games Plugin version 0.11.01 and I followed this sites:

I created Google App from Google Play Console. I was going to use only “Internal Testing” first that’s why i did not filled some information and directly started with Configuration settings and it redirected me to Google Cloud Platform.

I created OAuth consent screen,

  • External

  • Gave a name, Entered Supported Email

  • Add Scopes: Google Play Game Services → /auth/games , auth/games_lite , auth/drive.appdata

  • Added my Testers

Created My Credentials: Web and Android.

For android one i created a new Unity project and created a keystore, get my SHA1 key. Added to Android Credentials also configured Package name and added to Android Credentials settings.

After i finish with Cloud Settings i returned to Configuration settings on Google Play Console. Added Credentials and Got Resources from there.

I switch my project to Android, After that i added version 0.11.01 Google Play Games Plugin. I configured my settings from Window → Google Play Games → Setup → Android Setup, Resources and Web Client ID. Also configured the nearby settings.

In Unity Cloud i created my App, link it with my project, Downloaded Authentication 3.3.0 package created a provider for Google Play games, gave it Web settings.
For the code i used Offical Authentication With Google Play Games .

Only change i made i don’t want Auto Authenticate for my app just yet, that’s why i used ManuallyAuthenticate method from PlayGamesPlatform and added to my Button.

After i configured everything i created .aab file with symbol.zip. Uploaded to Internal testing and Added my Testers There.

Because i was using internal testing i went to App Signing page On Google Play Console i got google SHA1 key and Change my Android Credential from Google Cloud. After i setup everything i publish my Internal test.

Okey here everything gets complicated for me. On version 0.11.01 i have 2 opposite issues. Either i cannot Authenticate or it’s authenticate itself from the app first starts. After some exprementation i found out that if don’t use Grow → Play Games Services → Testers it’s not let my Testers to Authenticate. If i add my testers here it can Authenticate but its do it automatically. Even if I did not write any code for authentication, it still authenticate itself.

What i want is the middle. In my game if someone want to Authenticate, They have to do it themselfs. When someone pressed the Login button it should Authenticate my player, otherwise what’s the point about testing? Also how can i understand is it working or not?

Does this Automatic Authentication intended behaviour ? Is it going to be this way when i published my game or behavior is different?

No Reply yet?

First, google have made that package and they just don’t try to maintain it so it stuck

Second, if I remember it right, your problem is not solvable. Google Play Games signin api don’t allow changing account. It is the lightweight authentication linked with the play store running in the background and to change the account you then need to change it at playstore or google games app

The behaviour you want are more likely possible with Google SignIn package and system