Your Android App Bundle is signed with the wrong key
Updated 19 October 2026
Your Android App Bundle is signed with the wrong key Your Android App Bundle is signed with the wrong key. Ensure that your App Bundle is signed with the correct signing key and try again. Your App Bundle is expected to be signed with the certificate with fingerprint: SHA1: ... but the certificate used to sign the App Bundle you uploaded has fingerprint: SHA1: ... The Android App Bundle was signed with the wrong key. Found: SHA1: ..., expected: SHA1: ... You uploaded an APK that is signed with a different certificate to your previous APKs. You must use the same certificate. You uploaded an APK or Android App Bundle that was signed in debug mode. You need to sign your APK or Android App Bundle in release mode. APK signature is invalid
Google Play rejects the upload with “Your Android App Bundle is signed with the wrong key. Ensure that your App Bundle is signed with the correct signing key and try again.” The same mismatch shows up for APKs as “You uploaded an APK that is signed with a different certificate to your previous APKs”, and through the Play Developer API (EAS Submit, fastlane, leas) as “The Android App Bundle was signed with the wrong key”. All of them mean one thing: the artifact was not signed with the upload key Play has on file for this app. Below is how to find out which key you used, how to sign with the right one, and what to do if it is lost.
This is the upload key mismatch. A permissions failure is a different page: 403 The caller does not have permission. A code Play has already accepted is Version code N has already been used. Try another version code.
The short answer
Play compares your artifact against the upload key it has registered, and your artifact was signed with something else. Most of the time the something else is the debug keystore, because release builds from a stock React Native or Expo template fall back to the debug key unless you configure otherwise. The next most common cause is a second keystore: a new one generated on another machine, by a new CI setup, or by EAS for a project it did not recognise.
The error message already tells you which key Play expects. Check which key actually signed the artifact:
keytool -printcert -jarfile app-release.aab
Compare the SHA1 it prints against the expected fingerprint in the error,
which is the upload certificate shown on the Play app signing page in Play Console. If the
owner reads CN=Android Debug, the build was debug-signed. Find the keystore whose
fingerprint matches, sign with it, and upload again.
If no keystore you hold matches and the app uses Play App Signing, request an upload key reset (steps below). It is a supported path, not a dead end.
Why this happens
With Play App Signing, which is how apps are set up by default, Play uses two keys, and the error names neither of them clearly.
| Key | Who holds it | What it does |
|---|---|---|
| Upload key | You | Signs the .aab or .apk you upload, so Play can verify it
came from you. This is the key in this error. Google can reset it if it is lost. |
| App signing key | Signs the APKs Play actually delivers to devices. You usually never touch it. |
Google re-signs your bundle with the app signing key before distribution, so the upload key only authenticates the handoff. That is why the fingerprint of the artifact you built will not match the fingerprint your users' devices see, and why comparing against the wrong one of the two sends people in circles. For this error, the only comparison that matters is your artifact against the upload key certificate.
Apps that never enrolled in Play App Signing have one key that does both jobs. For them the expected fingerprint is that single key, and there is no reset if it is lost.
The usual causes
- The debug keystore. The Expo and React Native Android templates ship a signing config that falls back to the debug key, so a fresh clone can produce a runnable release build with no credentials. The result installs fine locally and is rejected by Play. If nothing in the build was ever pointed at a real keystore, this is your answer.
- A different keystore. A keystore generated on a new laptop, in a new CI pipeline, or by a build service is a new key, even with the same alias and password. Play accepts only the one registered for the app.
- The right keystore, wrong alias. A keystore can hold several keys. The alias you sign with picks one of them.
- You uploaded the app signing key, or the upload key is a copy of it. If you gave Google your own app signing key during setup and then registered a separate upload key, uploads must be signed with the upload key, not the app signing key.
How to fix it
1. Compare SHA-1 fingerprints
Three fingerprints are in play. Line them up before changing anything.
# What signed the artifact you uploaded
keytool -printcert -jarfile app-release.aab
# What each key in a keystore would sign with
keytool -list -v -keystore upload.keystore
# What Gradle will sign each variant with
cd android && ./gradlew signingReport
Then open the app in Play Console and go to the Play app signing page (under Protected with Play in the current layout; older layouts put it at Setup → App integrity → App signing). The Upload key certificate section lists the SHA-1 Play expects. The keystore whose SHA-1 matches that value is the one to sign with. If several keystores are lying around, check each one.
2. Sign with the key Play expects
Either point the Gradle release signing config at the real upload keystore, or build normally and re-sign the finished artifact:
# .aab
jarsigner -keystore upload.keystore app-release.aab upload
# .apk
apksigner sign --ks upload.keystore --ks-key-alias upload app-release.apk
Re-signing leaves your Gradle files untouched, which matters if prebuild
regenerates them. When re-signing an .aab, start from a build whose old signature
has been removed, or build clean, so only one signature is present.
3. If you build with EAS
EAS stores the keystore it used for earlier builds. Run
eas credentials -p android, choose the build profile, and download the existing
keystore along with its alias and passwords. Compare its SHA-1 with the upload certificate in
Play Console. If EAS finds no keystore for the project and package name (a different Expo account or
project, or a changed android.package), it offers to generate a new one, and
accepting that on an app already on Play produces exactly this error.
To build with a keystore you hold instead, set "credentialsSource": "local" on
the build profile in eas.json and describe the keystore in
credentials.json:
{
"android": {
"keystore": {
"keystorePath": "credentials/android/upload.keystore",
"keystorePassword": "...",
"keyAlias": "upload",
"keyPassword": "..."
}
}
}
4. If you build with leas
leas builds normally, strips the template's debug signature, and signs the artifact with the
upload key you configure, so a debug-signed build does not reach Play unless you
set skipSigning. Point the build profile in
leas.json at the keystore Play expects:
"android": {
"buildType": "app-bundle",
"keystorePath": "credentials/android/upload.keystore",
"keyAlias": "upload"
}
In CI the same keystore comes from LEAS_ANDROID_KEYSTORE_BASE64,
LEAS_ANDROID_KEYSTORE_PASSWORD, LEAS_ANDROID_KEY_ALIAS and
LEAS_ANDROID_KEY_PASSWORD. Moving from EAS? Download the keystore with
eas credentials as above and use that file; a newly generated keystore will be
rejected. See setup for the full credential layout.
5. If the upload key is lost: request an upload key reset
For an app on Play App Signing this is recoverable. Google's Play App Signing help describes the process:
Create a new upload key (an RSA key of 2048 bits or more):
keytool -genkeypair -v -keystore upload.keystore \
-alias upload -keyalg RSA -keysize 2048 -validity 10000
Export its certificate to PEM:
keytool -export -rfc -keystore upload.keystore \
-alias upload -file upload_certificate.pem
Request the reset. In Play Console, open the Play app signing page, find the
Upload key certificate section, click Request upload key reset,
give the reason, upload upload_certificate.pem, and submit.
Wait for Google to confirm the reset before uploading with the new key. Because the app signing key does not change, existing installs keep updating normally. Store the new keystore somewhere backed up, then update EAS, leas or your CI secrets to use it.
A lost key on an app that never enrolled in Play App Signing is the unrecoverable case: Play has no separate upload key to reset.
Catching it before you build
The half of this that is knowable up front is whether the keystore you are about to sign with is the one you think it is. leas doctor opens the keystore, confirms the alias exists, and reports its expiry, which catches the wrong-keystore and wrong-alias cases before a build rather than at upload:
▸ Android
✗ Upload keystore no alias "upload" — keystore holds androiddebugkey
→ Set keyAlias in leas.json to one of the aliases above.Set up leas in 10 minutesFree, MIT licensed, and it never receives your signing keys.
If that didn’t fix it
- Re-signed and still rejected. Signing an already-signed artifact can leave the old signature in place. Build clean, then sign once.
- The keystore holds more than one alias. Signing with the wrong alias
produces exactly this error.
keytool -list -v -keystore upload.keystorelists them with their fingerprints. - You are comparing against the app signing fingerprint. Play shows both. The one that must match your artifact is the upload certificate.
- The upload now succeeds but Google Sign-In, Maps or Firebase broke. Those services check the app signing key that Play applies, not your upload key. Register the app signing key's SHA-1 and SHA-256 from the same Play Console page with each provider.
Common questions
What does "Your Android App Bundle is signed with the wrong key" mean?
The bundle you uploaded was signed with a certificate whose SHA-1 differs from the upload key Google Play has registered for the app. Play prints both fingerprints in the error: the expected one is your registered upload key, the other is what actually signed the file.
Is the upload key the same as the app signing key?
Not with Play App Signing. You hold the upload key and sign every upload with it. Google holds the app signing key and uses it to sign the APKs delivered to devices. This error is always about the upload key.
How do I check which key signed my .aab or .apk?
Run keytool -printcert -jarfile app-release.aab (or the .apk) and compare the SHA1 line with the upload key certificate in Play Console. An owner of CN=Android Debug means the build was signed with the debug keystore.
I lost my upload key. Can I still update my app?
Yes, if the app uses Play App Signing. Generate a new upload key, export its certificate as a PEM file, and click Request upload key reset on the Play app signing page in Play Console. Existing users are unaffected because the app signing key does not change.
I build with EAS. Where is my upload key?
If EAS created it, EAS stores it. Run eas credentials -p android, pick the build profile, and download the existing keystore. Compare its SHA-1 with the upload key certificate in Play Console before generating anything new.