Google-signin: DEVELOPER_ERROR when Published in Google Play

[Brenw10]

Details

I added the Google Sigin and created the Auth for Android and set the SHA-1. I tested it in Debug, Release for emulator and real device and everything is working fine.
Today I was publishing in Google Play as internal testing and when I try to login I got the DEVELOPER_ERROR when downloaded by Google Play.
Is there any configuration missing from me?

Steps to Reproduce

You can see my code in: https://github.com/Brenw10/appAlineCampos

• Access application
• Click on Google Sign Button

Expected Behavior

Google Signin working fine

Actual Behavior

Google Signin showing DEVELOPER_ERROR

[DanielLinna]

I got the same when using Firebase for authentication. Google signs the application with different SHA-1, so I had to add that SHA-1 fingerprint to Firebase settings too, maybe that is the case for you too? You can find the fingerprint from Google Play Console, under Settings > App Integrity > App signing key certificate.

[Brenw10]

Thanks. This was the issue. Google Play creates a new SHA-1 and I get this in Google Play Console and it worked.

[SrBrahma]

I got the same when using Firebase for authentication. Google signs the application with different SHA-1, so I had to add that SHA-1 fingerprint to Firebase settings too, maybe that is the case for you too? You can find the fingerprint from Google Play Console, under Settings > App Integrity > App signing key certificate.

This. 6 hours of suffering here.

[mikehardy]

If I am not mistaken, the SHA-1 is from your keystore used to build the app if you are not doing application bundles and allowing Google to manage your signing key, but of course if you are using app bundles and letting google manage the signing then the SHA-1 must be fetched from them. Appears this may still happen on some devices (Samsung apparently) even if the SHA-1 is correct, per @ithustle

[damienherve]

For everyone having this error with Firebase, here was the problem (at least for me):
Looking at the Firebase console, i saw that when i added my SHA-1 fingerprint for my Android application, my google-services.json didn't change. Only the initial SHA-1 was added in the file with a line like:
"oauth_client": [ { "client_id": "<client_id>", "client_type": 1, "android_info": { "package_name": "<package_name>", "certificate_hash": "<sha-1>" } } ],

Looking at https://console.cloud.google.com/apis/credentials i saw that only one key was added for Android in the OAuth 2.0 section, and by editing this one i saw that it was linked to the SHA-1 that i gave when i created the App in Firebase (my debug SHA-1)

So when you add a new SHA-1 in Firebase, it will not automatically create a OAuth 2.0 client ID in Google Cloud Platform. And so, the google-services.json can't be updated because firebase can't find the pair & in its database.

What i had to do is create manually new Oauth 2.0 client IDs in Google Cloud Platform (Android type) matching the SHA-1 provided by Google Play App Signing. Then, when i had the same SHA-1 in the firebase console, the google-services.json 'oauth_client' value is well updated with all my oauth_clients, and corresponding SHA-1.

Then finally, gradle clean and rebuild your app, it should be good now.

Hope this will help