DEVELOPER_ERROR: SHA1 doesn't work on Google Play Store, but work on production code [android] [googleSignIn]

[alexiej]

My code for googleSignIn works fine on iPhone, Android Debug, Android Release, but when I push the code to Google Play for testing I've got error:

DEVELOPER_ERROR

I've added all type of SHA1, SHA256 to the firebase but without success :(

One I've got from ./gradlew signingReport for debug, and release, and after adding this it works fine. But when I've upload a release to the Google Play :(

I also added all SHA1, SHA256 from the Google Console Play App Signing Certificate but without success.
The only version that works is:

• iPhone
• Android Debug
• Android Release

but I din't know why Android Google Play for Open / Internal testing doesn't work :( Is it possible to get information about what SHA1 is assigned to the app after release?

[alexiej]

The topic can be closed. I found the solution. For anyone like me who f** with this 2 days. You need use App signing key: legacy key (not latest)

[maztak]

It's worked for me although I'm developing native android app.
When I run apksigner verify --print-certs 90.apk for the apk that signed universal apk downloaded from Play Console bundle explorer.

Signer (minSdkVersion=33, maxSdkVersion=2147483647) certificate SHA-1 digest:
Signer (minSdkVersion=24, maxSdkVersion=32) certificate SHA-1 digest:
Source Stamp Signer certificate SHA-1 digest:

My Android device and Android emulator also Android14(SDK34), so I don't know this response really relevant to this bug, but It worked for me. Thanks a lot, lovely ;)