Android multi-app kiosk keeps reinstalling old sideloaded APK after updateSolved

Participant
Discussion
9 hours ago Sep 25, 2026

We’re updating a sideloaded APK on Android devices in multi-app kiosk mode. The app vendor changed how the APK is signed, so installing the newer build over the older one fails with an app conflict unless the old version is removed first.

My original rollout was:

1. Remove the app from Required Apps, blocklist, app catalog, and multi-app kiosk lockdown policies.

2. Add the newer APK to the relevant app groups.

3. Push a manual uninstall from the Manage tab.

4. Run an app scan and confirm reports show the old version removed.

5. Re-add the app through app group deployment.

The confusing part is that reports showed the old version was removed, but the action history showed “Uninstall failed application not present on device”. Once I re-added the app, the old version appeared again on a large number of devices.

The “Remove app from device on policy removal” option under Required Apps was enabled. Is there a better way to update a sideloaded APK in multi-app kiosk without the old version coming back?

Regards,
Mary Romero

Replies (1)

Marked SolutionPending Review
Hexnode Expert
29 minutes ago Sep 25, 2026
Marked SolutionPending Review

This behavior can occur when the app is referenced in more than one policy payload, especially when a sideloaded APK is used in a multi-app kiosk configuration.

A few points explain the symptoms:

– If “Remove app from device on policy removal” is enabled, removing the app from the policy can trigger removal from the device.

– The message “Uninstall failed application not present on device” may appear if the device has already removed the app by the time the uninstall command is processed.

– If an older APK is still referenced in an active app group, Required Apps configuration, or multi-app kiosk app entry, the next policy sync can attempt to push that older package again.

– With sideloaded APKs, Hexnode cannot always treat an update the same way as a managed store app update, especially if the newer APK conflicts with the currently installed package due to signing or packaging changes.

For multi-app kiosk deployments, use the managed Play Store app entry in the kiosk policy wherever possible, so the kiosk app reference is based on the app’s package/bundle identity rather than a specific uploaded APK file.Then control the APK version through Required Apps or the app group used for deployment. Before rolling this out widely, test it on a small pilot group.

Regards,
Mary Romero

Save