Android multi-app kiosk app install stuck on Initiated after adding app to policySolved

For Android multi-app kiosk devices, first confirm that the app deployment is not being blocked by the kiosk configuration. Check the following:

1. Open the applied kiosk policy.
2. Go to Android Kiosk Lockdown > Background apps.
3. If the app is being installed from Managed Google Play or the Play Store, make sure Play Store is added as a background app in the kiosk policy.
4. Save the policy and make sure it is associated with the affected device.
5. On the device page, check Compliance Info to confirm which required apps are missing.
6. Open Action History and check the status of the app installation action.

If the device shows the app install action as Initiated or Pending for a long time, also check Enrollment details > Work account creation. If work account creation has failed, retry it and then trigger the app install again.

Adding Play Store under Background apps helped on one of the phones. The app installed and the kiosk updated there. But another phone is still stuck. Work account creation now shows successful, I scanned the device from the portal, and the action history refreshes, but the install action is still sitting at Initiated. Same kiosk policy is applied to the working phone and the stuck one.

If the same policy and app configuration work on other devices, and the affected device has a successful work account but the install action remains stuck at Initiated, temporarily disabling the kiosk policy on that device can help. Recommended sequence:

1. Remove or disable the kiosk policy from the affected device.
2. Wait for the device to exit kiosk mode and sync.
3. Confirm whether the pending app installation proceeds.
4. Once the required apps are installed, reapply the same kiosk policy.
5. Scan the device again and verify Compliance Info.

This is useful when the kiosk state is preventing the device from completing the required app installation even though the app and policy configuration are correct.