App version not updating in Blueprint: remove and re-add app to force latest version fetch

Android

When a managed app in a Blueprint does not show the latest version available on Google Play, selecting the correct version to deploy is impossible until the metadata is refreshed.

Why this happens

Esper caches app metadata at the time an app is added to a Blueprint. If the app publisher releases a new version after that point, the cached metadata becomes stale and the new version does not appear in the version dropdown. Removing and re-adding the app forces Esper to pull fresh metadata from Google Play.

Steps

Open the Esper Console and navigate to Blueprints.
Select the blueprint that contains the app with the outdated version.
Open the Apps section of the blueprint and locate the app.
Remove the app from the blueprint and save the change. This clears the stale cached metadata tied to that app entry.
Re-add the same app using the app search or selector. Esper fetches current metadata from Google Play at the moment the app is added.
Open the version dropdown for the app and confirm the latest version now appears.
Select the target version, save the blueprint, and publish it to the intended devices or groups.

Verify: Navigate to Devices & Groups → [Device Name] → Apps and confirm the installed version matches the version you selected in the blueprint. The updated version should be installed within 15 minutes of the blueprint being published, provided the device is online.

If the version still does not appear after re-adding the app

Staged rollout: The app publisher may not have fully rolled out the new version on Google Play. Staged rollouts can limit availability by region or device type. Check the Play Store listing to confirm the version is broadly available.
Private or enterprise APK: If the app is not a Play Store app, re-uploading to the Esper private app repository is required. Private APK versions are not fetched from Google Play and must be managed manually through Apps & Configuration → Company Apps.

If the version appears in the blueprint but is not installing on devices

Confirm the Esper Agent is online on the target devices by checking Devices & Groups → [Device Name] → Activity Feed for recent check-in events.
Verify the blueprint was successfully applied by navigating to Devices & Groups → [Device Name] → Blueprints and reviewing the convergence status.

If this doesn't resolve it

If the version dropdown remains outdated after multiple attempts to remove and re-add the app, contact Esper Support with the following information:

Blueprint name
App name and package ID
The version number you expect to see
Screenshots of the version dropdown showing the missing version

--- **Improved title:** App version missing in Blueprint — re-add app to refresh Play Store metadata

Still need help?

If the steps above don't resolve the issue, submit a support ticket with your device model, Android version, Esper Agent version, and a description of what you've already tried — this helps the support team investigate without a follow-up.