App not installing on specific devices: publish Blueprint and trigger converge

Android

If an app isn't installing on specific devices even though it's been added to your Blueprint, the issue is likely that your Blueprint hasn't been published yet. This article walks you through publishing your Blueprint and triggering a converge operation to deploy the app to your devices.

Before you begin

Make sure you have:

• Access to the Esper Console with permissions to manage Blueprints and devices
• The serial numbers of the affected devices
• Confirmed that the app has been added to the Blueprint (but not yet published)

How to publish your Blueprint

1. In the Esper Console, navigate to Blueprints.
2. Find the Blueprint assigned to your affected devices.
3. Confirm that the app you want to install is listed under Apps in the Blueprint configuration.
4. Click Publish. The Blueprint status should change from draft to published.

How to trigger a converge operation

1. Navigate to Devices & Groups.
2. Select the affected devices by their serial numbers.
3. Click Converge to push the published Blueprint configuration to the devices.
4. Wait for the converge operation to complete. The time required depends on device connectivity and app package size.

How to verify the app installed

1. In the Esper Console, navigate to Devices & Groups.
2. Select each affected device.
3. Confirm the device is no longer in Drift status.
4. Check the Apps section to confirm the app is now listed as installed.

Troubleshooting

The app still isn't installed after converge completes:

• Check the device's app install logs. Navigate to Devices & Groups → [Device Name] → Events/Logs and look for any install failure codes.
• If your device is not enrolled with a managed Google Play account, you cannot install apps from the Play Store through Esper. Instead, upload the app as a private APK through the Esper Console and add it to your Blueprint.

The converge operation is taking a very long time:

• Check your device's internet connectivity. Good signal strength doesn't always mean a stable MDM connection.
• If the converge appears stuck despite good connectivity, contact Esper Support with your device serial numbers, the converge job ID, and recent device event logs.

Important to remember: A Blueprint must be published before converge will have any effect. Triggering converge against a draft Blueprint will only sync your devices to the last published version—any draft changes will be ignored.

Still need help?

If you've completed these steps and your app still isn't installing, submit a support ticket and include your device serial numbers, the app name, and any error messages from your device logs.