React Native Google Sign-In fails with DEVELOPER_ERROR on Android
DEVELOPER_ERRORShort answer
DEVELOPER_ERROR means the app and the Google or Firebase setup do not match. The usual mismatches are a missing SHA-1 for the key that signed this build, a webClientId that is not the web type, a package name that differs from the console, or Google sign-in not enabled. Fix each in the console, then rebuild.
Fix it fast
1Find out which cause you have
Let the official Configuration Doctor inspect the APK, device or emulator that shows the error; it compares your setup with Google's.
npx @react-native-google-signin/config-doctor2Match what you see, then jump to its fix
- 1
Sign-in works with one build type (debug or release) but fails with the otherThe SHA-1 of the signing key is not registeredFix - 2
configure() was given an ID, but it is of the Android type or from another projectwebClientId is wrong, or it is an Android client IDFix - 3
applicationId differs from the package name in the console, or Google is not enabled as a sign-in methodPackage name or Firebase setup does not match the appFix - 4
Fails only when installed through an Internal App Sharing linkThe build came from Internal App SharingFix
- 1
What does the error look like?
DEVELOPER_ERRORcode: 10Developer console is not set up correctly
Cause 1 of 4
The SHA-1 of the signing key is not registered
1Check
Every signing configuration needs its SHA-1 in Firebase: debug, release, EAS and Play App Signing. The setup guide says to use SHA-1, not SHA-256. Get the local fingerprints from the signing report.
cd android && ./gradlew signingReport2Fix
In Firebase console open Project settings > Your apps, choose the app, click Add fingerprint, and add each SHA-1. For Play builds take the SHA-1 from Play Console > Release > Setup > App Signing. For EAS builds run eas credentials. Download google-services.json again.
eas credentials3Verify
Rebuild the app and sign in again; the account picker appears and returns a user.
npx react-native run-androidConfirmed by react-native-google-signin.github.io
Cause 2 of 4
webClientId is wrong, or it is an Android client ID
1Check
The troubleshooting page says that if you pass webClientId to GoogleSignin.configure() it must be the ID of the Web type, listed under OAuth 2.0 client IDs in Google's console.
grep -rn "webClientId" src app App.tsx 2>/dev/null2Fix
Copy the Web client ID from the OAuth 2.0 client IDs list of the same project and set it in configure.
GoogleSignin.configure({
webClientId: '<your-web-client-id>.apps.googleusercontent.com',
});3Verify
Restart the app and try to sign in again.
npx react-native start --reset-cacheConfirmed by react-native-google-signin.github.io
Cause 3 of 4
Package name or Firebase setup does not match the app
1Check
The package name in AndroidManifest.xml should match your application ID. With Firebase Auth, Google must be enabled under Build > Authentication > Sign-in method.
grep -n "applicationId" android/app/build.gradle
grep -n "package" android/app/src/main/AndroidManifest.xml2Fix
Make the console app's package name equal the applicationId, enable the Google provider, then download google-services.json again and rebuild.
# replace android/app/google-services.json with the new download, then rebuild3Verify
Sign-in completes on the rebuilt app.
npx react-native run-androidConfirmed by react-native-google-signin.github.io
Cause 4 of 4
The build came from Internal App Sharing
1Check
The troubleshooting page says Internal App Sharing re-signs the app with Google's own key, which causes DEVELOPER_ERROR.
npx @react-native-google-signin/config-doctor2Fix
Test with a build signed by a key whose SHA-1 you registered, and sign in with that build.
npx @react-native-google-signin/config-doctor3Verify
Sign-in works on the build signed with your registered key.
npx @react-native-google-signin/config-doctorConfirmed by react-native-google-signin.github.io
How do I stop it coming back?
- Collect the SHA-1 for debug, release, EAS and Play App Signing keys, and add them all in Firebase.
- Keep webClientId in one config file and never use an Android client ID there.
- Download a fresh google-services.json after every console change.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
- QistLockA NestJS and React SaaS driving an Android Device Owner agent that locks financed phones when payments lapse.
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- TaskvareA task and project-management suite: React on the web, Flutter on mobile, TypeScript underneath.
Related fixes
Mobile apps
Android build stops at processDebugManifest in a React Native app
Manifest merger failed
processDebugManifest is the step that merges your AndroidManifest.xml with the manifests of every library.
2 causes, each with a fixMobile apps
React Native Android build cannot find the foojay-resolver-convention plugin
Plugin [id: 'org.gradle.toolchains.foojay-resolver-convention'] was not found in any of the following sources:
The foojay plugin is a settings plugin that Gradle downloads from the Plugin Portal.
3 causes, each with a fixMobile apps
Kotlin and Java compile to different JVM targets in a React Native Android build
'compileJava' task (current target is 1.8) and 'compileKotlin' task (current target is 11)
Gradle refuses to build when the Java task and the Kotlin task target different JVM versions.
3 causes, each with a fixMobile apps
Gradle cannot run node in a React Native Android build
Process 'command 'node'' finished with non-zero exit value 1
The React Native Gradle plugin starts node for bundling.
3 causes, each with a fixMobile apps
The Android emulator opens the app but never connects to Metro or Expo
Metro bundler ECONNREFUSED 127.0.0.1:19001
When the emulator cannot reach Metro, first prove each side on its own: adb sees the emulator, and Metro listens on its port.
4 causes, each with a fixMobile apps
Axios request works on iOS or in a browser but fails on Android with Network Error
AxiosError: Network Error
A React Native app has no CORS, so on Android a Network Error usually means the request never reached the server.
3 causes, each with a fix