Android kiosk apps crash after switching kiosk policySolved

Participant
Discussion
1 month ago Sep 09, 2026

Several Android devices assigned to a kiosk policy suddenly couldn’t open two apps, including a driver app. The apps would start to open and then immediately close with a message saying the app could not open and had to close.

It affected more than one device, including a demo device. I didn’t see an access denied message. I moved the devices back to an older kiosk policy and, after some time, the apps started working again. Could this have been a kiosk policy sync delay, or is there something else I should check before trying the newer policy again?

Replies (1)

Marked SolutionPending Review
Hexnode Expert
1 month ago Sep 09, 2026
Marked SolutionPending Review

Hello @lila_ace ,

This behavior can occur if the devices are still processing a recent kiosk policy change or if the active kiosk configuration does not yet match the app access expected on the device.

Since the apps started working again after the devices were moved back to the older kiosk policy, the most likely cause is that the devices either had not fully synchronized the newer policy yet or the newer kiosk policy contained a difference that affected how those apps were launched.

For this scenario, try the following when moving devices back to the newer kiosk policy:

  1. Assign the new kiosk policy and allow a short sync window before testing the apps.
  2. Confirm that the required apps are included in the kiosk policy and are allowed to run in kiosk mode.
  3. If the apps still close immediately, restart the device and test again after the policy refresh completes.
  4. If production devices are affected, temporarily reassign the last known working kiosk policy to restore access while comparing the old and new policy settings.

The key point is to avoid repeatedly switching policies too quickly, as the device may need time to apply the kiosk configuration cleanly.

Regards,
Simon Scott
Hexnode UEM

Save