Google Play Game Services login issues

Solar2D General Questions/Discussion
#81

Hi funkyvisions, 

               how you get rid of this error. how your SHA1 are matched. when i used production/release key it create the apk successfully. when i extract the file from using this command

unzip YourGame.apk 

keytool -printcert -file META-INF/CERT.RSA

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

CERT.RSA file not create in corona apk so my SHA1 not match so therefore i face the problem the sign-in problem i think so you also face the same problem of SHA1. if you have any solution about this problem please help me

w8 for your reply

#82

A big THX to Naomi

it works now (my fault was that the app name and the keystore was not the same). sometime fingers are faster than the brain!

for all, if you like to restart the  OAuth2 procedure the only way i found, was to delete the app in the google play game service and recreate a new entry with all the parameters, copy the new ID to your build.settings and make a new version.

Michael

#83

Does it work for everyone now? Thought I’d share the lessons I learned in case it helps anyone else. I didn’t read everything above so I hope I’m not boring people. Anyway lessons learned:

  1. Like someone mentioned: the client ID is ALWAYS incorrect the first time you link a game on the google play dev console. you can see the error if you go to the api console. It will be stated like this the first time:

XXXXXXXXXXX.apps.googleusercontent.com

but when you remove the client ID and the linked app from the dev console and redo the process again the api console will show a client ID in the following format instead:

XXXXXXXXXXX-YYYYYYYYYYYYYYYYYYYYYYYYYYYY.apps.googleusercontent.com instead. Stupid bug Google…!

Well, now it will work! Unless:

  1. If you tried to sign-in when it was incorrectly configured like above, the phone will remember that in the cache for your app. Go to application management and clear the data/cache for your app and it will try to re-sign-in next time.

Hope this helps someone! I spent the better part of this day to get this to work. Finally got the plugin sample going just a few minutes ago!

#84

Hey, @benny5, about the client ID, I have one of my apps with XXXXXXXXXXX.apps.googleusercontent.com, and it has no issue signing in.  So the first client ID would not be always be incorrect.  I think there was something else that caused the client ID not to work right the first time you created one, but the second one was generated correctly.

When I linked my first app, it had issue with client ID and I had to go through cleaning process, and for that app, the client ID looks like XXXXXXXXXXX-YYYYYYYYYYYYYYYYYYYYYYYYYYYY.apps.googleusercontent.com, but for my second app (which is a separate product and has its own GPGS set up), the client ID looks like XXXXXXXXXXX.apps.googleusercontent.com, and that’s the first client ID I created for this app.

Naomi

#85

Hey Naomi,

That’s interesting. I made a second game and managed to login with the simpler type of client ID as well. I have no idea what’s going on. But both seem to work under certain conditions.

#86

Has anyone had any issues with logging out and back into Google Game Services a second time within the same application session?  In other words I request initialization, and login and it works.  Then I log out which doesn’t have a callback.  The next time I try to initialize and login I don’t get any kind of callback.  I hooked the Android device up to ADB and didn’t see anything in the logcat.  Perhaps you can only call initialize once thus after a log out I should only log in?  Any guidance would be appreciated.

#87

Just to answer my own question here in case anyone else has a similar issue, it appears that you need to keep track locally whether or not the app has called the init on game services.  Doing so a second time simply results in the call finishing but no callback.  So init game services, login, then if you logout skip straight to login by passing init.

#88

Has anyone had any issues with logging out and back into Google Game Services a second time within the same application session?  In other words I request initialization, and login and it works.  Then I log out which doesn’t have a callback.  The next time I try to initialize and login I don’t get any kind of callback.  I hooked the Android device up to ADB and didn’t see anything in the logcat.  Perhaps you can only call initialize once thus after a log out I should only log in?  Any guidance would be appreciated.

#89

Just to answer my own question here in case anyone else has a similar issue, it appears that you need to keep track locally whether or not the app has called the init on game services.  Doing so a second time simply results in the call finishing but no callback.  So init game services, login, then if you logout skip straight to login by passing init.