Ensuring devices auto-update to the latest app version after extended offline periods

Android

When a device returns online after an extended offline period, its apps may remain on older versions even though the assigned Blueprint has been updated one or more times while the device was offline.

Why this happens

Esper pushes configuration changes to devices through a Converge command delivered over an MQTT channel. When a Blueprint is published, only devices that were online at publish time receive the command immediately. Offline devices queue the command and execute it on reconnect — but only if Publish and converge devices was selected at publish time. If the Blueprint was published without that option, or if the device missed multiple publish cycles, no update command is waiting for it.

Option 1: Publish and converge the Blueprint (recommended)

Use this approach when the affected devices are assigned to a Blueprint and you want to bring all settings — including app versions — back into sync at once.

1. In the Esper Console, navigate to Blueprints and open the blueprint assigned to the affected devices.
2. Confirm the app version in the blueprint matches the version you want deployed. Update it if necessary.
3. Click Publish. In the publish dialog, select Publish and converge devices. This queues a Converge command for every device assigned to this blueprint, including devices that are currently offline.
4. Click Confirm to complete the publish. The Converge command is now queued. Offline devices will receive and execute it as soon as they reconnect to the internet.

Verify: Once a device reconnects, navigate to Devices & Groups → [Device Name] → Activity Feed and confirm the Converge command shows a status of Completed. Then open the Apps tab and confirm the installed app version matches the version specified in the blueprint. This should complete within a few minutes of the device coming back online.

Option 2: Push the app directly via Group Apps & Configuration

Use this approach when you want to update a specific app without changing other device settings, or when devices have drifted from their Blueprint configuration.

1. In the Esper Console, navigate to Devices & Groups and select the group containing the affected devices.
2. Click the Actions dropdown and select Apps & Configuration. This lets you issue an app install command scoped to the group without modifying the underlying blueprint.
3. Open the Install / Uninstall tab.
4. Set App Action to Install, select the target app, and choose the latest version from the App Version dropdown.
5. Configure App State or Managed Configurations if your app requires them.
6. Click Install. The install command is dispatched immediately to online devices and queued for any devices that are currently offline. Offline devices will execute the command upon reconnection.

Verify: Once a device reconnects, navigate to Devices & Groups → [Device Name] → Apps and confirm the installed version matches the version you selected. The update should appear within a few minutes of the device coming back online.

If this doesn't resolve it

If the app version does not update after the device reconnects, collect the following before contacting support:

• The device name or serial number
• The blueprint name and the app version it specifies
• A screenshot of the Activity Feed for the affected device, showing the Converge command status
• The app version currently installed, visible under Devices & Groups → [Device Name] → Apps

Contact Esper Support with this information so the team can investigate whether the command was correctly queued and delivered.

Still need help?

If auto-updates aren't triggering after your devices reconnect, submit a support ticket and include your app version, device offline duration, and any error messages from the Esper console.