Android KIOSK policy not working
After upgrading the MDM Server to version 3.3, the KIOSK policy failed to display installed applications for devices enrolled in version 3.2 due to a missing "statusReportingSettings" parameter in custom policies. Adding this parameter with "applicationReportsEnabled": true and redeploying the policy resolves the issue, ensuring installed applications are correctly shown in the WebUI.
Problem
After upgrading the MDM Server to version 3.3, the KIOSK policy is not working, specifically the "Installed Applications" are not displaying for devices enrolled in version 3.2.
Root Cause of the Problem
The custom KIOSK policy did not include the parameter "statusReportingSettings". This
parameter, with `"applicationReportsEnabled": true`, is necessary for installed
applications to be reported and displayed in the WebUI.
Note: This issue does not occur if the policy is created directly from the Kiosk policy page in MCM
version 3.3 or later, because the necessary parameters are automatically
included.
Resolution
- Add `statusReportingSettings`: Ensure that the following JSON snippet
is included within your custom policy, typically within the main policy
configuration
block:
"statusReportingSettings": { "applicationReportsEnabled": true } - Save and Deploy the Updated Policy: Save the changes to your custom KIOSK policy template. Then, deploy or re-deploy this updated policy to all relevant devices (both newly enrolled and existing ones) that are intended to use this KIOSK policy.