Play Store app not installing via Blueprint

Android

When a Play Store app is included in a Blueprint but fails to install on enrolled devices, the app appears in your Blueprint configuration yet never reaches the device—even after the Blueprint reports successful convergence.

Why this happens

Blueprint convergence confirms that the Esper Agent received and applied your configuration—it does not confirm that every app installed successfully. App installation depends entirely on the app being accessible through the managed Google Play account linked to your Esper enterprise. If the app vendor has not published the app to managed Google Play, or has not approved your specific account for private distribution, the Play Store will silently block the install regardless of your Blueprint settings.

Step 1: Confirm the app is accessible in your managed Play Store

Open the Esper Console and navigate to Apps & Configuration → Play For Work.
Search for the affected app by name or package ID (e.g. com.example.appname).
If the app does not appear in search results, your managed Google Play account cannot access it. No Blueprint change or re-apply will resolve this—proceed to Step 2.
If the app does appear, skip to Step 3.

Step 2: Contact the app vendor to resolve access

Contact the app vendor and ask them to confirm all of the following:
- The app is published and available on managed Google Play, or has been privately approved for your organization.
- The app is not region-restricted or limited to specific device types that exclude your hardware.
- If private distribution is required, the vendor must approve your managed Google Play Organization ID through the Google Play Console.
Retrieve your managed Google Play Organization ID to provide to the vendor if requested: in the Esper Console, go to Company Settings → Managed Google Play and copy the Organization ID shown there.
Once the vendor confirms access has been granted, return to Apps & Configuration → Play For Work and search for the app again to confirm it now appears before continuing.

Step 3: Re-apply the Blueprint after vendor confirmation

In the Esper Console, navigate to Apps & Configuration → Play For Work and confirm the app is now visible in search results.
If the app is not already part of your Blueprint, add it: go to Blueprints, open the relevant blueprint, add the app under the Apps section, and save the blueprint.
Apply the updated blueprint to the affected devices or group by navigating to Devices & Groups → [Device or Group Name] → Blueprint → Apply.
Allow up to 15 minutes for the Esper Agent to process the command and for Google Play to deliver the app to the device.

Verify: Navigate to Devices & Groups → [Device Name] → Apps and confirm the app status displays as Installed. You can also confirm on the device itself by checking the app drawer or Settings → Apps.

App is visible in the Console but still fails to install

If the app appears in the Play For Work search but installation continues to fail, the issue is likely on the device itself. Check the following:

Confirm the device is online: in Devices & Groups, the device status must show Online.
Verify the device has sufficient free storage—Google Play requires enough space to download and unpack the APK.
Confirm the app is compatible with the device's Android version and processor architecture (arm64 vs x86). Check the app's supported devices list in the Google Play Console with your vendor if needed.
Collect device logs to identify the specific install error. Run the following via ADB:
```
adb shell logcat -s PackageManager:E AndroidRuntime:E *:S
```
Alternatively, request a bug report directly from the Esper Console by navigating to Devices & Groups → [Device Name] → Actions → Request Bug Report. This generates a full device diagnostic you can review for Play Store error codes.

Multiple apps failing across multiple Blueprints

If no Play Store apps are installing on any device and none appear in the Apps & Configuration → Play For Work search, your managed Google Play account binding may be expired or misconfigured. This affects all app installs enterprise-wide and requires account-level remediation.

If this doesn't resolve it

If the app is confirmed accessible in managed Google Play, the Blueprint has been re-applied, and installation still fails, contact Esper Support with the following information:

The package ID of the affected app (e.g. com.example.appname)
The device serial number or Esper device ID
A screenshot of the app status in Devices & Groups → [Device Name] → Apps
The bug report or ADB logcat output collected in Step 3
Confirmation from the app vendor that your Organization ID has been approved

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.