Comments (5)
Hello @bglgwyng,
thank you for sponsoring!
DEVELOPER_ERROR is always a misconfiguration issue: either your package name or the SAH1 hash you entered in firebase (or google cloud console) is wrong. You should be able to find the SHA in play store console, as seen here https://github.com/react-native-google-signin/google-signin/blob/master/docs/android-guide.md#google-login-does-not-work-when-downloading-my-app-from-the-play-store
If there are more SHAs, add them all to firebase.
Please let me know if that helps
Thank you 🙂
from google-signin.
hello,
provided that you downloaded the apk from the store, keytool / apksigner will be giving you the correct information.
Firebase is only a proxy to google cloud console, so please double-check there. If that doesn't help then I don't think I can debug this over comments.
Good luck :)))
from google-signin.
Thank you for your brief reply! There's one thing I forgot to report.
Once I removed all the SHA1 fingerprints from my Firebase app to see what happened. What's weird is that the development build succeeded at signing it, while the fingerprints of it would also have been removed. So I'm confused if the modification on fingerprint values in Firebase console really affects the behavior. Is there a delay in applying the change? What would be the better way to debug this behavior?
from google-signin.
Also, I copied the installed APK from my device and examined its signature by
keytool -printcert -jarfile myapp.apk
And it was the same as the one registered on my Firebase project. From my understanding, this indicates that there's no chance of having problems with SHA1 fingerprints. Or am I missing something else?
from google-signin.
@vonovak You saved me! https://github.com/react-native-google-signin/google-signin/blob/master/docs/android-guide.md#google-login-does-not-work-when-downloading-my-app-from-the-play-store
This document has the right solution for me. To be more specific, this part.
If you are not using Firebase, and your app is enabled for "Google Play App Signing": Go to "https://console.developers.google.com/" -> click "Credential" in the right panel -> Find "Client ID" for type "Android" under "OAuth 2.0 Client IDs" section -> Edit -> replace "SHA-1 certificate fingerprint" with the one from App -> Release (in left sidebar) -> Setup -> App integrity -> App signing key certificate.
I found that the OAuth2 ID for Android in GCP doesn't have the valid SHA1 fingerprint value. So I copied the SHA1 fingerprint from my Google Play Store console into it. And the problem was gone.
But one thing weird is that I've been using Firebase and I suppose that at one moment, Firebase stopped reflecting its fingerprint value to GCP. Not sure if it's because of my mistake or just Firebase's wrong behavior.
from google-signin.
Related Issues (20)
- Incorrect version number in docs? HOT 1
- iOS Error when running pod install: CocoaPods could not find compatible versions for pod "ExpoAdapterGoogleSignIn" HOT 3
- Developer Error For Internal Testing HOT 2
- Additional SignIn Parameters
- missing dependencies HOT 2
- OneTap fails on web when 'sign-in prompts' are disabled HOT 4
- App crashing on iOS while tapping on Sign in with Google! HOT 4
- signInSilently gives error [Error: SIGN_IN_REQUIRED] HOT 8
- Unable to install sponsored version HOT 3
- Solution to issue #1176 (Supabase on iOS with Expo) HOT 2
- How to import isErrorWithCode HOT 2
- 11.0.0: CocoaPods could not find compatible versions for pod "ExpoAdapterGoogleSignIn": HOT 1
- [Website] Example links don't work HOT 2
- Include of non-modular header inside framework module 'GTMAppAuth.GTMAppAuthFetcherAuthorization': HOT 1
- (DEVELOPER_ERROR) Only in production Android HOT 1
- Tried to register two views with the same name RNGoogleSigninButton error
- I am not getting user's Birthday HOT 2
- AppAuth 1.7.0 will give 'No visible @interface for 'OIDAuthorizationResponse' declares the selector 'tokenExchangeRequestWithAdditionalParameters:' HOT 8
- no visible @interface for 'OIDAuthorizationResponse' declares the selector 'tokenExchangeRequestWithAdditionalParameters:' HOT 3
- Error: RN GoogleSignin native module is not correctly linked. Please read the readme, setup and troubleshooting instructions carefully. HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from google-signin.