Multi app kiosk(Android) shows "access denied" after policy is appliedSolved

Participant
Discussion
3 months ago Mar 08, 2026

I am running into a frustrating issue with a custom application. The app works completely normally outside of kiosk mode, but as soon as I apply an Android Multi App Kiosk policy through Hexnode, the app opens and immediately throws an “Access Denied” error.

Here is my current setup:

  • App installed through Hexnode.
  • Android Multi App Kiosk policy created and assigned.
  • App added to the kiosk allowed apps list.
  • Runtime permissions enabled with “Grant Android 10+”.

Since the runtime permissions are already being explicitly granted by the policy, what else could be causing the app to lock up and show “Access Denied” when kiosk mode is active?

Replies (1)

Marked SolutionPending Review
Hexnode Expert
3 months ago Mar 08, 2026
Marked SolutionPending Review

Hi @sarahmiller,

This usually happens when your primary app depends on additional Android packages or helper services that are being suffocated by the kiosk policy.

Runtime permissions and kiosk package access are handled completely separately. Runtime permissions allow the app to access hardware features like the camera, storage, or microphone. However, if the app relies on another hidden background package for authentication, web views, or SDK components, the strict kiosk environment will block that secondary package, resulting in the “Access Denied” error.

You can find and whitelist these missing dependencies using these steps:

  1. Go to the Manage tab in your Hexnode UEM portal.
  2. Select the affected Android device and run the Scan Device action.
  3. Open the Applications sub-tab for that device.
  4. Filter it by Blocklisted Apps to see exactly what the kiosk just stopped from running.
  5. Copy those package names and add them to your kiosk policy under Android > Kiosk Lockdown > Background Apps.
  6. Save and reapply the policy.

Allowing those dependencies as background apps gives your main app the services it needs to function, without exposing the background packages to the user.

I hope this helps get your app running smoothly!

Best regards,
Eden Pierce
Hexnode UEM

Save