Blueprint Converge triggers full uninstall/reinstall of managed apps, wiping local app data

Android

When you trigger a Blueprint Converge on a device group, Esper may uninstall and reinstall managed apps whose installed version does not match the version defined in your blueprint — permanently deleting those apps' local data, including saved accounts, cached content, and offline files.

Why this happens

Blueprint Converge enforces an exact match between the device state and your blueprint definition. When Esper detects a version mismatch — most commonly because an app auto-updated through Google Play outside of Esper's control — it uninstalls the mismatched version before reinstalling the blueprint version. Unlike a direct app deployment through Apps & Configuration, this uninstall-then-reinstall cycle does not preserve app data.

Before triggering a Blueprint Converge

Check for version drift across your device group. Navigate to Devices & Groups → [Group] → Apps and compare the installed app versions against the versions defined in your blueprint. Any app showing a version that differs from the blueprint is at risk of being uninstalled during Converge.
Update your blueprint to match currently installed versions. In your blueprint, go to the Apps section and update each managed app entry to reflect the version currently installed on your devices, or explicitly pin the version you want enforced going forward. This eliminates the mismatch before Converge runs, so no uninstall is needed.
Prevent future version drift by restricting Google Play auto-updates. In your blueprint's app settings, set the app update policy to Esper-managed only, or configure managed Google Play restrictions to block automatic updates. This ensures apps can only be updated through Esper, keeping device state aligned with your blueprint between Converge operations.
Notify end users to back up critical app data if you cannot resolve the version mismatch before converging. Ask users to re-authenticate accounts, export local documents, or take any other steps needed to preserve data they cannot afford to lose.
Test the Converge on a single device before rolling out to the full group. Navigate to Devices & Groups → [Group] → Blueprint → Converge Now and select one representative device. After Converge completes, go to that device's Apps tab and confirm all managed apps show the correct version and an Installed status. Then check the device's Activity Feed and confirm no uninstall events appear. Only proceed to the full group if the test device shows no unexpected uninstalls.

Use Apps & Configuration for ongoing app updates

When your goal is to update or deploy apps — rather than enforce a full blueprint state — use Devices & Groups → [Group] → Apps & Configuration → Install/Update instead of triggering a Blueprint Converge. This performs an in-place update that preserves all app data and does not risk uninstalling apps with version mismatches.

Verify: After a successful Converge, every managed app on the target devices should show the correct version and Installed status under Devices & Groups → [Group] → Apps, and the Activity Feed for each device should contain no uninstall events for managed apps.

If this doesn't resolve it

If apps are still being uninstalled during Converge after aligning blueprint versions, collect the following before contacting support:

The exact app name, package name, blueprint version, and installed version for each affected app
Esper Agent logs from an affected device: navigate to Devices & Groups → [Device] → Actions → Request Esper Agent Logs
A screenshot or export of the device's Activity Feed showing the uninstall events and their timestamps
The name and version of the blueprint used during the Converge

Contact Esper Support with this information so the uninstall behavior can be investigated.

Still need help?

If you're experiencing app data loss after Blueprint Converge operations, submit a support ticket and include the specific apps affected, your Blueprint configuration details, and the timeline of when the data loss occurred.