Help for owners
Google Play rejects my update because of the signing key, or I lost the key
Short answer
With Play App Signing there are two keys. You sign each bundle with an upload key, and Google signs what users receive with the app signing key. If the upload key is lost you are not locked out: you create a new one and request an upload key reset in Play Console. If you manage your own app signing key and lose it, it cannot be reset.
Does this sound like your situation?
- Play Console rejects my bundle and says it was signed with the wrong key.
- My developer left and took the keystore file with them.
- I have a keystore file but nobody knows the password.
- Google Maps or sign-in stopped working after the first release through Play.
- I do not know if my app uses Play App Signing at all.
Why does this happen?
There are two different keys
Google's page explains that the upload key is yours and is used to sign the bundle you upload, while the app signing key is held by Google and signs the final APKs delivered to users. Google recommends different keys for the two.
Confirmed by support.google.com
A lost upload key is recoverable
Google says that if you lose the upload key, you are not locked out of your app. Google can reset the upload key, whether it was lost or compromised. You create a new key and request the reset in Play Console, under Play app signing.
Confirmed by support.google.com
A lost own signing key is not
If you provide and manage your own app signing key and lose it, Google states it cannot be reset. This is why it matters whether the original release used a Google-generated key or your own.
Confirmed by support.google.com
Only admins can configure it
Google states that configuring Play App Signing needs admin permission. If the admin was the developer who left, you may not be able to reach the page.
Confirmed by support.google.com
Other services know the old fingerprint
If your app uses APIs such as Google Maps or sign-in, the app signing key's fingerprint, not just the upload key's, must be registered with those providers. A missing fingerprint can make a feature fail only in the store version.
Confirmed by support.google.comTechnical detail: Google Play rejects the upload because the bundle is signed with the wrong key
What can I do about it today?
- Open Play Console and look at the Play app signing pageIf you have access, the page shows which key the store expects. If you do not have access, see the page on lost access to Play Console.
- Search for the keystore before doing anything elseCheck old laptops, email attachments, cloud drives and the build service your developer used. Do not delete any file you find.
- Write down what you knowNote the key alias, when the app was first published and who built it. These help whoever does the reset.
- Do not publish a new app to get round itA new listing means no users, no reviews and no updates for existing installs.
- Never email or post the keystore or its passwordIf you find it, store it in a company password manager or vault and give access only to those who release the app.
When should I bring someone in?
- You cannot tell which key the app was signed with, or the app does not use Play App Signing.
- Sign-in or maps break after an upload key change.
- The only admin on the Play account is unreachable.
How do I handle it?
- Find out which signing set-up you haveI check from the Play Console side whether the app uses Play App Signing and which certificate fingerprints are registered.
- Create a new upload key properlyA new key is generated on a machine you control, protected with a password that is stored in a company vault.
- Prepare and send the reset requestThe certificate is exported and the reset request is filed in Play Console by the account admin, with me alongside.
- Check the services that use the fingerprintMaps, sign-in and other keys that depend on the app signing certificate are checked after the first release.
- Document the keysWho holds each key, where it is stored and how a release is signed is written down, so the next handover is not a crisis.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Can I get my old upload key back?
You do not need it. Google says you can request an upload key reset, and then sign with a new key.
What if the app signing key was my own?
Google states that a self-managed app signing key that is lost cannot be reset. In that case, ask Google Play support what options exist for your app.
Will users have to reinstall the app?
Google's page describes the reset for the upload key only, and says the app signing key is what Google uses to sign the APKs users receive. It does not say users must reinstall.
How long does a reset take?
Google's page does not give a time. Wait for its confirmation in Play Console.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.
For your developer: the technical fixes
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.Google Play rejects the upload because the bundle is signed with the wrong keyPlay Console blocks submitting a release whose app bundle targets an API level below 36Play Console will not accept the release because of its target API level