Bulk app update across all devices: use Group App Management, Pipelines, or Blueprints

Android

Title: Bulk app update not reaching all devices — choose the right deployment method

When you need to push an updated app version to your entire device fleet, the correct deployment method depends on how your devices are enrolled. Using the wrong method means devices may never receive the update.

Why this happens

Esper offers three distinct management models — Group-based, Pipeline-based, and Blueprint-based — and each has its own mechanism for delivering app updates. An update pushed through one model has no effect on devices managed by another, so identifying your enrollment method first is essential.

Before you begin

Confirm the updated APK is already uploaded and ready. Navigate to Apps & Configuration → Private Apps and verify the new version shows a Ready status. No deployment method will offer the new version in its selector until this step is complete.

Option 1: Group Apps & Configuration (recommended for Template-enrolled devices)

Use this method if your devices were enrolled using a Template and are organized into groups.

1. Navigate to Devices & Groups and select the group containing the devices you want to update.
2. Click Actions at the top of the group view, then select Apps & Configuration. This opens the app management panel scoped to that group.
3. Locate the application you want to update in the app list.
4. Open the version selector for that app and choose the new version.
5. Click Deploy to push the update to every device in the group.

Verify: Open Devices & Groups → [Device Name] → Apps on one or more target devices. The updated version number should appear within 5–10 minutes for online devices.

Option 2: Pipelines (recommended for staged or automated rollouts)

Use Pipelines when you need phased rollouts, scheduled deployments, or automated updates across multiple groups. Pipelines let you validate each stage before the update proceeds to the next group.

1. Navigate to Pipelines in the Esper Console.
2. Create a new pipeline or open an existing one that targets your device group.
3. Add an App Update stage, then select the application and the target version.
4. Set your stage conditions and schedule, then click Publish.
5. Run the pipeline and monitor the execution status on the pipeline detail view to confirm each stage completes successfully.

Verify: The pipeline detail view should show all stages as Completed. Cross-check by navigating to Devices & Groups → [Device Name] → Apps on a device in each stage group and confirming the new version is installed.

For full setup instructions, see Introduction to Pipelines.

Option 3: Blueprints (for Blueprint-managed devices only)

Use this method only if your devices are enrolled and actively managed through a Blueprint. Editing a Blueprint and publishing it propagates all changes — including app versions — to every device linked to that Blueprint.

1. Navigate to Blueprints in the Esper Console.
2. Open the blueprint associated with your target devices.
3. Under the Apps section, update the application to the desired version.
4. Click Publish to apply the updated blueprint to all linked devices.

Verify: Navigate to Devices & Groups → [Device Name] → Apps on a linked device. The new app version should appear within 10 minutes of publishing. The device's Blueprint sync status should show In Sync under Devices & Groups → [Device Name] → Overview.

For full setup instructions, see Updating Applications using Blueprints.

Troubleshooting

The new version does not appear in the version selector

The APK upload has not completed or did not succeed. Navigate to Apps & Configuration → Private Apps and confirm the new version shows a Ready status. If it shows Processing, wait a few minutes and refresh. If it shows Failed, delete the entry and re-upload the APK.

Devices show a Queued status after deployment

Devices that are offline at the time of deployment queue the update and install it automatically once they reconnect. To check connectivity, navigate to Devices & Groups → [Device Name] → Overview and review the device's last-seen timestamp and connection status.

The app fails to install on specific devices

A bug report from the affected device provides the most detail for diagnosing install failures.

1. Navigate to Devices & Groups → [Device Name] → Overview.
2. Click Bug Report and wait for the report to generate.
3. Download the report and review the install logs for error codes or permission conflicts.

If this doesn't resolve it

If devices still do not receive the update after following the steps above, contact Esper Support with the following information:

• The deployment method used (Group, Pipeline, or Blueprint)
• The device serial numbers or group name affected
• Screenshots of the deployment status or pipeline execution view
• Bug reports from at least two affected devices
• The app name, previous version, and target version

Still need help?

If bulk app updates aren't working as expected across your devices, submit a support ticket and include details about which method you're using (Group App Management, Pipelines, or Blueprints), the app name and version, affected device count, and any error messages you've encountered.