Play Store version shown in Esper Blueprint differs from installed version on device: version name vs. version code mismatch in Managed Google Play

Android

When you add an app from Google Play to an Esper Blueprint, you may notice that the version number displayed in Esper differs from the version shown on the public Google Play Store, or from the version installed on your devices. This article explains why this happens and how to verify you have the correct version deployed.

Understanding version discrepancies

Android apps use two different version identifiers that can cause confusion:

• Version name — a human-readable version string (for example, 4.7.9) shown on the public Google Play Store listing and in most user interfaces.
• Version code — an internal number used by Android and Google's Managed Google Play API for update management.

Esper pulls version information from the Managed Google Play API, which may display a different version string than the public Play Store listing. Additionally, if an app auto-updates on your device after you assign it in a Blueprint, the installed version may be newer than what the Blueprint shows.

Before you begin

Determine whether the app is distributed from Google Play or uploaded as an enterprise app in Esper. These are tracked separately and may show different version numbers.

Step 1: Confirm the distribution source

1. In the Esper Console, go to Apps → App Catalog.
2. Locate the affected app.
3. Check whether it is listed as a Play Store app or an Enterprise App (manually uploaded APK).
4. If both versions exist in your app library, verify that your Blueprint references the intended source.

Step 2: Check the version in your Blueprint

1. Go to Blueprints → [Blueprint Name] → Apps.
2. Find the app and note the version string displayed.
3. This version reflects what Managed Google Play last reported to Esper.

Step 3: Check the installed version on your device

1. Go to Devices & Groups → [Device Name] → Apps.
2. Locate the app and view the installed version.
3. The version shown here is what is actually running on the device and is the authoritative record.

Step 4: Refresh the app metadata (if needed)

If the version shown in your Blueprint is outdated, you can refresh the metadata from Managed Google Play:

1. Go to Apps → App Catalog → [App Name].
2. Look for a sync or refresh option. If available, select it to pull the latest metadata from Managed Google Play.
3. Alternatively, remove the app from the Blueprint and re-add it from Managed Google Play to force a fresh metadata pull.

Step 5: Verify against the public Play Store

1. Visit play.google.com and search for the app.
2. Compare the version name shown on the public listing with what Esper displays.
3. If they differ, this is expected behavior. Developers sometimes use different version names in the enterprise track versus the public store.
4. What matters most is that your devices are receiving and installing the correct build. The version string discrepancy is cosmetic and requires no action on your part.

Step 6: View version distribution across devices (optional)

To see how many of your devices are running each version of an app:

• Go to Apps → App Catalog → [App Name] and look for a Version Distribution option (available in some Esper plans).
• Alternatively, export your device list from Devices & Groups and filter by app version.
• You can also use the Esper API endpoint GET /v1/enterprise/{enterprise_id}/device/ with app filter parameters to programmatically retrieve installed versions across your device fleet.

Still need help?

If you are unable to resolve the version discrepancy or have questions about which version your devices should be running, contact Esper Support.