Building and Publishing
Android Signing Keystore
Generate or upload the release key used to sign APK and AAB files, preserve it for updates, and use its fingerprints for integrations.
Before you start
- Final package name
- A secure place to back up key material and passwords
Configure and verify
Choose generated or existing key
For a new app, let WebToAppMaker generate a JKS. For an existing Play app, upload the exact original JKS with matching store password, key password, and alias.
Save credentials
The dashboard stores the uploaded key reference and visible credential values needed by the worker. Restrict dashboard and server access accordingly.
Verify fingerprints
After valid credentials are saved, review SHA-1 and SHA-256. Use SHA-1 for Google OAuth/Firebase integrations and SHA-256 for Android App Links as required.
Choose architecture scheme
Select 64-bit only or both 32-bit and 64-bit compatibility based on release requirements.
Back up the key
Download the JKS and store it with passwords and alias in an encrypted backup separate from the build server. PEM is available for upload-key reset requests.
Build and inspect
Create a release and verify its certificate matches the expected key before Play upload.
Play App Signing
Google Play can re-sign distributed APKs. Direct APK tests use the upload/dashboard key fingerprint, while Play-installed builds may use the Play App Signing certificate fingerprint. Register both where external APIs require them.
Key loss
Test before release
- JKS backup exists
- Passwords and alias are recorded securely
- SHA fingerprints are registered with integrations
- Release is signed with the expected certificate