-
-
Notifications
You must be signed in to change notification settings - Fork 890
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting Developer Error even after putting everything in place in release mode (Android) #905
Comments
Maybe you turned on Google Play Signature in Play Market. This feature replaces your certificate by auto-generated by Google. PS. Also, it works for Facebook sign in. Download the certificate and do something like this:
to get hash to use with Facebook application settings PS. I'm not a contributor. I'm also dev. :) |
I'm having the same problem |
Same problem |
I'm having same problem. |
I have used a webClientId which I put to the whitelisted client ids in firebase console inside google login. But still it gives me DEVELOPER_ERROR. If I use my debug keystore, the login works because I have added the SHA1 of debug keystore in firebase console. But I cannot add the SHA1 of release keystore because it is already used in another project which I have lost access to. So I have created a new web client and added its id to the firebase google login whitelist and using the same inside the app. But still getting DEVELOPER_ERROR |
I use this package every year and every year I have to come back here. Lol |
If you're still having this problem try this solution #706 (comment) |
@usmansbk your solution did not help. I have already added the correct SHA1 to firebase. I am not using the default debug keystore. I have created my own and added the SHA1 to firebase. When I build the app using this keystore it works fine. But when I do the same with another keystore it does not work even after whitelisting the web client id |
Just started getting this problem too. Everything seems to be configured correctly, including SHA1. |
Can't seem to solve this issue. I have two custom keystores setup.
Still the same |
Always check the version to debug-keystore SHA you generated. I think there's one in the android/ folder of the project and there's ~/android of the whole system. |
No matters weather you are using a firebase or NOT you have to have both the configurations (Android as well as Web client ) //DeveloperError or any login error
|
I am facing same developer_error since I am using android React native app to complete google singin.
also to create SHA-1 for android used this command to C:\Users\satailor\Documents\ReactNative_workspace\App>keytool -list -v -alias androiddebugkey -keystore C:\Users\satailor\Documents\ReactNative_workspace\app\android\app\debug.keystore Inside Android folder following changes are added: android/build.gradle file included following lines:
Help me to resolve an issue. Let me know any other information required. |
Is there currently any solution to this problem? As many of you, I am struggling with the same problem. Everything is in place but I still get DEVELOPER_ERROR. |
Please help with this issue, I have tried everything available on the git and stack-overlow for this issue. |
If you are using firebase & still looking for solutions:
|
|
|
Following this tutorial fixed the problem for me. |
Not having an argument will throw to me |
https://github.com/t-ho/react-native-google-signin-example |
closing because this is not an issue with the library but with the app setup / environment. Thanks |
Nice work |
I use Firebase signin approach. It requires using |
how did you solved? |
@shivanshrajpoot ,then where else to provide this configuration like
Please |
Hi @AleeFarook , It's been quite a lot of time since I wrote this comment, but the configuration is automatically picked up from the config file that you download from console. If you reinitialise with a config object then it does not uses the config from the file. |
Hi Everyone, this issue is because of how configure is called for different platforms, this has been there for a lot of time and wasted a lot of time of others as well, If I had know that this will frighten the people for so long I would have created the PR my self, but here's one PR that someone create to fix this. check this may be fork it for temporary solution. #1003 |
Hi @shivansh-rajpoot-vas, your solution was worked without the configuration object but I my case I was require the serverAuthCode which I was getting null, so after some trouble the solution I found that: ` await GoogleSignin.hasPlayServices({ showPlayServicesUpdateDialog: true });
`
and add sign method of google sign in Authentication module in Firebase from side menu. now the solution worked and Thanks @shivansh-rajpoot-vas for quick response. |
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
The text was updated successfully, but these errors were encountered: