0

I have this app which uses Google Services json file configured with a SHA1 of a debug key, and then build the Signed Build with a new key and used that release.apk to install the app. But the sign in part isn't working now in the release version of the app.

So now my question is, should the Google services json file be configured using the SHA1 of the signed key?? Ignore the formatting since I'm using this from mobile.

burglarhobbit
  • 1,860
  • 2
  • 17
  • 32

1 Answers1

1

Based on the document: Setting Up Google Play Games Services

Specify client ID settings

You should create two client IDs, one with the release certificate fingerprint and another with the debug certificate fingerprint. Make sure to use the same package name for both. This allows Google Play games services to recognize calls from your linked APKs that are signed with either certificate. For more information about certificate signing for Android, see Signing Your Application.

Check this SO post, it talked about the difference of the clientID for debug and release version. Lastly, check the documents : Prepare for Release and Sign Your App for a detailed instruction of preparing your app for release.

Community
  • 1
  • 1
Mr.Rebot
  • 6,703
  • 2
  • 16
  • 91
  • Thank You, I managed to overcome that by adding the SHA-1 of my release version key to my current google services portal thing and downloaded the updated json file. Username checks out though ;) – burglarhobbit Feb 10 '17 at 09:53