Android kiosk shows Access Denied when opening WhatsApp JPEG files and web linksSolved

Hello,

Thank you for reaching out to Hexnode Connect.

For Android devices in kiosk mode, this “Access Denied” error usually happens when an app tries to open a file, link, or supporting package (like a gallery viewer or system browser component) that is not explicitly allowed by the kiosk policy. Even if WhatsApp itself has the required permissions, the kiosk restrictions will still block those dependent background packages.

Here is the exact workflow to identify and allow the correct background packages:

1.Reproduce the error:

Trigger the Access Denied message on the affected device by attempting to open the JPEG or web link.

2.Scan the device:

Run a Scan Device action from the Hexnode portal immediately after reproducing the error.

3.Identify the blocked package:

Navigate to Manage > [Select the device] > Applications. Check the Blocklisted Apps section and note the bundle IDs that were blocked at the time of the error.

4.Add the package to your inventory:

Go to Apps > Add Apps, choose to add by package name or bundle ID, and add the blocked package you identified.

5.Allow as a Background App:

Go to Policies > [Your Android kiosk policy] > Android Kiosk Lockdown > Background Apps. Add the package from Local Apps, save, and sync.

Regarding your deployment of the Meta Suite apps, you must handle both the installation and the kiosk visibility. To ensure they work correctly:

• Required Apps Policy: Add the apps here so Hexnode actively installs them on the device.
• Multi-App Kiosk Policy: Add the apps here so they are visible and launchable on the kiosk screen.

(Note: Social apps rely on background packages to open links or media. You may need to repeat the blocked package troubleshooting steps above if they throw access errors).

I hope this helps you get those files opening correctly and your social apps deployed! If you find any more issues or need further assistance, feel free to reach out.

Best regards,
George,
Hexnode UEM

That makes sense. I checked the device after reproducing the issue and found several blocked packages related to the web viewer, so adding them to the Background Apps should fix it.

One other question: is there a way to make Samsung software updates install automatically while the device is managed in Hexnode?

Hello,

Hexnode does allow you to schedule Android OS updates on supported enrolled devices, but forcing deep, silent OS updates on Samsung hardware has specific prerequisites.

To fully enforce automatic Samsung software updates without user intervention, the Hexnode app typically needs to be installed as a system app. This is usually achieved through specific OEM/vendor provisioning methods during the device’s initial setup, such as Knox Mobile Enrollment (KME).

If the devices were enrolled using standard methods and the MDM agent is not a system app, your ability to force automatic software updates will be limited by Samsung’s standard OS-level restrictions, meaning the user may still be prompted to accept the update.

Best regards,
George,
Hexnode UEM