Android multi-app kiosk apps not showing until installed firstSolved

Hello @jaxon_r ,

For Android multi-app kiosk, the apps added to the kiosk policy must already be installed on the device before kiosk mode is applied. Adding an app to the kiosk layout does not automatically install it.

Use this deployment order:

1. Create or use an app installation policy, such as a Required Apps policy, to deploy the required apps to the Android devices.
2. Make sure the devices are online, unlocked, and able to complete app installation.
3. Confirm that the apps are visible in the device’s installed applications list.
4. After the apps are installed successfully, associate the multi-app kiosk policy with the devices.

If the kiosk policy is applied before the apps are installed, the apps may not appear in kiosk mode because they are not present on the device.

Regards,
Simon Scott
Hexnode UEM

In my case, app installation was also getting stuck while the device was already restricted. Does the Play Store need to be allowed somehow for installs or updates?

We had a similar issue with a communication app in kiosk. The app opened but crashed right away because one of its helper packages was blocked by the kiosk restrictions.

That can happen with apps that depend on additional packages or background services.

If an app crashes only after kiosk mode is enabled, check whether the app requires dependent packages, services, or companion components to run. Those dependent packages should be added to the Background Apps section of the kiosk policy as well.

For example, if a two-way radio or communication app depends on additional packages, add each required package separately to the app repository if needed, then include them as background apps in the kiosk policy. This allows the main kiosk app to launch while its required background components continue running.