Managed Google Play app approval shows wrong app version / approved app not available in Blueprints

Android

When an organization publishes the same app across multiple Managed Google Play tracks (Alpha, Beta, Production), the wrong track can become approved in the Esper Console, causing an incorrect app version to appear or the correct Production app to be missing entirely from Blueprint app selection.

Why this happens

Managed Google Play treats each track (Alpha, Beta, Production) as a separate app entry. If an earlier track was approved before the Production track was published, that track remains the approved version. The Esper Console cannot approve a second track while another is already approved, and attempting to unapprove a track that is still referenced by a Blueprint returns an internal server error.

Fix the wrong app version or missing app in Blueprints

1. Open the Esper Console and navigate to Apps & Groups → Apps → Managed Google Play. Search for your app using the developer name or a unique keyword.
2. Browse the Other apps by [Developer] section to view all available tracks. Note which track is currently marked as approved and confirm whether it matches your intended Production app.
3. If you need to unapprove the incorrect track, first remove it from every Blueprint that references it. Navigate to Blueprints → [Blueprint Name] → Apps, remove the app entry, then save and publish the Blueprint. Repeat this for every affected Blueprint. Skipping this step causes an internal server error when you attempt to unapprove.
4. Check whether any Blueprint uses group-level app overrides that may still hold a reference to the app. Navigate to Blueprints → [Blueprint Name] → Apps and expand any group-level override sections to confirm the app is fully removed at all levels.
5. Return to Apps & Groups → Apps → Managed Google Play and unapprove the incorrect track.
6. Locate the correct Production track app and select Approve. This makes the Production version available for use in Blueprints.
7. Navigate to Blueprints → [Blueprint Name] → Apps → Add App and confirm the Production app now appears as a selectable option. Add it to the Blueprint, then save and publish.

Verify: The correct Production app should appear in the Blueprint app list immediately after approval. When you publish the Blueprint and apply it to a device, the device should install the Production track version. Confirm the installed version in Devices & Groups → [Device Name] → Apps.

If this doesn't resolve it

If the Production app still does not appear in Blueprint app selection, or the device continues to receive the wrong track after the Blueprint is applied, contact Esper Support with the following information:

• Your Esper Console environment name
• The exact package name for each app track
• Your Managed Google Play enterprise ID
• The names of all affected Blueprints
• A screenshot or screen recording showing the current approval state in Apps & Groups → Apps → Managed Google Play

Still need help?

If you're still experiencing issues with app version mismatches in Managed Google Play or app availability in Blueprints, please submit a support ticket and include the app name, the version shown during approval, and the version available in your Blueprints.