Android Signing Keystore
Every Android app must be digitally signed before it can be distributed. A keystore file contains the signing key that proves the app comes from you. Appilix generates a keystore automatically when you create your app, but if your app is already published on Google Play, you must use your original keystore to keep updates consistent.
New Apps
If your app has not been published before, no action is needed. Appilix generated a keystore when your app was created. That keystore will be used for all your builds and Play Store submissions automatically.
Keep a secure backup of this keystore. Losing it without Play App Signing enabled can permanently prevent you from publishing updates.
Apps Already Published on Google Play
If your app is live on Google Play and was not originally built with Appilix, you must upload the same keystore that was used for all previous releases. Using a different keystore will cause Google Play to reject your update with a signature mismatch error.
Upload your existing keystore and enter the correct credentials:
Keystore File
Upload your .jks keystore file. Only .jks format is supported.
Store Password
The password that protects the keystore file.
Key Password
The password for the signing key inside the keystore. This is often the same as the Store Password.
Alias
The alias (key name) used when the keystore was generated. Must match exactly.
App Build Scheme
Choose the processor architecture the build targets:
| Option | Description |
|---|---|
| 64-bit | Smaller file. Works on all modern Android devices (most devices since 2019). |
| 32 & 64-bit | Larger file. Required for older devices using 32-bit processors, such as some Android Go devices. |
If users report that the APK installs but will not open, check whether their device uses a 32-bit processor and switch to the 32 & 64-bit scheme.
SHA-1 and SHA-256
These fingerprints are generated automatically when a keystore is uploaded. They are read-only and frequently required when setting up Firebase, Google APIs, or Google Play services. Copy them from here when needed.
Lost Your Keystore?
If your app is already live on Google Play and you have lost the original keystore, you can request an upload key reset through Google Play Console — but only if Play App Signing is enabled for your app.
Steps to reset the upload key:
- Download the PEM certificate file from your Appilix dashboard.
- Log in to Google Play Console.
- Open your app and go to Test and release → App integrity → App signing.
- Scroll to Upload key certificate and click Request upload key reset.
- Select the reason (e.g., lost upload key) and upload the PEM file.
- Submit the request.
- After Google approves the reset, update your keystore settings in Appilix and rebuild.