Devices stuck in drift after Blueprint app update: Managed Google Play enrollment failure requiring reprovisioning

Android

Title: Devices stuck in drift after Blueprint update — Managed Google Play enrollment fix

When a Blueprint app update is applied and a device's Managed Google Play enrollment is degraded, the device enters drift and displays the error Couldn't install Google Play App(s), preventing convergence even after the Blueprint is correctly configured.

Why this happens

Each device maintains a binding to your enterprise's Managed Google Play account. If that binding becomes corrupted — due to interrupted provisioning, a Play Store service disruption, or an incomplete prior factory reset — the Esper Agent cannot install Play-managed apps on the device's behalf. A reboot clears transient faults; if the error persists, only reprovisioning fully restores the enrollment.

Before you start

Check how many devices are affected. A small number of devices in drift often converge on their own once network connectivity stabilises. Only proceed with the steps below if affected devices remain in drift for more than 60 minutes after the Blueprint update was applied.

Step 1: Confirm the exact error

1. Go to Devices & Groups and select the affected device.
2. Open the Blueprint tab and review the convergence status details.
3. Confirm the error message reads exactly: Couldn't install Google Play App(s). If a different error is shown, these steps may not apply and you should contact Esper Support.
4. Check that the app is available for the device's Android version, hardware architecture, and region in your Managed Google Play console. A misconfigured or regionally restricted app will cause the same error and reprovisioning will not resolve it.

Step 2: Reboot the device

1. Go to Devices & Groups and select the affected device.
2. Open the Actions menu and select Reboot. A reboot clears temporary Play Store session faults without data loss and should always be attempted first.
3. Wait 30–60 minutes, then return to the Blueprint tab and check convergence status.
4. If the device shows as compliant with no convergence errors, no further action is needed.

Step 3: Factory reset and reprovision

If the device remains in drift after the reboot, the Managed Google Play enrollment must be rebuilt through reprovisioning.

1. Go to Devices & Groups and select the affected device.
2. Open the Actions menu and select Factory Reset. This removes the corrupted enrollment binding so a clean one can be established during reprovisioning.
3. Once the device completes the factory reset, reprovision it using your standard method:
   • QR code
   • Zero-Touch Enrollment
   • Knox Mobile Enrollment
4. Apply the current Blueprint to the device during reprovisioning so apps are installed as part of the fresh enrollment.

Verify: In Devices & Groups, the device should show as Compliant within 30 minutes of completing reprovisioning. Open the Blueprint tab and confirm all apps show as installed with no convergence errors.

If the device re-enters drift after reprovisioning

If the same device drifts again immediately after reprovisioning, or if multiple devices fail on the same Blueprint app, the issue is likely with the app configuration rather than the device enrollment. Check the following:

• App availability: In your Managed Google Play console, confirm the app is approved and published for your enterprise binding, and is available in the device's region.
• Package name: In Apps & Configuration, verify the package name in the Blueprint matches the exact package name of the app in Managed Google Play.
• Play Store propagation: Newly published or updated apps can take up to 24 hours to propagate across all Play Store regions. If the app was recently published, wait 24 hours and retry convergence.
• Device storage: Confirm the device has sufficient free storage to install all apps defined in the Blueprint.
• Network access: Verify the device can reach Google Play endpoints and has a stable internet connection during convergence.

If this doesn't resolve it

If reprovisioning does not resolve the drift, or if more than a handful of devices are affected simultaneously, contact Esper Support. When you reach out, provide the following:

• The device serial number or Esper device ID for each affected device
• The name of the Blueprint applied and the specific app package name shown in the error
• A screenshot of the convergence error from the Blueprint tab
• The Activity Feed entries for the affected device, covering the period from the Blueprint update to the time of the error
• Confirmation of whether the issue affects one device or multiple devices on the same Blueprint

Still need help?

If your devices remain stuck in drift after reprovisioning, please submit a support ticket and include your Blueprint version, the specific app update that triggered the issue, and your device enrollment method.