Android signing key

To publish a release build to Google Play you need to sign it with a private keystore. This is a one-time setup.

1. Generate a keystore

keytool -genkey -v \
  -keystore ~/keystore.jks \
  -alias upload \
  -keyalg RSA -keysize 2048 -validity 10000

Answer the prompts and pick a strong password. Back this file up somewhere safe — losing it means you cannot ship updates for your app on Google Play, ever.

2. Drop the keystore into the project

Copy the generated file to:

android/app/keystore.jks

That path is gitignored — the keystore never ends up in a commit.

3. Fill in the values in setup.html

Open setup.html → Customizations → Signing. Enter:

• ANDROID_KEYSTORE_STORE_PASSWORD — the store password you set.
• ANDROID_KEYSTORE_KEY_PASSWORD — the key password (usually the same as the store password).
• ANDROID_KEYSTORE_KEY_ALIAS — the alias you used above (upload in the example).

Set ANDROID_SIGNING_IS_ENABLED=true.

Save. When the sync step runs, it writes android/key.properties from these values. Gradle picks it up automatically.

Verify

Build a release AAB and confirm it's signed:

make build-aab

If the values are wrong, Gradle will fail loudly at the signing step — you never ship an unsigned or misconfigured release build by accident.