Kiosk app does not auto-launch on power-on: set app install type to "Always Apply" in Blueprint

Android

If your Kiosk app isn't launching automatically when your Android device powers on, the issue is likely that the app's install type is set to "Provision Only" instead of "Always Apply" in your Blueprint. This article explains how to fix this.

Why your Kiosk app isn't auto-launching

When you add an app to a Blueprint and configure it as your Kiosk app, Esper needs to enforce that app's launch behavior every time the device boots. If the app's install type is set to "Provision Only", it installs during initial device setup but isn't re-enforced after power cycles. This breaks the auto-launch behavior you expect from Kiosk Mode.

To guarantee your Kiosk app launches automatically on every boot—including after power cycles—you must set the app's install type to "Always Apply".

How to fix this

1. In the Esper Console, go to Blueprints and open the Blueprint assigned to your affected devices.
2. Find the Kiosk app in the Blueprint's app configuration section.
3. Change the app's install type from "Provision Only" to "Always Apply".
4. Click Save, then click Publish.
5. Once published, select your affected device group (or individual devices) and click Converge. This pushes the updated Blueprint configuration to your devices.
6. Power cycle one or more devices and verify the Kiosk app launches automatically at startup without requiring a manual tap.

Before you begin

Make sure:

• The Blueprint you're modifying is correctly associated with your affected device group. You can verify this in the group settings.
• You publish the Blueprint after making changes—saving alone doesn't push the configuration to devices.
• The Converge action completes successfully. Check device status in the Esper Console to confirm the Blueprint sync completed.

If the app still doesn't auto-launch

Check the following:

• App permissions: Some apps require additional permissions (such as overlay or autostart permissions) that may not be granted through the Blueprint alone. Check whether your Kiosk app has any special permission requirements for your device's OEM.
• App startup behavior: Confirm the app itself doesn't have delayed-start behavior that prevents it from launching immediately after boot.
• Device status: Verify no devices are stuck in a pending or failed Blueprint sync state.

If the issue persists across multiple devices and power cycles after trying these steps, contact Esper Support and include:

• Your Blueprint name
• Your device group name
• Esper Agent version from the affected devices
• Esper Agent logs (run adb shell logcat -b all -d > dpc_logs.txt and attach the file)

Still need help?

If you're still experiencing issues or have questions about Blueprint configuration, submit a support ticket. Our team is here to help.