Blueprint converge reports success but app version is not updated on device

Android

When a Blueprint converges successfully in the Esper Console but the app version specified in that blueprint is not installed or updated on the device, the device continues to run the old version despite the console reporting no errors.

Why this happens

A successful Blueprint convergence confirms that Esper delivered the desired-state configuration to the device, but individual sub-commands — including app installs — are queued and executed separately. If the device was offline at the moment the blueprint was applied, or came online after the convergence window closed, app install commands can remain in a queued state indefinitely without triggering a convergence failure.

Steps to resolve

1. Check the app install command status. Navigate to Devices & Groups → [Device Name] → Activity Feed and locate the app install command issued during the Blueprint convergence. Note the status:
   • Queued — the command has not yet reached the device
   • Success — the command completed; verify the version in the next step
   • Failed — the command encountered an error; the reason is shown inline
2. Confirm the device is online. On the device details page under Devices & Groups → [Device Name], check that the device status shows Online. Queued commands will not execute while the device is offline — bring the device online before proceeding.
3. Verify available storage on the device. Insufficient storage silently prevents app installs from completing even when the device is online. On the device details page, check the storage indicator. If storage is low, free space before attempting to install.
4. Confirm the app version exists in your app library. Navigate to Apps & Configuration → Company Apps and confirm the exact app version referenced in the blueprint is still available. If the version has been removed or superseded, the install command will fail silently. Re-upload or re-approve the correct version if needed.
5. Manually push the updated app to the device. Navigate to Devices & Groups → [Device Name] → Apps, locate the app, and select Install / Update App to push the correct version immediately. This bypasses the queued command and installs the app directly while the device is online.
6. Re-apply the blueprint to force re-convergence. Navigate to Devices & Groups → [Device Name] → Blueprints and confirm the correct blueprint is assigned to the device. Select Apply Blueprint to trigger a fresh convergence while the device is online. This ensures all commands — including app installs — are re-issued cleanly.

Verify: Navigate to Devices & Groups → [Device Name] → Apps and confirm the correct app version is now listed. Then check Activity Feed and confirm the install command shows a Success status. Both should reflect the update within 5 minutes of the device coming online.

If this doesn't resolve it

If the install command remains in Queued status while the device is online, or this pattern repeats across multiple devices, collect the following before contacting Esper Support:

• Device UUID (found on the device details page)
• Blueprint name and the app version specified in it
• Esper Agent version (found under Devices & Groups → [Device Name] → Device Info)
• Timestamp of the Blueprint convergence event and when the device was last online
• Esper Agent logs — collect via Devices & Groups → [Device Name] → Actions → Request Bug Report, or via ADB:

  adb shell logcat -d -s EsperAgent > agent_logs.txt

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.