Signing and your keystore
What signing means, why you own the key, and how to keep it safe.
Updated October 1, 2026 · 1 min read
Android requires every app to be signed. The signature proves that updates come from the same publisher, which is why Google Play refuses an update signed with a different key.
How ApkZio signs
On your first build ApkZio generates a keystore for that app with a 25-year validity, signs the APK and AAB with it, and offers the keystore and passwords for download. Every rebuild of the same app uses the same key.
Play App Signing
When you first upload the AAB, Play Console enrols the app in Play App Signing. Google keeps the app signing key and your ApkZio key becomes the upload key. That is the normal, recommended setup; you still need your keystore to sign each upload.
Bring your own keystore
If you already have a keystore from a previous app, upload it on the Review step with its passwords. ApkZio uses it instead of generating one.
Keep it safe
- Store the keystore and passwords in a password manager or encrypted backup.
- Do not share it publicly or commit it to a public repository.
- If it is lost after ApkZio’s retention period, Play App Signing lets you request an upload-key reset with Google.