Play Store app install during provisioning causes device to stall: change install timing to post-provisioning

Android

If your device stalls during provisioning when installing Google Play Store apps, you can fix this by changing the install timing to "Post Provisioning" in your Blueprint. This article explains why this happens and how to resolve it.

Why Play Store apps cause provisioning to stall

When you configure a Blueprint to install a Google Play Store app (such as OpenVPN) during provisioning, the device may become stuck because the Google Play Store itself may not be fully initialized yet on the device. The device waits for the Play Store installation to complete before advancing to the next provisioning step, which prevents it from completing provisioning and appearing in your Esper Console.

To avoid this timing issue, Google Play Store apps should always be installed after provisioning completes, when the Play Store is ready to fulfill installation requests.

How to fix this

In the Esper Console, navigate to Blueprints and select the relevant Blueprint.
Locate the app entry for the Google Play Store application you want to install.
Change the install timing setting from "During Provisioning" to "Post Provisioning".
Save and publish the updated Blueprint.
For future provisioning runs, use the updated Blueprint. Test on a device to confirm the new timing setting resolves the issue.

If your device is currently stuck

If a device is still stuck during provisioning and has not yet appeared in Devices & Groups:

Allow additional time for the in-progress installation to complete. The device will eventually register in the Esper Console once the Play Store fulfills the pending installation request. This may take 15–20 minutes or longer.
Do not interrupt the device or factory reset unless it has been unresponsive for an extended period.

If the device remains stuck for more than 15–20 minutes and still does not appear in Devices & Groups:

Factory reset the device.
Re-provision it using the updated Blueprint with "Post Provisioning" timing already configured.

Best practices for Play Store apps

Always set Google Play Store apps to install "Post Provisioning," regardless of the type of app.
Private or enterprise APKs that you upload directly to Esper are not subject to Play Store initialization timing and may be installed during provisioning without this issue.
Verify that your device has a stable internet connection during and after provisioning.
Confirm that the Google account associated with your Managed Google Play has the app approved and distributed.

Still need help?

If your device continues to fail provisioning even with "Post Provisioning" timing set, or if Play Store apps consistently fail to install, contact Esper Support.