Hi @cameron,
If you are editing the existing app entry in Hexnode and uploading the new APK there, the Hexnode-side app deployment workflow is correct.
For Android APKs, whether an app can be updated in place is enforced by the Android OS. Android will block an in-place update if the new APK does not meet these requirements:
- The package name must be identical:
The installed app and the new APK must use the exact same package name/application ID, for example com.example.app.
- The
versionCode must be higher:
Android checks the integer versionCode inside the APK, not just the display version name. The new APK must have a versionCode that is strictly higher than the version currently installed on the device.
- The APK must be signed with the same keystore:
The updated APK must be signed with the same signing certificate/keystore as the version already installed.
If all three conditions are met, Android should allow the app to upgrade in place and preserve the existing app data. After your developer confirms these values, upload the new APK by editing the existing app under Apps tab in Hexnode and let the Required App policy deploy the update.
Regards,
Sienna Carter
Hexnode UEM