Play Store app install times out ("Queued" → "Timed Out"): recreate AFW account via Blueprint to restore Managed Google Play installs

Android

If Play Store app installations are timing out on your devices, you can fix this by recreating the Android for Work account through your Blueprint settings. This article walks you through the troubleshooting steps.

Understand the problem

When you push a Play Store app to a device from the Esper Console, the installation command may remain in a Queued state for an extended period before transitioning to Timed Out without completing. This typically affects multiple devices simultaneously. However, manually uploaded APKs install successfully on the same devices.

This issue occurs when the Android for Work (AFW) account on the device is corrupted or missing. Without a valid AFW account, your device cannot authenticate with Managed Google Play, so Play Store apps cannot be delivered. Manually uploaded APKs bypass the Play Store pipeline entirely and work normally.

Step 1: Reboot the device

Start by rebooting the affected device to clear any stale command queue states.

1. In the Esper Console, go to Devices & Groups → [Device Name].
2. Click Actions → Reboot.
3. Wait for the device to restart.
4. Retry the app install after the reboot completes.

If the install succeeds, you're done. If the installation still times out, proceed to Step 2.

Step 2: Recreate the AFW account via Blueprint

Toggling the Control Managed Google Play Services setting forces your device to tear down and re-establish the Managed Google Play account. Follow these steps:

1. In the Esper Console, go to Devices & Groups → Groups → [Your Group Name].
2. Find the Blueprint assigned to this group and click Edit.
3. Navigate to Platform Services.
4. Disable the toggle for Control Managed Google Play Services.
5. Click Save and Publish.
6. Click Converge and wait for convergence to complete successfully on your affected device(s).
7. Open the Blueprint again and click Edit.
8. Re-enable the toggle for Control Managed Google Play Services and set the enforcement mode to Always Apply.
9. Optionally, enable Google Play Store visibility on the device temporarily to verify Play Store is accessible.
10. Click Save and Publish.
11. Click Converge again and wait for convergence to complete.

Verify the fix

After convergence completes successfully, test a Play Store app install:

1. Go to Devices & Groups → [Device Name] → Apps.
2. Push a Play Store app install command.
3. Confirm the command transitions from Queued → In Progress → Success.

A successful Play Store installation confirms that the AFW account has been re-established.

If the issue persists

Try these additional troubleshooting steps:

• Device lacks Google Play Services: Non-GMS (AOSP) devices or devices from manufacturers that ship without Google Play Services cannot install Play Store apps. Instead, upload the APK directly to Esper by going to Apps → Private Apps → Upload APK, then push the private app version to your device.
• Network issues: If timeouts persist after a reboot, test the device on a different network (for example, a personal hotspot) to rule out firewall or proxy interference.
• Collect device logs: If the issue persists after toggling the AFW setting twice, collect logs from your device using the Esper Console: go to Devices & Groups → [Device Name] → Actions → Collect Logs. You can also collect logs via ADB by running adb logcat -d | grep -i "Esper Agent\|esper\|afw\|play".

Still need help?

If these steps do not resolve the issue, contact Esper Support and include the device logs you collected. Our support team can investigate further and help restore Play Store installations on your devices.