Android kiosk blocks microphone and file picker in web appSolved

Participant
Discussion
5 days ago Jul 29, 2026

I have an Android device running a web app in Hexnode Kiosk mode. When Kiosk mode is disabled, the site can use the microphone and the “Select file” option works normally.

After enabling the Android Kiosk policy, the allowed camera and gallery/photos apps can be opened, but from inside the web app the microphone and file selection stop working. It looks like the web app cannot launch the Android file picker or related permission screens while kiosk is active.

Has anyone seen this with Android kiosk policies?

Replies (3)

Marked SolutionPending Review
Hexnode Expert
5 days ago Jul 29, 2026
Marked SolutionPending Review

Hi @ruthg_, this usually happens when the web app depends on Android system components that are not allowed in the kiosk policy.

In Android Kiosk mode, the OS restricts the device to the app packages explicitly allowed by the policy. If the web app tries to call another system package, such as the native file picker, permission dialog, media service, or another helper activity, that package may be blocked even though the main web app is allowed.

To confirm this:

  1. Reproduce the issue on the kiosk device by trying the microphone or file upload option.
  2. In the Hexnode portal, go to Manage > Devices and open the affected device.
  3. Go to Actions > Scanning and Monitoring > Scan Device.
  4. After the scan completes, open the Applications sub-tab.
  5. Check the Blocked Packages section.
  6. Compare the timestamps with the time you reproduced the issue to identify the relevant blocked packages.

Once identified, add those blocked package identifiers as Background Apps in the Android Kiosk policy:

Policy > Kiosk Lockdown > Android Kiosk Lockdown > Background Apps

After updating and syncing the policy, test the microphone and file picker again.

Best Regards,
Isabel Lora
Hexnode UEM

Marked SolutionPending Review
Participant
5 days ago Jul 29, 2026
Marked SolutionPending Review

I checked the blocked packages after reproducing the issue. There are several entries appearing at the same time as the file picker/microphone attempt. Some of them look like Android system activities rather than normal installed apps, so they do not show up when I try to add them directly to the kiosk policy.

Marked SolutionPending Review
Hexnode Expert
5 days ago Jul 29, 2026
Marked SolutionPending Review

If a blocked package does not appear in the app list, you can create it manually using its package identifier and then add it to Background Apps.

Use this method:

  1. Go to Apps in the Hexnode portal.
  2. Select Add App > With Bundle ID.
  3. Enter a display name for identification. The name can be anything meaningful, such as “Android file picker helper”.
  4. In the Bundle ID field, enter the exact package identifier shown under Blocked Packages.
  5. Select an appropriate category and save the app.
  6. Go back to the kiosk policy and add the newly created entry under Background Apps.
  7. Save the policy and apply it to the device.

Repeat this for each relevant blocked package that appears when the microphone or file picker action is attempted. The key is to use the exact package identifier from the device’s Blocked Packages list rather than a generic example.

Best Regards,
Isabel Lora
Hexnode UEM

Save