Access denied error in Android kiosk mode when opening contacts on Samsung deviceSolved

Yes. When an Android kiosk policy blocks an app or background service, you can use the device scan results to identify the blocked package. Try the following:

1. Go to Manage > Devices and open the affected device.
2. Click Actions > Scanning & Monitoring > Scan Device.
3. Open the Action History sub-tab and confirm that the Scan Device action completed successfully.
4. After the scan succeeds, go to the Applications sub-tab.
5. Check Blocked Packages and compare the timestamp with the time when the Access denied message appeared.
6. Copy the relevant blocked package name.

Once you have the package name:

1. Go to Apps > + Add Apps.
2. Choose Upload as Bundle ID.
3. Enter a suitable app name and category.
4. Add the blocked package name as the Bundle ID and save it.
5. Go to Policies and open the kiosk policy applied to the device.
6. Navigate to Kiosk Lockdown > Background Apps.
7. Add the newly created Bundle ID app to Background Apps.
8. Save the policy and confirm from Action History that the updated policy is associated with the device.

This should allow the required background package while keeping the device in kiosk mode.

I tried running Scan Device, but it sat there for several minutes. The device was right next to me and connected to Wi-Fi. Is it normal for the scan to take that long?

The scan usually completes quickly when the device has a stable internet connection and is actively checking in with the portal. However, the completion time can vary depending on network connectivity and device check-in behavior. If the device has checked in recently, it is usually best to wait for the action to complete, then verify the result in Action History. The Blocked Packages list should be reviewed only after the Scan Device action shows as successful.

The scan eventually changed to Success. I checked the Blocked Packages list using the timestamp from when the Access denied message appeared, then added those package names as Bundle IDs and included them under Kiosk Lockdown > Background Apps.

That helped identify what was missing from the kiosk policy.