Error-10 DEVELOPER_ERROR

[saadraj4]

I am getting Error-10 DEVELOPER ERROR, even though all the configurations are correct

[aliffarisqi]

@saadraj4 i have the same issue, in my case I have Developer Error alert when sign in by google in my apps after build aab and uploaded to internal testing google console, while in simulator and build release apk run successfully, I don't know what the problem

[saadraj4]

have you distributed it to google play console internal testing ?

No I haven't. I done this for locally. Soon I'll publish it on google play, then see what happens

[aliffarisqi]

okay bro, thank you for your response, good luck for you

[saadraj4]

Thanks and Welcome

[GowthamResbee]

Firebase google-services.json contains multiple client IDs — but for AAB builds, Firebase alone isn’t enough. You must register and configure the correct OAuth Client ID in Google Cloud Console, tied to your Play App Signing SHA-1.

Solution:

If you're using @react-native-google-signin/google-signin with Firebase Auth in a React Native app and it's only failing on AAB builds (production), here's what worked for me:

Key Fix:
For Debug Builds/Local Testing: (May not work for others)
Use the client ID with "client_type": 3 from your google-services.json.

For Production (AAB Build):

You must use the OAuth 2.0 Web Client ID created in Google Cloud Console, not the Android client ID.

If you don’t already have a matching Web Client ID:

Go to Google Cloud Console

Create a new OAuth 2.0 Client ID (Web Application)

Use the same package name

Then update your app config:

[gfadamm]

I managed to fix the problem by adding SHA-1 from the Google Play Console .
Here's to get it:

1. Go to https://play.google.com/console/
2. Select your app.
3. On the left menu, go to “Test and Release” > “App integrity”
4. Click "settings" under "Play app signing": You'll see the SHA-1 and SHA-256 fingerprints of the Google Play app signing key