Hi @cullen,
In Android Enterprise kiosk mode, any app, package, or system activity that is not explicitly allowed by the kiosk policy can be blocked. This includes system components such as the Android photo picker and secondary browser activities launched by a web app.
For photo upload from a kiosk web app, check the following:
- Allow the photo picker or gallery component
- If the blocked package/activity appears as “com.android.photopicker.MainActivity”, add the relevant photo picker package to Hexnode first if it is not already listed.
- Go to Apps > Add App > With Bundle ID and add the package shown by the device.
- Then go to Policies > Kiosk Lockdown > Android Kiosk Lockdown > Background Apps and add it there.
- Allow Chrome correctly
- If Chrome needs to open in the foreground, add Google Chrome to Multi-App Kiosk as an allowed app.
- If Chrome is only needed silently in the background, add it under Background Apps instead.
- An app cannot be configured as both a Multi-App Kiosk app and a Background App in the same policy. If it does not appear in the Background Apps list, check whether it is already selected under Multi-App Kiosk.
- Grant media/storage permissions
- Go to Policies > Android > App Management > App Permissions.
- Set the required storage/media permissions to Grant for the browser or web app handling the upload.
- Use package names, not activity names, where possible
- The blocked list may show an activity such as “org.chromium.chrome.browser.document.ChromeLauncherActivity”.
- For policy configuration, add the actual Chrome app/package as shown in Hexnode or the Play Store, rather than only the activity name.
Policy changes are pushed automatically after saving. Running Scan Device does not force a policy update, but it is useful for verifying whether the packages are still listed as blocked after the policy syncs.
Regards,
Sienna Carter
Hexnode UEM
What's new 
82 Views
