Skip to content

App Build, Signing, and Release ​

Build, install, and run a package for the target platform in a test environment before production signing and distribution. A successful browser launch does not verify native dependencies, permissions, or upgrades.

1. Before You Start ​

ItemDetails
Entry pointOpen the mobile project in HBuilderX and select the native target for the delivered version
PermissionsAccess to build tools, signing or distribution accounts, and a physical device for the target
What to prepareSource commit, tool version, application ID, app version, service environment, and last known working version

2. Verify Platforms and Signing ​

TargetBefore buildingBefore delivering
AndroidPackage name, version, signing identity, and native permissionsVerify clean installation and upgrade with the same signing identity through an approved distribution channel
iOSBundle ID, signing configuration, privacy information, and distribution accountVerify installation and upgrade through the deployment owner's authorized channel on a target device
HarmonyOSApplication package name, signing, and target permissions; check HarmonyOS configurationVerify on a physical device with the delivered HarmonyOS toolchain. Do not reuse the Android upgrade entry point

3. Build and Verify ​

  1. Check the target API, MQTT service, application ID, and version as described in Source Code, Environment, and API Configuration. Build a test package first, and record its source, environment, and target.
  2. On a physical device, verify first installation, startup, login, device viewing, live connectivity, and permission prompts. For provisioning, camera, or BLE, verify what happens both when access is granted and when it is declined.
  3. Verify the upgrade from the previous delivered version. In the current source, Check for Updates queries the server version and takes different paths on Android and iOS. Verify the actual download URL or store entry. An H5 download page does not verify a native upgrade.
  4. Sign the production package only after acceptance. Record the version, distribution channel, release notes, and rollback conditions. Keep signing materials in authorized environments and out of docs and general build logs.

3.1. Test Clean Installation and In-place Upgrade with the Same Candidate ​

ScenarioStepsPass criteria
First installationInstall the candidate on a test phone that can be cleared, read the policy at startup, then sign in with a test accountThe app points to the intended environment; login, the device list, and device details work
Upgrade from the previous versionInstall the previous delivery and sign in. Keep app data and upgrade through the actual distribution channelThe app starts afterward. Expected state is retained, and any required sign-in is clearly prompted
Permission deniedDeny one relevant permission on the target device, check the prompt, then restore access through the operating systemThe affected feature gives a clear prompt without blocking unrelated viewing workflows

Record each phone's OS version, installation source, and versions before and after upgrade. Uninstalling the previous package skips in-place upgrade issues and does not count as a passing upgrade test.

4. Verify the Upgrade Method ​

The V2 App Version Management guide is a reference for version records and acceptance checks. It does not imply the same WGT hot update support in the current release. Rebuild and retest a full native package when plugins, permissions, or signing change. Verify resource updates against the delivered base app and target platform.

Release Gate

Verify clean installation, upgrade, login, key device workflows, and clear failure messages. Keep a signature-verified previous package or another tested rollback plan.

Next: Frontend-Backend Version Compatibility.