Ensure configurations according to the respective APK.
When building an APK for release, ensure the following fields are set appropriately.
Player Settings
Company Name → [CompanyName]
Product Name → [ProductName]
Version → Refer to the Version and Bundle Version Guideline below
Other Settings
Identification
Package Name → com.CompanyName.ProductName
Version → Refer to the Version and Bundle Version Guideline below
Bundle Version Code → Refer to the Version and Bundle Version Guideline below
Located in Build Settings, ensure debug settings are disabled.
Once Configurations Validated and Built
Submit APK to QA for full test pass before client handoff
For APK deliveries: Make sure to use a keystore, do NOT deploy dev-signed apps (upgrading will fail unless built using the same machine).
Version and Bundle Version Guideline
Versioning secures APKs from being downgraded or overridden.
Motive APKs
Under Project Settings > Player > Other Settings > Identification
Version
Use 0.x.x for pre-release builds
Releases to clients move up by minor number (i.e. 0.1.0 → 0.2.0)
Releases between client builds move up by build number (i.e. 0.1.0 → 0.1.1)
Use 1+.x.x for release+ builds
Bundle Version Code
For Android builds, make sure to set the Bundle Version Code. This needs to increment with every release. Utilize the following pattern: Take the Version (xx.yy.zz) and construct a Bundle Version Code (xxyyzz) with this. E.g.:
0.1(.0) = (00 01 00) = 100
0.1.2 = (00 01 02) = 102
1.0.0 = (01 00 00) = 10000
11.24.7 = (11 24 07) = 112407
Launch APKs
Under the file LaunchService\app\build.gradle
versionCode
Takes in positive integers. Every time versionName is updated, increment versionCode by 1.
versionName
Use “1+.x” notation.
If updated (either minor or major version), increment versionCode by 1.