Ctrl+Z Therapy
CasesQuick answersGuides10-minute checklistHow we testCartoonSend it in

Google login works in testing but fails from Google Play? Add the right SHA-1

Ship ItChecked against the official source

Source checked 10 Oct 2026 · Published 23 Oct 2026 · Last reviewed 23 Oct 2026 · By Ctrl+Z Therapy (how we test)

The short answer

Google Sign-in needs the SHA-1 fingerprint of your app's signing certificate. With Play App Signing (required for Android App Bundles), Google signs the final app that users download with its own app signing key. Google's Play Console Help says you must "register the Google-held app signing key fingerprint with your API providers, not just your local upload key". That's why login can work on your test phone but fail in the version from Google Play.

What to do

  1. In Play Console, open App Integrity (Release, Setup, App Integrity) and copy the SHA-1 of the App signing key certificate.
  2. Add it to your Android app in Firebase, or to the Android OAuth client in Google Cloud.
  3. Keep your debug and upload key fingerprints there too, so test builds still work.
  4. Ask your AI tool: "Google sign-in fails only in the version downloaded from Google Play. Tell me every place I must add the SHA-1 of the Play app signing key, and keep my debug and upload keys working."

Good to know

  • Google's help pages don't all describe the Play Console menus the same way. Look for App Integrity and the App signing key certificate.

Source

Checked on 10 Oct 2026. Prices, limits and settings change, so check the source before you rely on them.