What a keystore is
A keystore is a file that holds the private key used to sign your app. Every update must be signed by the same key, so the keystore is effectively your app’s identity. If you lose it, you may not be able to update the app in the way you expect, so treat it carefully.
Create the keystore on your phone
In Apk Converter & AAB Tools, open the keystore maker and fill in the details. Choose the PKCS12 format, a clear alias, a long and unique password, and a validity of at least 25 years.
- Alias: a short name for the key, for example upload.
- Password: long, unique, and stored in a password manager.
- Validity: 25 years or more.
- Details: your name or organisation, and country.
Back it up straight away
Copy the keystore file to at least two safe places, such as an encrypted cloud folder and an offline drive, and store the passwords separately from the file. Never send it by chat or email, and never publish it in a public repository.
If you use Play App Signing, the key you hold is the upload key, which can be reset through Play Console support if it is lost. Check Google’s current guidance for your case.
Sign the bundle
Pick your .aab file, choose the keystore, enter the alias and passwords, then start signing. The app writes a signed bundle next to the original. Keep the original unsigned file too, in case you need to sign it again.
Upload and verify
Upload the signed bundle to your release track in Play Console. If the upload is rejected, read the message: a different upload key from the one registered is the most common reason. Use the inspect tool to look at the signature details of any bundle before you upload it.
Good habits
Use one clear naming scheme for keystores, keep a short private note of which app uses which, and test the whole process on a throwaway app before doing it for a real release.
