Google play game services - testing login results with an unknown error

Question

I followed tutorials on how to implement the services of a google game for Android, and as a result a simple google + sign appeared. I tried to somehow log in before fixing the problem. And now I can’t log in to this account, but I can if I use another.

Error with first account:

06-05 16:49:03.226: W/dqi(19754): Authentication error: Unable to respond to any of these challenges: {bearer=WWW-Authenticate: Bearer realm="https://www.google.com/accounts/AuthSubRequest", error=invalid_token} 06-05 16:49:03.226: E/Volley(19754): [4376] il.a: Unexpected response code 401 for https://www.googleapis.com/games/v1/players/115167649949168063107 06-05 16:49:03.515: W/dqi(19754): Authentication error: Unable to respond to any of these challenges: {bearer=WWW-Authenticate: Bearer realm="https://www.google.com/accounts/AuthSubRequest", error=invalid_token} 06-05 16:49:03.515: E/Volley(19754): [4376] il.a: Unexpected response code 401 for https://www.googleapis.com/games/v1/players/115167649949168063107 06-05 16:49:04.280: W/dqi(19754): Authentication error: Unable to respond to any of these challenges: {bearer=WWW-Authenticate: Bearer realm="https://www.google.com/accounts/AuthSubRequest", error=invalid_token} 06-05 16:49:04.280: E/Volley(19754): [4375] il.a: Unexpected response code 401 for https://www.googleapis.com/games/v1/players/115167649949168063107 06-05 16:49:04.593: W/dqi(19754): Authentication error: Unable to respond to any of these challenges: {bearer=WWW-Authenticate: Bearer realm="https://www.google.com/accounts/AuthSubRequest", error=invalid_token} 06-05 16:49:04.593: E/Volley(19754): [4375] il.a: Unexpected response code 401 for https://www.googleapis.com/games/v1/players/115167649949168063107 06-05 16:49:04.648: E/SignInIntentService(19754): User has not completed registration. 06-05 16:49:04.648: E/SignInIntentService(19754): aol 06-05 16:49:04.648: E/SignInIntentService(19754): at ajy.a(SourceFile:108) 06-05 16:49:04.648: E/SignInIntentService(19754): at abm.a(SourceFile:213) 06-05 16:49:04.648: E/SignInIntentService(19754): at abm.a(SourceFile:194) 06-05 16:49:04.648: E/SignInIntentService(19754): at aav.a(SourceFile:486) 06-05 16:49:04.648: E/SignInIntentService(19754): at aqu.a(SourceFile:221) 06-05 16:49:04.648: E/SignInIntentService(19754): at com.google.android.gms.games.service.GamesSignInIntentService.onHandleIntent(SourceFile:343) 06-05 16:49:04.648: E/SignInIntentService(19754): at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:65) 06-05 16:49:04.648: E/SignInIntentService(19754): at android.os.Handler.dispatchMessage(Handler.java:99) 06-05 16:49:04.648: E/SignInIntentService(19754): at android.os.Looper.loop(Looper.java:137) 06-05 16:49:04.648: E/SignInIntentService(19754): at android.os.HandlerThread.run(HandlerThread.java:60) 

The result is a small dialog box with an unknown error.

I assume that his cache is stored somewhere in this application when I allowed to use my G + account. How can I cancel this so that it works again with my first account?

Answer 1

Try navigating to the Google+ settings on your device and clear the access you gave the app. Subsequently, MANUALLY set up Google+ for your test account either through the PC / Mac web browser or through your device, and then try re-linking the application. It worked for me.

The exact steps for Samsung Galaxy S3:

Settings → Google → Google+ → Applications with Google+ Sign in → tap the application and click "Disconnect application" from the bottom.

For what it's worth, I also applied the "Delete all actions for this application" option when I deleted it.

Answer 2

I managed to get my own leaderboard in production last night. The error you are describing is what I (and judging by the other comments I saw in the bug reports on SO), and other people also came across. I found that I was not able to use the google account that I am a user in the developer console to log into it, although it is explicitly listed as a test account for the game. I tried to disable the emulator, etc., but I could never get it to work. I used a different account and I was able to register. I don’t know what the problem is with my developer console account - I also use it in Google Plus without any problems. By the way, I still cannot use my developer account in a working application using a real device.

My advice is to use a separate account for testing. Good luck

Answer 3

This problem is usually related to the problem of setting the client ID. There is probably a mismatch between setting the client ID, the name of your package, and the certificate that you use to sign the application. In any case, follow our troubleshooting steps step by step, and this should lead you to a solution:

https://developers.google.com/games/services/android/troubleshooting.html