Android enterprise app stuck at Initiated during install in HexnodeSolved

Hello @ezekiel ,

For Android Enterprise devices, an app remaining in the “Initiated” state usually means the install command has been triggered but the device has not completed or reported the installation back to Hexnode UEM.

Start by checking these items:

1. Confirm that the device has recently checked in with Hexnode UEM.
2. If the app is from Managed Google Play, open Managed Google Play on the device and confirm that the app is visible and available for that device.
3. If the app is an enterprise APK uploaded to Hexnode, verify whether the APK is a new build or the same build being pushed again.
4. Run a Scan Device action and check the app status under Manage > Device > Applications.

If this is an enterprise APK update, pay special attention to the Android ‘versionCode’. Android uses ‘versionCode’ to determine whether an APK is newer than the installed version. If the uploaded APK has the same ‘versionCode’ as the app already on the device, Android may reject it as a duplicate, and the deployment can appear stuck in an “Initiated” loop.

Regards,
Simon Scott
Hexnode UEM

The app is already in the inventory. It is an enterprise app, and we uploaded a build with the same visible version number because it was just a small change. The portal still shows the install as Initiated.

In that case, the most likely cause is that the new APK was built with the same internal ‘versionCode’ as the previous APK.

For Android app deployment, the visible version name is not enough. The APK must also have a higher internal ‘versionCode’. Both Android and Hexnode UEM rely on this value to detect an upgrade.

To resolve it:

1. Ask the app developer to increment the APK ‘versionCode’ in the app build configuration.
2. Update the ‘versionName’ as well, if needed, so the displayed version is clear.
3. Generate a new APK with the higher version values.
4. Upload the new APK to Hexnode App Inventory.
5. Push the app again to the Android devices.

Once the APK has a higher ‘versionCode’, Android will recognize it as a valid update or install package, and the deployment should move past the “Initiated” state.