google-signin: DEVELOPER_ERROR on real device

i can success login in simulator, but when i build an alpha release for google play and test it on real device i got DEVELOPER_ERROR message in logcat

i generated a signing key $ keytool -genkey -v -keystore my-release-key.keystore -alias my-key-alias -keyalg RSA -keysize 2048 -validity 10000
i generated a SHA1 key keytool -exportcert -keystore ~/.android/debug.keystore -list -v
i added SHA1 key to firebase console
i added google-services.json in my app folder
i used this code GoogleSignin.configure({ iosClientId: "xxx-xxx.apps.googleusercontent.com" });
i also generated a release key and added to firebase too - same error keytool -exportcert -list -v \ -alias <your-key-name> -keystore <path-to-production-keystore>

i miss something?

react-native@0.55.4 react-native-google-signin@1.0.0-rc1

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 19 (1 by maintainers)

Most upvoted comments

I finally found it after 2 days of hitting my head here and there 😵. Apparently google has launched new signings service where they sign your app on play store after you upload, with their key after which they give you SHA1 for the same on play store developer console. under <YOUR APP> > Release Management > App Signing take SHA-1 from there and add it to your Firebase project app. And yay! it worked for me and hopefully will work for you if you are facing same issue.

+36

iyogeshjoshi on Sep 12, 2018

@usmansbk I was facing the same issue in RN 0.60. Turns out when I was running the SHA1 generation command on my Mac, the default debug.keystore on my mac was being used. But when the React Native Android App is compiled, it takes the debug.keystore from inside the project Android Folder Screen Shot 2019-08-21 at 6 31 05 PM

I generated SHA 1 from this Keystore and added it to Firebase, and Voila ! 🎉

+18

rathoreabhijeet on Aug 21, 2019

@ajitdas123 thanks, all the keys generated running signin report was already in firebase console. still no way to resolve this

pkers87 on Jul 12, 2018

@pkers87 @vonovak faced this problem, my keys was correctly generated. I fixed it followin instructions at the bottom of android F.A.Q https://github.com/react-native-community/react-native-google-signin/blob/master/docs/android-guide.md

Yauheni-Ihnatsyeu-EPAM on Jul 30, 2019

Check this link , this might help Developer error

ajitdas123 on Jul 12, 2018

I finally found it after 2 days of hitting my head here and there 😵. Apparently google has launched new signings service where they sign your app on play store after you upload, with their key after which they give you SHA1 for the same on play store developer console. under <YOUR APP> > Release Management > App Signing take SHA-1 from there and add it to your Firebase project app. And yay! it worked for me and hopefully will work for you if you are facing same issue.

This really Helped me!!! thanks a lot!!!

allindeveloper on Jun 4, 2020

Thanks @iyogeshjoshi. You just saved me some time on this. I think it would be nice to have in android-guide.md FAQ section on point E.

markhomoki on Oct 12, 2018

Solution: Answer by @rathoreabhijeet is working. Every app has it’s own key store. So while generating hash make sure to change the path to key store.

keytool -list -v -alias androiddebugkey -keystore ~/myprojects/yourappname/android/app/debug.keystore

keytool -list -v -alias androiddebugkey -keystore path_to_your_apps_keystore

Kailash23 on Nov 22, 2019

I’m facing same problem and not able top solve it. I’m already on rc3 version of the app. Everything runs fine when I install from my dev environment. But after uploading it to store I get DEVELOPER_ERROR. I have tried everything. SHA1 have confirmed multiple time that my keys are proper. Tried with or without webClientId. Tried everything I could find and think of but still unable to resolve this error. Please help me.

P.S: This is happening only on Android, on iOS it’s working fine.

iyogeshjoshi on Sep 10, 2018