Where to Find Your App's SHA-256 Fingerprint
Google Sign-In, Firebase and Maps all ask for your app's SHA-256 certificate fingerprint. Here's where to find it in Play Console if you've published, or straight from the APK if you haven't.
Where to Find Your App's SHA-256 Fingerprint
Some services — Google Sign-In, Firebase, Google Maps — won't work until you give them your app's SHA-256 certificate fingerprint. It's how Google checks that the app asking for access is really yours.
Where you find it depends on whether your app is already on Google Play.
---
If your app is on Google Play
This is the one you need in almost every case.
1. Open Google Play Console and select your app. 2. In the left menu go to Test and release → Setup → App integrity. 3. Open the App signing tab.
You'll see two certificates:
- App signing key certificate — the key Google uses to sign the app your users actually install.
- Upload key certificate — the key used to upload releases.
Each one shows an SHA-256 certificate fingerprint with a copy button. For Google Sign-In, Firebase and Google Maps, use the one under App signing key certificate.
---
If you haven't published yet
If all you have is the APK file, you can read the fingerprint straight out of it. You need Java installed (it also comes with Android Studio). On your computer, run:
keytool -printcert -jarfile myapp.apkIn the output, look for the line that starts with SHA256: — that's your fingerprint. Nothing else is needed: no keystore, no account, no upload.
→ Not sure how to get the APK? See APK vs AAB: Getting Your Android App File.
---
The mistake that costs people an afternoon
Sign-in works perfectly while you test, then fails for everyone who installs from Google Play.
That happens when the fingerprint you registered belongs to the upload key (or to a test build) rather than to the app signing key. Google re-signs your app with the app signing key before delivering it, so that's the certificate your users' copy actually carries.
The fix is simple: register the app signing key SHA-256 as well. Most services let you add more than one fingerprint, so you can keep the test one and add the Play one next to it — then both your test build and the published app work.
---
Where each fingerprint goes
| Service | Where you paste it |
|---|---|
| Google Sign-In | Google Cloud Console → Credentials → your Android OAuth client |
| Firebase | Project settings → your Android app → Add fingerprint |
| Google Maps SDK | Google Cloud Console → Credentials → API key → Application restrictions → Android apps |
---
In short
keytool -printcert -jarfile myapp.apk.Ready to get your app on Google Play? Start with How to Publish Your Android App to Google Play.
Snapp Team
SNAPP ekibinden yazılar ve içerikler