Your first release uploaded fine, you fixed a few bugs, built a fresh .aab, and dragged it into Create release in Google Play Console—only to get stopped immediately under the upload box:
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: <EXPECTED_SHA1> but the certificate used to sign the App Bundle you uploaded has fingerprint: SHA1: <ACTUAL_SHA1>
The moment you upload an app's very first signed .aab, Play Console locks that certificate's SHA-1 fingerprint as your upload key. Every future update on every track must be signed with that exact keystore. Developers hit this constantly mid-way through a 14-day closed test when pushing an update from a second computer, rebuilding after wiping a gitignored .jks file, picking the wrong key alias, or moving builds between local Gradle and Expo EAS or GitHub Actions.
Before panicking, remember how Play App Signing works on all modern .aab apps. Under Protected with Play > Play Store protection > Manage Play app signing (moved from Test and release > App integrity), the App signing page separates two keys:
- App signing key: Held securely on Google's servers and used to sign the final split APKs delivered to users' phones.
- Upload key: Held by you solely to authenticate your
.aabuploads to Play Console.
Because Google holds the real app signing key, a misplaced .jks no longer forces you to abandon your package name and start a new app. Either you still have the original keystore somewhere, or you can ask Play Console to replace the upload key.
1Check your existing keystores before resetting anything
Do not request an upload key reset right away if your original .jks or .keystore might still exist on another laptop, cloud drive, or CI service—resetting locks all bundle uploads for 48 hours.
Compare the two fingerprints in the error message first:
<EXPECTED_SHA1>: The upload key Play Console expects (you can also view this anytime on the App signing page under Upload key > SHA-1 certificate fingerprint).<ACTUAL_SHA1>: The certificate inside the.aabyou just tried to upload.
Run keytool against every .jks or .keystore file on your machine to check its SHA1 fingerprint:
keytool -list -v -keystore your-upload-key.jks
Look under Certificate fingerprints for the SHA1: line. If a single keystore holds multiple keys, inspect every Alias name: block in the output—pointing Gradle at the right .jks file with the wrong keyAlias produces a completely different SHA1.
Three quick checks solve most mismatches without a reset:
- Check if
<ACTUAL_SHA1>is actuallydebug.keystore: Runkeytool -list -v -keystore ~/.android/debug.keystore -alias androiddebugkey -storepass android -keypass android(on Windows PowerShell, replace~/.android/debug.keystorewith"$env:USERPROFILE\.android\debug.keystore"). If thatSHA1matches<ACTUAL_SHA1>, your release build silently fell back to debug signing—very common in Flutter whenandroid/key.propertiesis missing on a new machine. See how to fix bundles signed in debug mode. - Android Studio, Flutter, and Unity: Open
android/key.properties(or Project Settings > Player > Publishing Settings > Custom Keystore in Unity) and verifystoreFileandkeyAliasaren't pointing at a keystore created for a different app. - Expo (React Native / EAS Build): Moving between local Gradle builds and
eas buildis a classic trigger when EAS generates a separate upload keystore in the cloud. Run:
eas credentials
Choose Android → production → Keystore to inspect the SHA1 stored on EAS. If EAS holds <EXPECTED_SHA1>, download that keystore for local builds; if your local .jks holds <EXPECTED_SHA1>, upload it to EAS so both environments sign with the same key.
2Keystore permanently lost? Request an upload key reset in Play Console
If the original .jks file (or its keystore password) is gone for good, replace your upload key through Play App Signing:
Step 1: Generate a new 2048-bit RSA keystore
keytool -genkeypair -v -keystore new-upload-key.jks -alias upload -keyalg RSA -keysize 2048 -validity 10000
Always include -validity 10000 (about 27 years). Without -validity, keytool defaults to 90 days, which Play Console immediately rejects because upload certificates must stay valid past October 22, 2033.
Step 2: Export the public certificate in PEM format
keytool -export -rfc -keystore new-upload-key.jks -alias upload -file upload_cert.pem
Step 3: Submit upload_cert.pem in Play Console
- Sign in to Play Console as the account owner and open Protected with Play in the left menu, expand Play Store protection, and click Manage Play app signing (if you open the old Test and release > App integrity menu, click Go to Protected with Play).
- Under Upload key, click Request reset.
- Select why you're resetting the key, upload
upload_cert.pem, and submit the request. - Update
android/key.properties, your CI secrets, oreas credentialsto usenew-upload-key.jks(keyAlias=upload) and build a new.aab.
3Don't panic during the 48-hour cooldown after a reset
Play Console usually emails approval for an upload key reset within minutes. Many developers immediately rebuild with new-upload-key.jks, drop the .aab into Create release, and get hit by a second red error:
You uploaded an app bundle that is signed with an upload certificate that is not yet valid because it has been recently reset. You will be able to upload app bundles again from <Date/Time> UTC.
Nothing is wrong with your new keystore. After approving a reset, Google enforces a mandatory 48-hour security delay before the new upload certificate goes live, giving the account owner two days to spot and cancel an unauthorized key reset if their account was compromised.
- Do not generate another keystore or request another reset. Creating a third
.jksonly invalidatesnew-upload-key.jksand restarts the entire headache. - Convert
<Date/Time> UTCto your local time, wait until that exact timestamp passes, and upload the exact same.aab—no rebuild required.
4Prevent it on your next update
- Back up
.jksandkey.propertiesin a password manager on day one: Both files belong in.gitignore, never in your repository—which also means an OS reinstall, dead drive, or freshgit cloneon a second computer leaves them behind. Attach the.jksfile alongsidestorePassword,keyAlias, andkeyPasswordinside 1Password, Bitwarden, or an encrypted vault the moment you create it. - Keep local Gradle and CI / EAS on the exact same
.jks: Never let local builds use one keystore while GitHub Actions or EAS uses another. Base64-encode that single.jksinto your GitHub Actions secrets (or sync it viaeas credentials) so every build pipeline produces the exact sameSHA1.
Shipping updates smoothly during your 14-day closed test
Once your .aab clears the signing check, keep an eye out for Step 1 and Step 2 blockers that often follow on an update—such as Version code has already been used or 16 KB native library alignment, both covered in our Google Play Console AAB Upload Errors directory.
Keeping your signing setup clean matters most while your 14-day closed test is running: when you apply for access to production, Google evaluates whether testers genuinely used your app and whether you shipped real updates addressing their feedback—losing 48 hours to an avoidable key reset right before day 14 can stall your release momentum (see "More testing required" on Google Play: 5 reasons and fixes).
If you're still looking for 12 testers who will actually install your app and stay active through those updates, BetaLobby (free, no paid plans) matches 16 developers into a Team mode squad sharing one Google Group, with automatic install verification and daily check-in tracking for the full 14 days.