Blueprint convergence stalls at Managed Google Play app installation — EMM re-registration resolves on some devices
Android
Title: Blueprint convergence stalls on Managed Google Play app install — re-register EMMWhen a Blueprint is applied to a device, convergence stalls indefinitely during the Managed Google Play app installation phase and the affected apps never reach an installed state.
Why this happens
Each Android device must maintain an active registration with Google's managed app infrastructure (EMM registration) before it can receive and install Managed Google Play apps. If that registration becomes degraded or incomplete — due to a interrupted enrollment, a Google Play Services update, or a connectivity gap during provisioning — the Esper Agent sends installation commands that Google Play silently drops, causing convergence to hang.
Before you begin
Collect the following before proceeding:
- Device name or serial number
- Blueprint name currently applied
- Package names of the apps that are not installing (see Step 2)
Steps
-
Confirm convergence is stalling at the Managed Google Play phase.
Navigate to Devices & Groups → [Device Name] → Activity Feed and review the entries. Look for a Blueprint convergence command acknowledged by the device, followed by Managed Google Play installation requests with no corresponding installation completion events. If the Activity Feed entries are inconclusive, navigate to Devices & Groups → [Device Name] → Actions, select Request Bug Report, download the report, and search it for installation timeout entries. -
Identify the specific package names blocking convergence.
In the bug report or Activity Feed logs, note the exact package names that are not installing. Common examples include:-
com.openvpn.openvpn(OpenVPN Connect) -
com.google.android.apps.nbu.files(Files by Google) -
com.android.chrome(Chrome) -
org.mozilla.firefox(Firefox) -
com.opera.browser(Opera)
-
-
Check EMM registration status on the device.
Navigate to Devices & Groups → [Device Name] → Device Info and confirm the device is shown as EMM-registered in the Esper Console. On the device itself, open the app list and verify that both Google Play Protect and Android Device Policy are present and not showing errors. Any error state on either of these indicates a degraded EMM registration. -
Clear Google Play Store and Google Play Services data to re-establish EMM registration.
This forces both services to re-initialize their managed app state without requiring a factory reset. Connect to the device via ADB and run the following commands:
Then reboot the device:adb shell pm clear com.android.vending adb shell pm clear com.google.android.gms
Allow the device to fully restart and reconnect to the network before proceeding.adb reboot -
Reapply the Blueprint to re-trigger convergence.
Once the device is back online, navigate to Devices & Groups → [Device Name] → Blueprint, select the Blueprint currently assigned to the device, and apply it. This sends a fresh convergence command so the Esper Agent reattempts installation of the previously blocked Managed Google Play apps.
Verify: Navigate to Devices & Groups → [Device Name] → Blueprint → Convergence Status. The status should transition from Pending to In Sync within 10–15 minutes of reapplying the Blueprint. All previously blocked apps should appear as installed under Devices & Groups → [Device Name] → Apps.
If this doesn't resolve it
If convergence continues to stall after re-registering EMM and reapplying the Blueprint, collect the following and contact Esper Support:
- The bug report downloaded in Step 1
- The device serial number and Esper device ID (visible under Devices & Groups → [Device Name] → Device Info)
- The Blueprint name and a list of the blocking package names identified in Step 2
- Screenshots of the Convergence Status screen showing the stalled state
Still need help?
If you continue to experience blueprint convergence issues or Managed Google Play app installation failures after attempting EMM re-registration, please submit a support ticket with your device serial numbers, the specific apps failing to install, and details about when the convergence stalled.
Please sign in to leave a comment.
Comments
0 comments