[Android] DEVELOPER_ERROR with code 10

[rsuubinn]

I use React Native cli. I followed setting in this documentation. (https://react-native-google-signin.github.io/docs/setting-up/android)

• android/build.gradle

• android/app/build.gradle

• debug, release, signing keys

I registered all three keys in Firebase. I registered the key in firebase and placed the google-service.json file inside android/app folder.

• Web Client ID

• My google signin Codes

It works fine in debug or release mode without any problems. However, I face this problem when I generate .aab file and run this app released on the Play Store and try to log in with Google.

Environment

"react-native": "0.72.5" "@react-native-google-signin/google-signin": "^10.1.1" node: v18.17.1

[rboy0509]

i have same problem but with expo . My response : {"nativeStackAndroid":[],"userInfo":null,"message":"DEVELOPER_ERROR","code":"10"}

[vonovak]

Hello and thanks for asking, DEVELOPER_ERROR is always a configuration mismatch. Please see the instructions here https://react-native-google-signin.github.io/docs/troubleshooting#google-login-does-not-work-when-downloading-my-app-from-the-play-store

Thank you 🙂

[rsuubinn]

i have same problem but with expo . My response : {"nativeStackAndroid":[],"userInfo":null,"message":"DEVELOPER_ERROR","code":"10"}

Have you ever had your app signing key reissued? After looking through the registered issues, I finally found a solution. Go to the google play console, sort the app signing key into legacy rather than the latest, and then register the SHA-1 fingerprint of the app signing key that appears in firebase. This was of great help to me.

@vonovak I wonder if I need to register a legacy key rather than the issued key. I think this part is wrong.

[bweston92]

Getting the same, checked SHA1 fingerprint of the APK and package name and all match Firebase.

[SnowingFox]

i have same problem but with expo . My response : {"nativeStackAndroid":[],"userInfo":null,"message":"DEVELOPER_ERROR","code":"10"}

have you solve this problem？

[utyfua]

If you are using firebase you actually need to add google as Sign-in method in Firebase itself (Build -> Authentication -> Sign-in method, see screenshot below). If you have already created an app already you will be prompt for fingerprints and after you will get a new google-services.json which you need to use in your app instead of old one.

If this was helpful, please let everyone know about. If I was not only me I will try to bring this to the documentation.

[bweston92]

@utyfua this is exactly what resolved it for me.

[cliffgor]

I am getting developer Error when doing internal testing for my Android app. i followed the instructions of using my playstore signin key on firebase but the issue still persists

[cliffgor]

Thanks @rsuubinn Your solution for using the legacy key works, I don't know if @vonovak would have an update for this fix or add it to the documentation

[rsuubinn]

Thanks @rsuubinn Your solution for using the legacy key works, I don't know if @vonovak would have an update for this fix or add it to the documentation

I'm glad it helped you. Have a nice day!

[katwal-dipak]

Hello and thanks for asking, DEVELOPER_ERROR is always a configuration mismatch. Please see the instructions here https://react-native-google-signin.github.io/docs/troubleshooting#google-login-does-not-work-when-downloading-my-app-from-the-play-store

Thank you 🙂

DEVELOPER_ERROR with code 10 in android with .aab file. Though it works fine with apk file. I am in v 14.0.0 and I am not using firebase for google signIn. I am using SHA-1 certificate fingerprint from google play setup > App signing.

It seems SHA-1 certificate fingerprint from upload-key always throws this error (only with .aab file), but works fine with production SHA-1 certificate fingerprint

[phuocantd]

Hello and thanks for asking, DEVELOPER_ERROR is always a configuration mismatch. Please see the instructions here https://react-native-google-signin.github.io/docs/troubleshooting#google-login-does-not-work-when-downloading-my-app-from-the-play-store Thank you 🙂

DEVELOPER_ERROR with code 10 in android with .aab file. Though it works fine with apk file. I am in v 14.0.0 and I am not using firebase for google signIn. I am using SHA-1 certificate fingerprint from google play setup > App signing.

It seems SHA-1 certificate fingerprint from upload-key always throws this error (only with .aab file), but works fine with production SHA-1 certificate fingerprint

same here, It work in debug and apk but when I upload aab then error with DEVELOPER_ERROR

[bzliu94]

Able to deal with this with Expo by making sure app.json android.package_name matches package name at Google Console for a OAuth 2.0 Client ID credential record (for Android).