-
Notifications
You must be signed in to change notification settings - Fork 259
Google Play Store issue #58
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
Comments
I am having the same issue now, once I release the whole thing fails... When I build and install locally it's fine |
I solved this problem. Did you use Google Play App Signing to register your app with Google Play Console? There are two SHA-1 values for uploading and for signing. Try changing the SHA-1 value. |
Thanks you're right about the SHA-1. However, for those using firebase with this plugin just link your app (with the google play store link) in the firebase console which will update the SHA-1 in the firebase project. If it doesn't update just add it in the firebase project manually yourself. Basically there should be both SHAs in the firebase project the upload SHA-1 and the app signing SHA-1 |
I noticed that when you are using Android Bundles and let Google Play Store sign your app, the SHA-1 key is not valid for the app in the app store anymore. I had to setup another Android App in the Google console, using the SHA-1 you can find in Play Store. |
MY PROBLEM :
Google Sign-in worked fine before uploading my app to the Google Play Store. However, if you upload your app to the Google Play Store and download the app from the Store and try Google Sign-in, you will not be able to sign in.
In logcat, I see the following error message:



Has anyone experienced a similar problem?
The text was updated successfully, but these errors were encountered: