Seamless provisioning fails with "Failed pushing device Details": temporary communication error

Android

When provisioning multiple devices using seamless provisioning, the devices stop mid-flow and display a Failed pushing device Details error on-screen.

Why this happens

This error occurs when the device cannot complete its handshake with Esper's provisioning servers during enrollment. It is almost always caused by a transient network or server-side communication failure rather than a misconfiguration on the device. If only one or two devices are affected while others provision successfully, the problem is likely isolated to those specific devices rather than your network or Esper's infrastructure.

Steps to resolve

1. Wait 5–10 minutes, then retry provisioning. Because this error is typically transient, a short wait is enough to resolve it. Attempt the seamless provisioning flow again before continuing with the steps below.
2. Remove the stale device registration in the Esper Console. Navigate to Devices & Groups → [Device Name] → Device Details and select the affected device by serial number. Click Remove Registration. Repeat for every device that failed. Removing the stale registration ensures the device can re-register cleanly instead of conflicting with an incomplete enrollment record.
3. Re-add the device serial number to seamless provisioning. Navigate to Provisioning → Seamless Provisioning and add the device serial number again. This creates a fresh registration entry for the device to claim during enrollment.
4. Perform a full factory reset using the Esper logo tap method. A standard recovery-mode reset may not clear all provisioning state left from the failed attempt. On the device, locate the Esper logo on the provisioning screen and tap it 5–6 times. When the option appears, select Factory Reset and wait for the reset to complete.
5. Retry the seamless provisioning flow. Initiate provisioning on the freshly reset device.

Verify: The device should appear as a blue (pending/online) entry under Devices & Groups within a few minutes of completing provisioning. Once enrollment finishes, the entry turns active and the device moves into its assigned Blueprint.

If this doesn't resolve it

If all or most devices continue to fail with no recent changes to your network or Esper Console configuration, this points to a backend or infrastructure-level issue. Before contacting support, collect offline Esper Agent logs from an affected device:

1. Connect the affected device to a laptop via USB.
2. Confirm ADB is installed and the device is recognized:

   adb devices

3. On the device, tap the device ID shown on-screen 5–6 times until a Fetching logs message appears.
4. Pull the log archive to your laptop:

   adb pull /storage/emulated/0/Download/dpc_logs.zip /path/to/save/locally

Contact Esper Support and include the following: the affected device serial numbers, the exact error message displayed, your provisioning method, your geographic region, and the Esper Agent log archive collected above.

--- **Improved title:** Seamless provisioning fails with "Failed pushing device Details" — clear stale registration and retry

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.