Google Sign in Not Working After Publishing in Play Store

Google sign in not working after publishing in play store

When you upload an apk to the play store then play store creates a new SHA1 key called "App signing certificate". You get that SHA1 and save in your console or firebase account (as you need).

New SHA1 will be found at Released Management->App Sigining on your play console.

[]

Google Sign In Service not working after publish on PlayStore

I fixed this problem, Firstly i downloaded my apk from play store and i unzip my apk and checked my SHA, and i saw Play Store used App-Signing cert SHA. but i used Upload-Cert SHA everywhere.

after i changed my API sha to Play Store App-Signing SHA, worked perfectly.

Google Sign In not working after published in playstore

This is due to different SHA1 keys for debug and release version.

The thing is that for google sign in you must add SHA1 key in your google account which you can get from programming or from command prompt.

SHA1 key is different for signed apk. So you have two SHA1, one each for debug and release version. The SHA1 for release version can be obtained from keystore file.

if you want to read more about this you can check this link. It is very well explained there.

Google sign in does not work for app when uploaded to Play Store

Here is the answer for why you can't see the Google Map.

I recently Upload the APK on Google Play store and I faced the same issue after checking the Play Console I found the solution for this problem.

Their is no problem with your key but the problem is with your SHA-1. You signed your APK with your SHA-1 that is fine and then upload the APK it also fine.

But as per the new update for Play Console when you signed your APK with SHA-1 and upload the APK it only signed by you but as per the new update it is also signed by Google Play for more security. Have a look here some part of Google Play section:

With Google Play App Signing: You sign your app with your upload key.
Then, Google verifies and removes the upload key signature. Finally,
Google re-signs the app with the original app signing key you provided
and delivers your app to the user.

You can refer Documentation here.

Now, The Answer of your question is After successfully upload the APK you can see that in the section with Two SHA-1 the 1st SHA-1 is Google created its own and 2nd SHA-1 is its yours.

So just copy the Google SHA-1 and paste it to your console where you generate the Google Map API Key.

Google Sign in not working from app downloaded from playstore

Solution:

• The problem was that while generating the google-services.json, the App signing certificate SHA-1 certificate fingerprint needs to be provided; I was providing the Upload certificate's SHA-1 certificate fingerprint which is why it wouldn't work on production.
• In essence, in the credentials page, you'll need to create a two oauth client ids for Android (one with the App Signing certificate and one with the Upload certificate and one oauth client id of type web and in while using react-native-google-signin you need to specify the webClientId.

---

Related Topics