Google-signin: Clarification on how to configure keystore?

[ElixirMike]

I'm trying to follow the configure steps, but am confused on how to setup the keystore.
I have it configured such that when I click the "sign with google" button, it works and I can select my google account. But when I click to continue, it throws a "DEVELOPER ERROR". From reading threads, people say this is most likely due to issues setting up the SHA1 hash.

This is where I'm confused. In the docs, it mentions using the keytool to generate your own keystore. They refer to this guide: https://facebook.github.io/react-native/docs/signed-apk-android.html . I followed these instructions and created the 'my-upload-key.keystore" file and put it in the /android/app folder, as well as updated the gradle.properties per the article.

However, in the setup process, it then says "You can use your debug keystore's SHA1 hash, get it by running this command inside $ROOT/android" .

keytool -exportcert -keystore ~/.android/debug.keystore -list -v

I don't have a file, calld "debug.keystore" . so this command fails, I assume what it wants me to do is run this command for the "my-upload-key.keystore" file , which I did.

This generated a SHA-1 hash, which I copied into my firebase project, and downloaded the google-services.json file.

At the end of this section, it then talks about the "WebClientID" ?? I have no idea if I need to use this? Where do I use it?

Any help is appreciated ...just need a bit more detailed steps in getting this keystore configured I think.

[vaibsshukla]

This might help you with keystore.
https://stackoverflow.com/questions/27609442/how-to-get-the-sha-1-fingerprint-certificate-in-android-studio-for-debug-mode

[allthetime]

This might help you with keystore.
https://stackoverflow.com/questions/27609442/how-to-get-the-sha-1-fingerprint-certificate-in-android-studio-for-debug-mode

This is not his issue. He stated that he got both the release and debug keystore and added it to firebase.

I am having the same issue. I have all my keystores in firebase, and things like notifications work, but Sign In does not.

The incredibly opaque DEVELOPER_ERROR is incredibly unhelpful.

[usmansbk]

Also getting this error after upgrading RN from 0.58 to 0.60.4. I have both debug and release keystore added to firebase and OAuth clientId.

UPDATE
turns out my _app/build.gradle_ was missing
implementation "com.android.support:appcompat-v7:${rootProject.ext.supportLibVersion}"
dependency

[tboulis]

Im having the sam problem. All SHA1 key on firebase, tried all webclientIDs and still gettings this useless DEVELOPER_ERROR.
This error needs to be more detailed imo

[reidkersey]

I wanted to add my 2 cents. I thought I had everything setup correctly, then I realized I had a file called debug.keystore in my android/app folder.

I used the command keytool -list -v -keystore C:\Users\reidk\Documents\Git\Pr ojectR\android\app\debug.keystore -alias androiddebugkey -storepass android -keypass android to read the sha1 key from the react-native debug keystore. Then I added that to firebase, and now everything works great!

[aashishgaikwad]

Hey, @tboulis did you get rid of that DEVELOPER_ERROR?

[tboulis]

@aashishgaikwad Yes, I finally fixed it. The problem was that the packageName didn't match the app name on Firebase. It was com.company.appName vs com.appName. Hope this helps

[aashishgaikwad]

@tboulis thank you for replying. In my case, package names are same on both sides. I have added SHA1 key in firebase console. As signIn was working fine in my app when I was using earlier version of react-native-google-signin. I have upgraded it to 2.0.0 and it's throwing me this error: 'DEVELOPER_ERROR'.

[tboulis]

@aashishgaikwad I'm not sure what the problem is, but if I were you I would check if both the SHA1 of the keystores(if you use one for dev and one for prod) are on firebase. DEVELOPER_ERROR is google-side triggered so it is definitely a misconfiguration. I would also try with a new firebase app

[vonovak]

I have improved the docs. Please take a look and let me know if that helps.

[martinzokov]

I'm was still having issues with that while writing this comment to complain. However, writing it I made a list of all steps I tried and noticed I missed one of them 😆 After that it worked.

The steps I tried are:

1. Generated new keystore (when you check out the repo there's a debug.keystore file in android\app but have a go at creating your own anyway). Also, this claims that Google is picky about the debug keystore details so follow it closely
2. Got the SHA1 key from the new debug.keystore
3. Added the SHA1 to Firebase
4. Downloaded the new google-services.json
5. Double checked package name is same on Firebase and my app
6. Double checked that the webClientId matches the one from the newly downloaded google-services.json

I hope that helps

[tboulis]

@martinzokov The trickier step is 5. This was my problem (as i mentioned above) and it took me a week to figure it out. Good job writing those down!

[makx]

i had the problem of the package name. Please add it to the troubleshooting. Thanks!