What's new 
I enrolled a Samsung Android tablet and created a Single App Kiosk policy for testing. The policy uses Google Maps as the kiosk app and also sets a custom background. The background applies and the device enters kiosk mode, but the only app shown is Google Chrome instead of Google Maps. I tried creating another kiosk policy with a different app and saw the same behavior. In the device compliance details, I noticed a missing app count of 1. Does that mean kiosk apps are restricted during evaluation, or is there something wrong with my policy setup?
31 Views
Replies (1)
Marked SolutionPending Review
Hexnode Expert
59 minutes ago
Jul 27, 2026
Marked SolutionPending Review
This is not a trial limitation. Hexnode trial portals support Android kiosk mode and app deployment functionality.
The missing app count is the key indicator here. It means the device has received a policy that expects a specific kiosk app, but the app has not been installed or made available to the device successfully. When an Android device enters Single App Kiosk mode but cannot launch the configured kiosk app, it may fall back to an available app such as Chrome instead of opening the intended app.
For Android Enterprise devices, the kiosk app should be approved and distributed through Managed Google Play so that Hexnode can install and manage it correctly.
Try the following:
- Login to Hexnode UEM and navigate to Apps Tab.
2. Click Add Apps.
3. Select Managed Google Play app.
4. Search for the required app.
5. Approve and add the app to the app repository.
6. Edit the kiosk policy and select the app from the Hexnode app repository.
7. Add the same app under Mandatory Apps in the policy so it is pushed to the device automatically.
8. Save and reapply the policy.
Once the app installs successfully and the missing app count changes to 0, the Single App Kiosk policy should launch the selected app instead of Chrome.
Regards,
Mary Romero
Save