App install/update failures for bulk group deployment: transient network errors cause silent failure with no auto-retry

Android

When you deploy an app update to a device group, some devices may fail to install due to transient network issues. These failures don't trigger automatic retries or alerts. This article explains what's happening and how to resolve it.

Why app installs fail in bulk deployments

When you issue a bulk app install or update command to a device group, individual devices may experience temporary network interruptions during APK download or installation. If a device can't complete the download or installation handshake within the command window, the operation fails silently. Esper does not automatically retry failed app installs or send alerts when failures occur.

Before you begin

Verify that:

• The affected devices were online when you issued the app update command
• You have access to the Esper Console
• You know the app package name and target version

How to identify failed app installations

1. In the Esper Console, go to Devices & Groups → [Your Device Group]
2. Look for devices showing a failed status for the app update command
3. Note the device names or IDs

How to retry app installations manually

For each device that failed to install the app:

1. Navigate to Devices & Groups → [Device Name] → Apps
2. Find the app that failed to install
3. Trigger a manual reinstall or update to the target version
4. Wait for the installation to complete
5. Verify the app version is now correct under Devices & Groups → [Device Name] → Apps → Installed Apps

Alternative: Reissue the group command for failed devices

Instead of retrying devices one at a time, you can reissue the app deployment command to only the devices that failed:

• Create a new device group containing only the failed devices
• Issue the app update command to this subset group
• Or, use individual device commands if your Esper setup doesn't support filtered group commands

If retrying doesn't work

If manual retry also fails on specific devices:

1. Confirm the device has stable internet access and can reach Esper's app delivery servers
2. Check device-level logs for more specific error codes:

   adb shell logcat -d | grep -i "install\|package"

3. If failures are widespread, collect the following information before contacting Esper Support:
   • The command request ID from the failed deployment
   • A list of affected device IDs
   • Logs from at least two affected devices
   • Description of your network environment (Wi-Fi, cellular, proxies, firewalls)

Current product limitations

Be aware of the following:

• No automatic retries: Esper does not automatically retry failed app installs or updates. You must retry manually or reissue the command.
• No failure alerts: There is no built-in notification system for app install failures. You must manually check the Esper Console to discover failures.
• Limited log detail: Device logs may not provide enough detail to identify the root cause beyond a general network issue.

Monitor app installations programmatically

If you need to track app installation status automatically, you can use the Esper API to poll command status:

GET /v0/enterprise/{enterprise_id}/devicecommand/

Filter results by command_type: INSTALL and status: Failure to identify failed deployments, then build your own alerting or retry logic downstream.

Still need help?

If you've tried these steps and app installations are still failing, contact Esper Support. Include the command request ID, list of affected device IDs, device logs, and your network environment details.