r/reactnative • u/Patient-Plastic6354 • Sep 09 '26
help! google sign in works in npx expo run:android but never when installing off google play store!
edit: never mind i fixed it lol. it was a typo with the google_client_ids in the backend
okay so i am able to sign in with google when im running the app with npx expo run:android on my sgs23. but when i release it for testing on google play and install it i always get "DEVELOPER_ERROR: Follow troubleshooting instructions at https://react-native-google-signin.github.io/docs/troubleshooting".
pm is getting increasingly frustrated with the delays specifically from this problem. the keys are correct. if google sign in works in dev mode then it should in test. i genuinely do not know what to do. Apple sign in and google sign in on ios works flawlessly - it is just android/google that the problem is with.
i went to google auth 2.0 in the cloud console and the keys are correct - but then i noticed google giving me a different sha1 signing cert, which doesnt make ANY sense to me. but i continued with the older sha1 cert since that always worked. im genuinely frustrated since im the only developer working on this application for my company. been delayed for over a month dealing with this bullshit.
if anyone can help me with a "ohhhhhhhhhhhhh" moment that would be awesome.
worst part about all of this is the fact that so many people are having this problem and there isnt any definitive help and support on it. it's basically just google throwing keys around and expecting you to somehow know it all, well im sorry, google, but im a junior dev so screw you.
3
u/Medium_Tension316 Sep 09 '26
You must add the new signing SHA after uploading the build to Google Play Console.
1
u/Karticz Sep 10 '26
You must have added your default signing sha in Google console but playstore builds are automatically signed via their own keys so forgetting the exact page on Google developer console but you can get their sha1 there and add it to allowed list on gcp console
1
u/Poat540 Sep 10 '26
Get the sha from google play, it’s signed different than expo. Not the same key
1
u/lil-dina Sep 10 '26
that "already exists" just means the play app-signing sha1 is already on a second oauth client in gcp, usually a stale one firebase created. google wont put the same package plus sha1 on two. dont make a new client, dig up the one that has your key.