Auto Launch does not fire after fresh app install (uninstall + reinstall): manual Blueprint Converge required as workaround

Android

Title: Auto Launch stops after app reinstall — trigger Blueprint convergence to restore

When an app configured for Auto Launch is uninstalled and reinstalled on a managed device, the app does not relaunch automatically after the reinstall completes.

Why this happens

Auto Launch is enforced by Blueprint convergence, not by the install event itself. When an app is reinstalled outside of a full convergence cycle — for example, through a manual reinstall or an in-app update — the Esper Agent does not re-evaluate the Auto Launch instruction. The behavior restores as soon as convergence runs again.

Before you begin

Confirm that Auto Launch is enabled for the app in the Blueprint applied to this device. Navigate to Blueprints → [Blueprint Name] → Apps & Configuration, select the app, and verify the Auto Launch toggle is on. If it is off, enable it and save the Blueprint before continuing.

How to restore Auto Launch after reinstall

Open the Esper Console and navigate to Devices & Groups.
Locate and select the affected device.
Open the Actions menu and select Converge. This forces the device to re-evaluate its Blueprint and re-apply all settings, including Auto Launch instructions.
Confirm the convergence operation when prompted.
Wait for convergence to complete. Monitor the device status in the Activity Feed until it returns to Compliant.
Observe the device screen to confirm the app launches automatically without any user interaction.

Verify: The device should show a Compliant status in Devices & Groups within a few minutes of convergence completing, and the app should launch on its own without a user tapping it.

If Auto Launch is also failing after Esper Agent updates

The same behavior can occur when the Esper Agent updates itself on a device. If a managed app closes during an agent update and does not relaunch, use the same convergence steps above to restore Auto Launch.

If this doesn't resolve it

If the app still does not launch automatically after the device reaches Compliant status, collect the following before contacting Esper Support:

A bug report captured immediately after the failed launch: Devices & Groups → [Device Name] → Actions → Bug Report.
Esper Agent logs pulled via ADB:
```
adb shell logcat -d -s EsperAgent
```
The Esper Agent version installed on the device, found under Devices & Groups → [Device Name] → Device Info.

Providing these logs at the time of contact allows the support team to investigate the exact point at which the Auto Launch instruction was dropped.

Still need help?

If the steps above don't resolve the issue, submit a support ticket with your device model, Android version, Esper Agent version, and a description of what you've already tried — this helps the support team investigate without a follow-up.