Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Getting Developer Error even after putting everything in place in release mode (Android)

See original GitHub issue

Info

React native google signIn is working fine in debug mode. But google siginIn is not working in release mode, its giving DEVELOPER_ERROR code 10. I have added both debug and release certificates on firebase console, everything is checked.

But still I am getting DEVELOPER_ERROR. Do we need to add SHA1 from playstore also for release mode (apk generated using ./gradlew assembleRelease)?

Expected Behavior

Actual Behavior

Environment

Please provide

System:
    OS: Windows 10 10.0.18362
    CPU: (8) x64 Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
    Memory: 1.13 GB / 7.84 GB
  Binaries:
    Node: 12.9.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.4 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 6.10.2 - C:\Program Files\nodejs\npm.CMD
    Watchman: Not Found
  SDKs:
    Android SDK:
      API Levels: 28, 30
      Build Tools: 28.0.3, 29.0.3, 30.0.0
      System Images: android-28 | Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom_64, android-30 | Google Play Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: Version  3.6.0.0 AI-192.7142.36.36.6392135
  Languages:
    Java: 1.8.0_211
    Python: 3.8.3
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.13.1 => 16.13.1
    react-native: 0.63.0 => 0.63.0
  npmGlobalPackages:
    *react-native*: Not Found

Issue Analytics

State:
Created 3 years ago
Reactions:7
Comments:25 (1 by maintainers)

Top GitHub Comments

15reactions

usmansbkcommented, Jul 31, 2020

I use this package every year and every year I have to come back here. Lol

14reactions

radetskycommented, Jul 16, 2020

Maybe you turned on Google Play Signature in Play Market. This feature replaces your certificate by auto-generated by Google. You can find it at the Play Console on the page ‘App signature’. You can download deployment certificate or just copy-paste fingerprints MD5, SHA1, etc. Copy SHA1 to Firebase Console App settings Android app.

PS. Also, it works for Facebook sign in. Download the certificate and do something like this:

cat ~/Downloads/deployment_cert.der | openssl sha1 -binary | openssl base64

to get hash to use with Facebook application settings

PS. I’m not a contributor. I’m also dev. 😃

Top Results From Across the Web

React-native google signin gives Developer Error

Go to the Google Play console and copy SHA-1 key from Release ... and added an Android Oauth client Id with the correct...

Prepare for release - Android Developers

Developer documentation on how to build the signed, release-ready APK. This process is the same for all Android apps.

Troubleshoot known issues with Android Emulator

To update the emulator in Android Studio, go to Tools > SDK Manager and install the latest stable version of Android platform.

Known issues with Android Studio and Android Gradle Plugin

This error occurs on Linux-based platforms when starting the native debugger. It indicates that one of the libraries required by the native debugger...

Crashes | Android Developers

The first step to fix a crash is to identify the place where it happens. You can use the stack trace available in...