iOS App Update Fails During Convergence When App Is Actively Running: Close App Before Re-converging Blueprint

iOS

Title: iOS app update fails during Blueprint convergence — close app first

When an iOS Blueprint convergence runs with App Auto Update enabled, the update fails silently and the app version stays unchanged if the target app is open or running in the background on the device.

Why this happens

Apple's MDM framework rejects update commands for any app that is actively running, including apps suspended in the background. When Esper sends the update command during convergence, iOS refuses it at the platform level, causing the convergence operation to fail. This is an Apple platform constraint, not an Esper limitation.

Steps to resolve

1. Identify affected devices by navigating to Devices & Groups → [Device Name] → Activity Feed and looking for failed convergence events. Note each device where the app update step shows a failure.
2. Confirm App Auto Update is enabled in the Blueprint by navigating to Blueprints → [Blueprint Name] → Edit → iOS → Manage Applications and verifying the target app has App Auto Update set to ON. This rules out a misconfiguration as the cause.
3. If your apps are VPP-managed, confirm your VPP token is valid by navigating to Settings → Integrations → VPP and checking the token expiry date. An expired token will block all VPP app updates regardless of device state.
4. On each affected device, fully close the target app. Open the app switcher and swipe the app off the screen. Do not leave it suspended in the background — iOS treats backgrounded apps as running and will still reject the MDM update command.
5. Retry the convergence by navigating to Devices & Groups → [Device Name or Group], selecting the device or group, and applying the Blueprint again. This sends a fresh update command now that the app is fully closed.

Verify: Navigate to Devices & Groups → [Device Name] → Activity Feed and confirm the convergence event shows a successful status. Then open the app on the device and check its version — it should match the latest version available in the App Store. Allow up to 5 minutes for the Activity Feed to reflect the completed status.

If this doesn't resolve it

If convergence continues to fail after closing the app, try the following before contacting support:

• Reboot the device, then close the app again once the device restarts, and retry the convergence. A reboot clears any background processes that may be holding the app open.
• Check whether an update is actually available by verifying the App Store shows a newer version than what is installed. If the device is already on the latest version, no update command will be issued.
• Review the Activity Feed for specific error codes at Devices & Groups → [Device Name] → Activity Feed and note the exact error message.

If the issue persists, contact Esper Support with the following information: the affected device name or serial number, the Blueprint name, the app bundle ID, and any error codes visible in the Activity Feed.

Still need help?

If the issue persists after closing the app before re-converging, please submit a support ticket and include the app name, device model, and the specific error message received during the failed update attempt.