Skip to content
Get a quote

Google Play upload errorGoogle Play: “Your Android App Bundle is signed with the wrong key”

You build an update, upload it, and Play Console says the App Bundle was signed with the wrong key. Google checks each upload against your app’s registered upload key, and this build used a different one: a new laptop, a cloud builder that made its own key, or a lost keystore. Unless you manage the app signing key yourself and lost it, you aren’t locked out. Here’s the way back, in Google’s words, or hand it over at a fixed price.

Short answer

Sign the bundle with the upload key Play Console expects. Compare the upload key certificate on the Play app signing page in Play Console with your keystores to find the right one. If it’s lost, create a new upload key, export its certificate, and request an upload key reset in Play Console. Google keeps the app signing key, so users keep getting updates.

Why the key doesn’t match

  1. 01

    The build used a different keystore

    “You use this key to sign your app bundle before uploading it to the Play Console. Google uses it to verify your identity.” Google, Use Play App Signing

    A new machine, a debug key, or a builder such as FlutterFlow, Expo EAS or Codemagic that generated its own keystore all produce a bundle Google won’t accept. Match the fingerprint before reaching for a reset.

  2. 02

    The upload key is lost

    “If you lose your upload key or suspect that it was compromised, you are not locked out of your app.” Google, Use Play App Signing

    Ask Google for an upload key reset. Create the new upload key in Android Studio, export its certificate to PEM, then request the reset on the Play app signing page and upload the certificate.

    keytool -export -rfc -keystore upload-keystore.jks -alias upload -file upload_certificate.pem

  3. 03

    The app signing key is yours, and lost

    “This key cannot be reset if you manage it yourself and lose it.” Google, Use Play App Signing

    If the app predates Play App Signing and you kept the app signing key yourself, Google can’t reset it. Check the Play app signing page in Play Console to see whether Google holds the key.

Checked against the vendor’s docs on : Play Console Help: Use Play App Signing.

Rather hand it over?

Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.

Related: Google Play version code already used · Expo EAS Build failed · Firebase Google sign-in DEVELOPER_ERROR on Android · Google Play Data safety form rejected

Questions

More on this launch

Will a new upload key break Google sign-in or Maps?

Not for store installs, which are signed with Google’s app signing key. Google says to register the app signing key’s fingerprint with your API providers, not just your local upload key.

Where do I keep the upload key so this doesn’t happen again?

In a password manager or secret store with its password, outside the project folder and not in the repository.

Something else?

Describe it and get a written quote

Describe the app and where it is in the launch. You get a written scope, a fixed price and a timeline; we reply by email, usually within one business day.

Describe your problem All fixes