We have an Android 14 device running in Hexnode multi-app kiosk mode with our main warehouse app allowed. The app has camera permission on the device, and the native camera app is also added to the kiosk policy.
Outside kiosk mode, the camera works. Inside kiosk mode, the app throws an “access denied” message when trying to open the camera. Has anyone seen this on Android 14? I’m not sure what else needs to be allowed if both the app and camera app already have access.
53 Views
Hello @gnishilda ,
In multi-app kiosk mode, camera access can fail if the app depends on another system component to launch the camera workflow. Allowing only the main app and the native camera app may not always be enough.
A good way to identify the missing component is to reproduce the issue and then check the blocked packages reported by the device:
If a system package or activity appears there, it should be explicitly added to the kiosk policy as an allowed/background app, depending on how the policy is configured.
We checked the blocked packages after reproducing it. The entry showing up is: ‘com.android.intentresolver.ChooserActivity’. The native camera app itself was already in the policy, so this was a bit unexpected.
The camera launch flow may invoke Android’s intent resolver/chooser component, and kiosk mode can block it unless it is explicitly allowed.
Add ‘com.android.intentresolver.ChooserActivity‘ to the Hexnode UEM portal as an app with Bundle ID, then add it to the kiosk policy.
Reassociate the policy to the device. After that, test the camera action again from the managed app.
On Android 14, some camera-related behavior that may have worked under default kiosk allowances on older Android versions can require explicit permission in the kiosk policy. So, if the native camera app is already allowed but access is still denied, the blocked packages list is the best place to confirm what else needs to be added.
Regards,
Simon Scott
Hexnode UEM
Don't have an account? Sign up
What's new 
