Devices Not Auto-Updating Apps After Extended Offline Periods: Sync Blueprint Configuration

Android

Title: Apps not updating after device reconnects — sync Blueprint configuration

When a device goes offline for an extended period and then comes back online, its apps may remain on older versions even though the assigned Blueprint has been updated multiple times since the device last connected.

Why this happens

Esper delivers configuration changes to devices through a Converge command over its messaging channel. When you publish a Blueprint update, that command is only queued for offline devices if you explicitly choose Publish and converge devices at publish time — a standard publish does not reach devices that are offline. If that option was not selected, or if the Blueprint was updated before the device was ever connected, no Converge command is waiting for the device when it reconnects.

Option 1: Publish and converge the Blueprint (recommended)

Use this approach when you want to bring all devices assigned to a Blueprint fully up to date with the latest app versions and all other configuration settings at once.

1. Open the Esper Console and navigate to Blueprints.
2. Open the blueprint assigned to the affected devices and update it with the correct app version.
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 any that are currently offline.
4. Confirm the publish. Devices that are already online will begin reconciling immediately; offline devices will execute the command as soon as they reconnect.

Verify: Navigate to Devices & Groups → [Device Name] → Activity Feed and confirm the Converge command status shows Completed. Then open the Apps tab and confirm the installed app version matches the version specified in the blueprint. This should reflect within a few minutes of the device reconnecting.

Option 2: Push the app update directly to a group

Use this approach when you want to update a specific app without changing any other device configuration, or when devices in the group have drifted from their Blueprint and a full converge is not appropriate.

1. Navigate to Devices & Groups and select the group containing the affected devices.
2. Open the Actions dropdown and select Apps & Configuration.
3. Open the Install / Uninstall tab.
4. Set App Action to Install, select the target app, and choose the specific version to deploy. Configure App State or Managed Configurations if your deployment requires them.
5. Click Install. The command is queued for any offline devices in the group and will execute automatically when each device reconnects.

Verify: Navigate to Devices & Groups → [Device Name] → Activity Feed and confirm the install command status shows Completed. Open the Apps tab on the device and confirm the correct app version is installed. Allow up to 5 minutes after reconnection for the command to execute and the Console to reflect the update.

If this doesn't resolve it

If the Converge command shows a status other than Completed, or if the app version still does not match the Blueprint after the device has been online for more than 10 minutes, collect the following before contacting support:

• The device serial number or Esper device ID
• A screenshot of the Activity Feed showing the Converge or install command and its status
• The Blueprint name and the app version specified in it
• The app version currently shown on the device's Apps tab

Contact Esper Support with these details so the issue can be investigated further.

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.