Home › Build error fixes › Android / Gradle

Bundle signed with a different key than Play expects

Android / Gradle · last reviewed 2026-11-10

The error looks like this

Your Android App Bundle is signed with the wrong key. Ensure that your App Bundle is signed with the correct signing key

Why it happens

You built with a new/other keystore. Play only accepts the registered upload key.

How to fix it

  1. Compare SHA-1: keytool -list -v -keystore your.keystore vs Play Console > Setup > App signing > Upload key certificate.
  2. Find and use the original keystore.
  3. If lost and you use Play App Signing: request an upload key reset in Play Console (takes a few days).

Not sure this is your error? Let ReleaseMedic read the whole log

Build logs are long and the last line is rarely the real cause. ReleaseMedic finds the first real error, explains it and gives the steps — free, and the log never leaves your computer.

$ npx releasemedic log build.log

Or pipe a build straight in: cd android && ./gradlew bundleRelease 2>&1 | npx releasemedic log -

Catch it before you build

Most release errors come from project settings you can check in seconds — signing, SDK levels, privacy manifests, permissions, push and login setup.

$ npx releasemedic

Related Android / Gradle errors