8
votes

I have a problem with google sign in on production installation file. On debug installation everything is normal I can login into the application. But after changed on release i get null on account from google response. What could have been problem?

I worked with ("https://developers.google.com/identity/sign-in/android/start-integrating"). every step same.

2
you need to have a configuration file with sha-1 key of release key, so only it will work on release build - Madhur
@Madhur is it compulsary to get configuration file and add it to app folder. It seems that there is no need of it for launching app. - عثمان غني
nope but Google sign in won't work without that config file - Madhur

2 Answers

7
votes

I know this is an old question, but for anyone using Firebase, you have to add the SHA-1 fingerprint to the Firebase Console > Settings > Android App page.

If you are using the Google Play Console, you can get this from the Google Play Console > App Signing page. There will be two of them (the one you signed your app with, and the one that Google signed your app with). You'll need to add both so you can test local release builds.

If you don't use the Play Store, you'll need to get the SHA-1 fingerprint from your keystore file using these directions: https://developers.google.com/android/guides/client-auth

2
votes

You need to have a configuration file with,

Android Signing Certificate SHA-1 with release key so only it will work with release build