Two keys: app signing key and upload key
With Play App Signing there are two keys. The app signing key is held by Google and signs the APKs delivered to users. The upload key is yours and proves an AAB came from you. You sign with the upload key; Google verifies, then re-signs with the app signing key for distribution.
| Key | Held by | Purpose | If lost |
|---|---|---|---|
| App signing key | Signs APKs on user devices | Not lost through you | |
| Upload key | Developer | Proves uploads come from you | Request a reset via official flow |
The benefit: even if your upload key leaks or disappears, the signing identity on user devices stays intact, which is far cheaper to recover from than the old model of one self-held key.
Enabling it for a new app
- Create the app in Play Console and begin the first release
- Choose to let Google manage and protect the app signing key
- Generate an upload keystore locally and sign your AAB with it
- Upload the AAB; Google registers the upload certificate fingerprint
- Back up the keystore and passwords in at least two secure places and record alias and fingerprint
Never send the keystore or passwords to anyone or commit them to a repository. Store them with your handover docs and team password manager.
Also useful in this topic cluster:
If the upload key is lost
If you lose the upload key or suspect leakage, request a reset on the app signing page: generate a new upload key, export its public certificate and submit the request. After verification Google enables the new key and retires the old one. It can take days and resets per app are limited, so do not retry repeatedly.
Only owners or members with the right permissions can submit a reset. Mismatched permissions after a handover often surface here, so the checklist must say who can manage app signing.
# Generate a new upload key (example path and alias; use your own)
keytool -genkeypair -v -keystore upload-new.jks \
-alias upload -keyalg RSA -keysize 2048 -validity 10000
# Export the PEM certificate to attach to the upload key reset request in Play Console
keytool -export -rfc -keystore upload-new.jks \
-alias upload -file upload_certificate.pemClean accounts versus accounts with keyed apps
In buying chats you hear 'clean package' and 'with key'. Clean usually means no historic apps or signing leftovers; with key means apps already exist along with upload-key material used to keep updating them.
| Type | Meaning | Upside | Verify |
|---|---|---|---|
| Clean (empty) | No apps | No baggage | Create date, type, closed-testing status |
| With apps | Existing apps | Continuity of users and ratings | Package names, signing, policy history, upload keys |
| With key | Apps plus upload key | Can ship updates immediately | Legitimate key source and replaceability |
Any claim that 'with key guarantees approval' is not credible. A key solves can-I-upload, not is-it-compliant.
Signing terms to agree in a handover
- Whether each app uses Play App Signing, in writing
- Who holds the upload key and whether it is reset to a buyer-generated key
- If legacy apps stay, verify package names, versions and policy status
- Within week one, the new owner resets the key and confirms an upload works
Credential-only handovers carry noticeably more risk; read the account versus app transfer guide and the first-week checklist.
Day-to-day custody
Manage the upload key like a company asset: two offline backups, two responsible people, and a periodic drill signing a build from backup. Record the fingerprint in release docs and hand it over when staff change.
Never leave the keystore in a public repo or an open share link. If leakage is suspected, reset immediately instead of waiting for trouble.
Related reading:
Related
Related desks