Blueprint convergence fails with Google Play app region/compatibility error: remove or replace region-restricted apps in Blueprint

Android

When a Blueprint fails to converge and devices report a Google Play compatibility or region error, affected devices remain non-compliant and the Blueprint retries indefinitely without success.

Why this happens

Google Play enforces geographic restrictions on certain apps, preventing installation on devices outside the app's approved regions. When a Blueprint includes one of these restricted apps, the Esper Agent cannot fulfill the install instruction and convergence fails on every attempt. Removing the Play restriction is not possible from within Esper — the only resolution is to remove or replace the incompatible app in the blueprint.

Steps to resolve

1. Identify the incompatible app. In the Esper Console, go to Devices & Groups → [Device Name] → Blueprint → Compliance Status. Look for the error message:
   
   Couldn't install Google Play App(s). Check compatibility and region requirements for the app and device.
   
   The app name causing the failure is listed in the error detail (for example, Phone Dialer by Google). Note the exact package name or app title.
2. Confirm the app is region-restricted. Open Google Play in a browser and search for the app by name or package ID. If the app does not appear in results or displays as unavailable in your country, it is region-restricted and cannot be installed on devices in that region regardless of Blueprint configuration.
3. Edit the blueprint to remove or replace the app. In the Esper Console, go to Blueprints → [Blueprint Name] → Edit Blueprint → Apps. Remove the incompatible app from the app list. If the app's functionality must be preserved, use one of the following alternatives:
   • Add a different Google Play app confirmed to be available in your devices' region.
   • Upload a private APK through Apps & Configuration and add it to the blueprint instead. This bypasses Google Play region enforcement entirely.
   Save and publish the updated blueprint.
4. Re-apply the blueprint to affected devices. Go to Devices & Groups → [Your Group] → Blueprint → Apply Blueprint. Applying the updated blueprint pushes the corrected app list immediately and clears the pending convergence error.

Verify: Within 10–15 minutes of applying the updated blueprint, all affected devices should show Blueprint: Compliant with no convergence errors in Devices & Groups → [Device Name] → Blueprint → Compliance Status.

If this doesn't resolve it

If convergence still fails after removing the identified app, the blueprint may contain additional region-restricted apps. Repeat the steps above for each app listed in the compliance error. If only one app is listed but convergence continues to fail after 24 hours, a temporary Google Play propagation delay may be the cause — wait 24 hours and re-apply the blueprint before investigating further.

If the issue persists beyond 24 hours with no clear app-level cause, collect the following before contacting support:

• The exact error message from Devices & Groups → [Device Name] → Activity Feed
• The blueprint name and the package names of all apps included in it
• The affected device model, Android version, and registered device region
• Device logs collected via ADB:

  adb shell logcat -d -v time > esper_agent_logs.txt

  Filter the output for Blueprint and PackageInstaller entries.

Contact Esper Support with the above information for further investigation.

Still need help?

If you're still encountering Blueprint convergence errors after removing region-restricted apps, submit a support ticket and include your device's region settings, the specific app names causing the error, and your Blueprint configuration details.