Google Play Store prompts sign-in despite Managed Google Play enabled in Blueprint

Android

If your device prompts you to sign in to Google Play Store even though your blueprint has Control Managed Google Play Services enabled, this article walks you through troubleshooting steps. This is typically a device-specific account binding issue.

Before you begin

Verify that your device is enrolled under a blueprint with Control Managed Google Play Services enabled. If multiple devices use the same blueprint and only one shows the sign-in prompt, the issue is likely device-specific rather than a configuration problem.

Step 1: Create a test blueprint

1. In the Esper Console, go to Blueprints.
2. Click Create Blueprint and give it a name (for example, Test - Play Store Access).
3. Under Platform Services, enable Control Managed Google Play Services.
4. Add Google Play Store as the only application in the blueprint.
5. Save and publish the blueprint.

Step 2: Apply the test blueprint to your device

1. Go to Devices & Groups and select your device.
2. Open the Blueprint tab.
3. Select your test blueprint and apply it.
4. Wait for the device to fully converge (you'll see a confirmation in the Esper Console).

Step 3: Test Google Play Store access

1. On your device, open Google Play Store.
2. Check whether a sign-in prompt appears.
3. If no prompt appears, the issue is resolved. You can now apply your production blueprint.

Step 4: Re-provision your device if the prompt persists

If Google Play Store still prompts for sign-in, the device may have a corrupted managed account binding. The most reliable fix is to wipe and re-provision:

1. Go to Devices & Groups, select your device, and open Actions.
2. Click Factory Reset (or Wipe + Remove if you plan to re-enroll).
3. Re-enroll the device using your original provisioning method.
4. Apply your production blueprint.
5. Open Google Play Store and verify that no sign-in prompt appears.

Troubleshooting with ADB commands

If re-provisioning does not resolve the issue, you can use Android Debug Bridge (ADB) to check your device's account and Play Store state:

Check managed account status:

adb shell dumpsys account

A managed account (typically marked with @managedprovisioning or your enterprise domain) should appear. If only a personal Google account is present or no managed account exists, the device's account binding may be broken.

Check Google Play Store package state:

adb shell pm list packages | grep vending
adb shell dumpsys package com.android.vending | grep -i "userId\|state\|install"

The Play Store package should be installed and enabled. If it shows as disabled or has errors, reinstalling it may help.

Compare with a working device:

Run the same ADB commands on a device that works correctly with your blueprint. Compare the account entries and package states between the two devices to identify differences.

Still need help?

If none of these steps resolve the issue, contact Esper Support. provide:

• Your device model and Android version.
• Your Esper Agent version (found in Devices & Groups → Device Details → Agent Version).
• Output from the ADB commands above (from both the affected and a working device, if available).
• Screenshots showing the sign-in prompt on your device.