Android Builds
The keystore file is used to securely and uniquely sign your app binary, so that e.g. other apps can't pretend to be an update for your app. For example, submitting an update to Google Play requires that the new app binary has been signed with the same keystore file as the original build.
To generate a keystore file, the easiest way is to use the Javakeytool (you need install JDK for this).
Note that using JDK 16 to generate the keystore file seems to cause build failures. Please use JDK 15 instead!
Run the following command in your Terminal or Command Prompt (replacing my-app-name appropriately) .
keytool -genkey -v -keystore my-app-name.keystore -alias my-app-name -keyalg RSA -keysize 2048 -validity 10000
You then need to input a password required to use the keystore. The owner, city etc. data are not necessary, but you can fill them in if you want. You ca enter a separate password for the alias, but that's not necessary either. In Composer on the Keystore tab, you have the following fields:
Keystore file – your
my-app-name.keystorefile is uploaded hereKeystore password – enter the password you gave when generating the keystore
Keystore alias – enter the keystore alias (
my-app-namein the above example)Keystore alias password – unless you set a separate alias password, this is the same as Keystore password
This setting defines the unique package identifier for your binary APK package. It must be in reverse domain format, e.g. com.appgyver.myapp.production.
This is the name for your app shown under the app icon in the device home screen, as well as in settings and other places.
On the Build Settings page you can choose a runtime version and set the version properties for the build.
Internal version code for the app, given as an integer, e.g. 10000. When you publish an update to your app in Google Play, its version code must be higher than previous version codes.
Semantic version name for the current build, e.g. 1.0.0. Shown in device settings and other places.
Check out this guide.
