Updates need the same key
An installed app accepts an update only when the new build has the same signature. Changing the key blocks the update.
Signing guide
Android and iOS only install apps that carry a valid signature. This guide explains why, then shows how to add a signing credential to html2app and assign it to a project.
iOS builds are planned and not available yet. Android builds are live now.
01 Why signing
Your build is only a bundle of files until a key signs it. The signature does two jobs: it proves the author, and it proves the file was not changed after signing.
Signed and verified. The device accepts the install.
An installed app accepts an update only when the new build has the same signature. Changing the key blocks the update.
Any change to a signed file breaks its signature, so the store and the device reject the file.
Whoever holds the key can publish updates as you. Store the keystore and its passwords in a safe place.
02 Android and iOS
Android
iOS (planned)
03 In html2app
Credentials live in two places. The credentials page stores them, and each project chooses which one to use for each platform and build type.
Open app.html2app.dev/credentials. Upload your Android keystore, or your iOS certificate and provisioning profile, then enter its details and passwords.
Open your project, then go to its settings page.
Under Signing Credentials, pick a credential for each platform and method, then select Save Settings.
Start a build. html2app signs the output with the credential you assigned for that method.
Example only. The names of your credentials will differ.
Stored credentials are encrypted. You can delete them from the credentials page at any time. Under the current terms, stored credentials expire after one year. See the Terms of Service.
04 Video
TODO: embed the YouTube video here.
05 Keep your keys safe
Keep a copy of every keystore and iOS certificate outside html2app, for example in a password manager or encrypted drive.
A lost keystore password cannot be recovered. Store it with the keystore.
Build with test credentials and re-sign the download locally with your production keys. The re-signing guide covers both platforms.
06 FAQ
Android installs only signed APK and AAB files. The signature proves that an update comes from the same developer as the installed app.
With Google Play App Signing, you can register a new upload key with Google Play. Without that, updates signed with a different key are rejected. Keep backups.
No. You can build with test credentials and re-sign the downloaded build locally with your production keys.
Not yet. iOS builds are planned. The iOS options appear in the app so you can prepare credentials in advance.