App Auto-Update Stuck in "Pending" State: Check Managed Google Play Services Blueprint Setting

Android

Improved Title: App updates stuck in Pending — fix Managed Google Play Blueprint setting

---

When app updates are pushed to managed Android devices, the updates remain in a "Pending" state indefinitely and never progress to downloading or installing, even after device reboots or network changes.

Why this happens

The Control Managed Google Play Services setting in a Blueprint determines how long Esper maintains authority over the Managed Google Play layer. When this is set to Enforce only during provisioning, Esper's control lapses as soon as enrollment completes. Without that persistent control, update and install commands sent from the Esper Console are acknowledged and queued, but the Play Services layer never executes them.

Steps to fix

1. Open the Esper Console and navigate to Blueprints.
2. Select the blueprint applied to your affected devices and click Edit.
3. Navigate to Platform Services within the blueprint editor.
4. Locate the Control Managed Google Play Services setting and change it from Enforce only during provisioning to Always Apply. This ensures Esper retains ongoing control over Managed Google Play after enrollment, so update commands can be executed at any time.
5. Click Save and publish the updated blueprint.
6. Navigate to Devices & Groups, select the affected devices, and click Actions → Converge to push the updated policy to the devices.
7. Reboot the affected devices once Converge completes. This clears any queued state and lets the updated policy take full effect.

Verify: Open Devices & Groups → [Device Name] → Apps and confirm the app version has advanced to the latest published version. No "Pending" entries should remain in the Activity Feed within 10 minutes of the reboot.

If this doesn't resolve it

• Try a manual install: Go to Devices & Groups → [Device Name] → Apps and trigger a manual install for the app. Watch the Activity Feed to see whether the command moves beyond Acknowledged or Queued.
• Check the managed Google account: On the device, confirm the EMM-managed work account is set as the default account. If multiple Google accounts are present, Managed Google Play may route requests through the wrong account, blocking updates.
• Check device convergence state: In Devices & Groups, confirm the device is not showing drift. If it is, run Actions → Converge again and wait for the device to reach a fully converged state before re-testing updates.

If the issue persists after completing all steps above, contact Esper Support with the following information: the device serial number, the blueprint name and version, and a screenshot of the Activity Feed showing the stuck commands.

Still need help?

If the steps above don't resolve the issue, submit a support ticket with your device model, Android version, Esper Agent version, and a description of what you've already tried — this helps the support team investigate without a follow-up.