Provisioning stuck on "Awaiting installation of 1 app from Google Play": resolve by adjusting Launch on Start and installation timing settings

Android

If your Android devices are stuck on a screen that says "Awaiting installation of 1 app from Google Play" during provisioning, you can resolve this by adjusting your blueprint's app installation settings. This article walks you through the fix.

Before you begin

This issue typically occurs when a blueprint contains an app that is configured with both of the following settings:

Installation rule: During Provisioning
Launch on Start: Enabled

If Google Play fails to install the app during the provisioning window (due to connectivity issues, Play Store delays, or app availability), your device will wait indefinitely and never complete provisioning.

How to fix provisioning stuck on app installation

In the Esper Console, navigate to Blueprints.
Find the blueprint assigned to your affected devices.
Click the blueprint name, then select Actions → Clone Blueprint. This creates a safe copy without changing your live blueprint.
Open the cloned blueprint and go to the Apps section.
For every app that has Launch on Start enabled, toggle it to Disabled.
Optionally, you can change the Installation rule to Post Provisioning for these apps. If you need Launch on Start enabled later, you must keep the installation rule as During Provisioning—the Esper Console will reject other combinations.
Click Save and Publish the cloned blueprint.
Factory reset each affected device that is stuck in the provisioning loop.
Re-provision your devices using the updated cloned blueprint.
Once provisioning completes successfully, you can re-enable Launch on Start on the desired apps by editing the blueprint again. Save and publish the changes—the apps will install and configure during Blueprint convergence.
Verify that your devices appear as Online in Devices & Groups, assigned to the correct blueprint, with convergence status showing Applied.

Verify the fix worked

Navigate to Devices & Groups and check each device:

Device status shows Online
Device is assigned to your updated blueprint
Convergence status shows Applied (not Pending or Failed)

If convergence is still failing

Device shows as Offline: Blueprint commands require your device to be online. Navigate to Devices & Groups → [Device Name] → Overview and check the connectivity status. Bring the device online—the pending convergence command will execute automatically.

Validation error when editing the blueprint: Make sure you are not combining Launch on Start: Enabled with Post Provisioning on the same app. Disable Launch on Start first, then change the installation rule.

Issue persists across multiple devices: If Play Store installation consistently stalls across different devices and networks, contact Esper Support. This may indicate an issue with your Play Store entitlement or managed Google Play account.

Still need help?

If you've followed these steps and your devices are still stuck in provisioning, submit a support ticket. Include the affected device names, blueprint name, and a screenshot of the provisioning screen.