Enrollment blocked for a Blueprint group due to delisted/removed Google Play apps in Blueprint configuration

Android

If devices in a specific Esper group fail to enroll and you see enrollment blocked at the app installation phase, the issue may be caused by Google Play Store apps in your Blueprint that are no longer available. This article explains how to identify and fix this problem.

Understand the issue

When you apply a Blueprint to a group, the Esper provisioning process attempts to install all apps configured in that Blueprint — including apps from Google Play. If one or more of those apps have been delisted or removed from the Play Store, the device cannot complete enrollment and remains stuck.

This issue affects only devices enrolling against the affected Blueprint. Other groups using different Blueprints continue to enroll normally.

Before you begin

• Verify that enrollment failures are limited to devices in one specific group. If multiple groups are affected, the issue may be different.
• Ensure you have permission to edit the Blueprint applied to the affected group.

How to identify delisted apps in your Blueprint

1. In the Esper Console, navigate to Blueprints.
2. Open the Blueprint applied to the affected group.
3. Go to the Apps section and review all Google Play Store applications listed.
4. For each app, search for it manually in the Google Play Store using the package name or app name. If you cannot find an app, it has likely been delisted or removed.
5. Note the package names of any apps that are unavailable.

How to fix the issue

1. In the affected Blueprint's Apps section, delete each app entry for apps you identified as unavailable in the previous section.
2. Save and publish the updated Blueprint.
3. Navigate to Devices & Groups → [your group] → Blueprint and reapply the corrected Blueprint.
4. Attempt to enroll a test device against the corrected Blueprint.
5. Verify that enrollment completes successfully and the device reaches a managed state in the Esper Console.

If enrollment still fails

• Check for additional unavailable apps: Audit all Google Play Store app entries in your Blueprint. There may be more than one delisted app. Repeat the manual search process for every app listed.
• Collect logs for further investigation: If the Blueprint appears correct but enrollment still fails, collect device logs using adb logcat or request a bug report from the device to identify where the enrollment process fails.
• Blueprint is locked or not editable: If the Blueprint cannot be edited from the Esper Console, contact Esper Support to have the invalid app references removed directly.
• Multiple groups are affected: If enrollment is failing for groups using different Blueprints, this suggests a broader issue. Contact Esper Support with details about all affected groups.

Still need help?

If you've removed unavailable apps from your Blueprint and devices still cannot enroll, submit a support ticket. Include the Blueprint name, affected group name, and the package names of any apps you removed.