Play Store app installation fails on managed devices: fix missing or corrupt AFW/EMM account, then reset Managed Google Play Services via Blueprint

Android

When you try to install Google Play Store apps on your Esper-managed Android devices, the installation may fail or time out. This usually happens because the device's Android for Work (AFW) account is missing or corrupted. This article walks you through verifying and repairing the account, then resetting Managed Google Play Services to restore app installation functionality.

Before you begin

• Ensure the affected device is online and connected to a stable network (Wi-Fi or LTE).
• If you're applying Blueprint changes, resolve all validation errors (shown in red in the Esper Console) before saving.
• Allow 15 minutes for app installations to complete under normal network conditions.

How to identify if this is your issue

Your Play Store app installation is affected if:

• Apps fail to install after being approved in the Esper Console.
• The installation command times out without showing the status message Requested Google EMM to install the app on the device.
• The issue affects multiple devices simultaneously.

Step 1: Verify the device's AFW account

1. In the Esper Console, navigate to Devices & Groups → [Device Name] → Device Info.
2. Note the device serial number.
3. Contact Esper Support and provide the device serial number. Request that support verify and repair the Android for Work (AFW) account for this device.
4. Once support confirms the AFW account has been repaired, try installing the app again from Devices & Groups → [Device Name] → Apps → Install.
5. Verify the device status updates to Requested Google EMM to install the app on the device. The installation should complete within 15 minutes.

Step 2: Reset Managed Google Play Services (if Step 1 alone does not work)

1. In the Esper Console, navigate to Blueprints → [Affected Blueprint] → Platform Services.
2. Locate Control Managed Google Play Services.
3. Disable this setting, set the policy to Always Apply, then click Save & Publish.
4. Navigate to Devices & Groups → [Device Name] → Blueprint and apply the Blueprint.
5. Wait for the Blueprint convergence to complete successfully.
6. Return to Blueprints → [Affected Blueprint] → Platform Services.
7. Re-enable Control Managed Google Play Services, set the policy to Always Apply, then click Save & Publish.
8. Apply the Blueprint to the affected device again.
9. Retry the Play Store app installation and confirm the status message appears.

Troubleshooting

Blueprint save is blocked by validation errors

If you cannot resolve the validation errors shown in red, take a screenshot of the flagged fields and contact Esper Support for help.

Device goes offline during troubleshooting

Confirm the device has a stable network connection and is not in a sleep or power-saving mode that drops the network. If the device cannot stay online, it will not be able to complete the installation process.

Commands time out even after AFW account repair

If a specific device continues to fail despite AFW account verification, contact Esper Support and provide:

• Device serial number and enterprise ID.
• Timestamp of the failed installation attempts.
• Screenshot of the install command status screen (note whether the Requested Google EMM message is absent).

Multiple devices across your enterprise show the same issue

If this pattern affects many devices, there may be an enterprise-level issue with your EMM binding to Google. Contact Esper Support immediately, as this could indicate a broader device enrollment problem.

Still need help?

If you've completed these steps and app installations are still failing, submit a support ticket. Include the device serial number, the timestamp of your installation attempts, and a screenshot of the install command status screen.