All posts

Google sign-in fails in Play test builds? Check the SHA-1

· 7 min read

"Sign in with Google" works every time on your own phone. Then your first testers install the app from a Google Play test track, tap the same button, and nothing happens, or they get an error. You changed no code. What changed is the key that signed the app. This post explains which keys sign your app on the way to testers, where to find each fingerprint, and where to register it. I checked the official Google and Firebase pages in November 2026.

Short answer: Google sign-in checks your app's signing certificate. The build from Android Studio is signed with your debug key. A build from a Play test track is signed by Google with your app signing key. A build through internal app sharing, or an AAB through Firebase App Distribution, gets yet another test key. Register the SHA-1 fingerprint of every key your testers' builds use, in Firebase or Google Cloud. Then test the real tester build, not your local one.

Why it works for you and fails for testers

Google's Authenticating your client page says "Certain Google Play services (such as Google Sign-in and App Invites) require you to provide the SHA-1 of your signing certificate so we can create an OAuth2 client and API key for your app." Your app is recognised by its package name plus that fingerprint. A build signed with a key you never registered looks like a stranger's app.

Most apps on Google Play use Play App Signing: you sign your upload with an upload key, and Google re-signs what users and testers get. The Play App Signing help page says it plainly: "If your app uses APIs such as Google Maps, OAuth, or Facebook Login, those services authenticate your app using your app signing key's fingerprint. Because Google signs the final APK, you must register the Google-held app signing key fingerprint with your API providers, not just your local upload key."

If your logs show status code 10, Google's CommonStatusCodes reference names it DEVELOPER_ERROR: "The application is misconfigured." A missing fingerprint is exactly that kind of misconfiguration, so check it first.

The keys that can sign your app

  • Debug key. What Android Studio uses when you press Run. It lives on your computer, so a teammate's laptop has a different one.
  • Upload key. What you sign the release bundle with before you upload it to Play. Testers on Play tracks never get a build signed with it.
  • App signing key. Google's key, used for what people install from Play, including internal, closed and open test tracks.
  • Internal app sharing key. The internal app sharing page says uploads are "automatically re-signed with an Internal App Sharing key, which is automatically created for your app by Google", and "Every APK is resigned with this test certificate, regardless of which certificate you used to sign your app."
  • Firebase App Distribution with an AAB. Firebase's AAB guide says "App Distribution integrates with Google Play's internal app sharing service", and "Generated APKs are automatically resigned by Google Play using a test app signing key certificate." Upload an APK instead, and it keeps your own signature: the APK version of that guide says "You must sign the APK with your debug key or app signing key."

So the same app can need three or four registered fingerprints: yours, the Play one, and a test one. More on that channel in Firebase App Distribution for test builds.

Find each fingerprint

Debug key

The client-auth page gives this command for Mac and Linux, and adds "The default password for the debug keystore is android." It also says Gradle's signingReport task prints the same information.

keytool -list -v \
  -alias androiddebugkey \
  -keystore ~/.android/debug.keystore

App signing key (Play test tracks and production)

The Play help page: "Sign in to Play Console, select your app, and go to the Play app signing page (Protected with Play > Play Store protection > Manage Play app signing). Scroll to the App signing key section. Copy the required fingerprints (SHA-1 or SHA-256)."

Internal app sharing and App Distribution AABs

In Play Console, the internal app sharing page says to go to "Test and release > Internal testing > Internal app sharing". On the Uploaders and testers tab, scroll to the "Internal test certificate" section. The certificate is created after your first upload there. For App Distribution AABs, Firebase says "your app's test certificate can be viewed in the Firebase console."

Register them in the right place

  • Firebase Authentication. Firebase's Google sign-in guide: "In the Firebase console, go to the settings Settings > General tab. Scroll down to the Your apps card, select your Android app, and add your SHA-1 fingerprint in the SHA certificate fingerprints field." Add one entry per key. Then, as the same guide says, "download the updated Firebase config file (google-services.json), which now contains the OAuth client information required for Google sign-in", and ship a new build with it.
  • Google Cloud without Firebase. Google Cloud's OAuth clients help page says that for an Android client "You need to specify your Android app's package name and SHA1 fingerprint." Each fingerprint gets its own Android client.
  • The Web client ID in your code. With Credential Manager, Android's Sign in with Google guide says to set setServerClientId, and "The webClientId is the Web Client ID you set up for OAuth in your Google Cloud Project". Not the Android client ID. Mixing them up breaks sign-in on every build, not only test builds.

The Play page names Facebook Login too, so other sign-in providers that ask for a key hash need the Play key as well. And features that check the SHA-256 fingerprint, such as verified app links, have the same trap. See test deep links before launch.

A test task testers can follow

Your own phone can't tell you if this works, because it runs a different build. Ask testers who installed from the test link. Paste this into your test task:

Install from the test link I sent
(not from a file).

Tap "Sign in with Google".
- Did the account picker appear?
- After you picked an account,
  were you signed in?
- If not: what did you see?
  Exact error text or a screenshot.

Close the app fully, open it again.
Are you still signed in?

Send: phone model + Android version.

For writing tasks like this, see how to write a test task, and for which Play track to use when, see internal, closed and open testing.

Where TestSwap fits

TestSwap is a free app testing exchange where indie developers test each other's apps. You can post web, iOS and Android apps, with a link testers can open or install, like a TestFlight link or a Google Play testing link. You can add a test login, which only signed-in testers can see. Everyone starts with 3 credits. Writing a review earns 1, and each review your app receives costs 1. You can rate each review 👍 or 👎, and a 👎 takes back the reviewer's credit.

That makes it a good place for this check: the testers install your app the way real users will, on phones you don't own. TestSwap is not affiliated with Google.

The checklist

  1. List every way testers get your app: Play track, internal app sharing, App Distribution, a shared APK.
  2. Find the SHA-1 of each key behind those builds, plus your own debug key.
  3. Register each one in Firebase (SHA certificate fingerprints) or as a Google Cloud Android client.
  4. If you use Firebase, download the new google-services.json and ship a new build.
  5. Use the Web client ID in setServerClientId.
  6. Have a tester who installed from the test link sign in, close the app, and open it again.