Play Store version shown in Esper Blueprint differs from installed version on device: understanding version identifiers

Android

Title: Play Store version in Blueprint differs from device — version code vs. version name

When you add a Google Play app to a Blueprint and compare the version shown in the Esper Console against the public Play Store listing or the version installed on a device, the numbers often do not match.

Why this happens

Android apps carry two separate version identifiers: a version name (the human-readable string such as 4.7.9 shown on the public Play Store) and a version code (an internal integer Android uses to manage updates). Esper receives app metadata from the Managed Google Play API, which may surface a different version string than the public Play Store listing. Separately, if an app auto-updates on a device after you assign it in a blueprint, the installed version can advance beyond what the blueprint currently shows.

Steps

1. Confirm the app's distribution source. In the Esper Console, go to Apps & Configuration → App Catalog and locate the affected app. Check whether it is listed as a Play Store app or an Enterprise App (a manually uploaded APK). Both can exist in your catalog simultaneously and are tracked independently — version numbers between the two are not directly comparable.
2. Note the version your blueprint is targeting. Go to Blueprints → [Blueprint Name] → Apps and find the app. The version string shown here reflects what the Managed Google Play API last reported to Esper and is the version that will be enforced on newly provisioned or re-synced devices.
3. Check the version actually installed on the device. Go to Devices & Groups → [Device Name] → Apps and locate the app. The version displayed here is what is running on that device and is the authoritative record of what is installed.
4. Compare against the public Play Store listing. Visit play.google.com and search for the app. If the version name there differs from what the Esper Console shows, this is expected. App developers sometimes publish under a different version name in the managed enterprise track than in the public consumer track. What matters is that the correct build is reaching your devices, not that the version strings match exactly.
5. Refresh app metadata if the Blueprint version appears stale. Go to Apps & Configuration → App Catalog → [App Name] and select the refresh or sync option if available. This pulls the latest metadata from Managed Google Play. If no refresh option is present, remove the app from the blueprint and re-add it from Managed Google Play to force a fresh metadata pull. This step is only necessary if you believe devices are not receiving the latest release.
6. Review version distribution across your fleet. Go to Apps & Configuration → App Catalog → [App Name] and open the version breakdown view to see how many devices are running each version. Use this to confirm the intended version has propagated to the devices you expect.

Verify: After refreshing metadata and re-syncing, go to Devices & Groups → [Device Name] → Apps and confirm the installed version matches the build you intended to deploy. The version string displayed in the blueprint and on the device may still differ in label while referencing the same underlying build — this is normal and requires no further action.

If this doesn't resolve it

If devices are consistently installing an unexpected version, or if the App Catalog shows no refresh option and the blueprint version appears significantly out of date, contact Esper Support. Before reaching out, collect the following:

• The app package name (for example, com.example.appname)
• The version string shown in the blueprint
• The version string shown under Devices & Groups → [Device Name] → Apps
• The version shown on the public Play Store listing
• Screenshots of the App Catalog entry and the device app list

Still need help?

If you're still seeing version mismatches between Esper Blueprint and your device after reviewing the differences between Play Store, system, and app versions, please submit a support ticket and include the specific version numbers shown in Blueprint, your device's system settings, and the Play Store listing.