Seamless provisioning fails for all devices with "Failed pushing device Details": self-resolved transient failure

Android

If your devices fail to provision with a "Failed pushing device Details" error during seamless provisioning, follow these steps to resolve the issue. This error typically indicates a temporary communication problem between your devices and Esper's provisioning servers.

Before you begin

This troubleshooting guide applies when multiple devices fail to provision simultaneously with the Failed pushing device Details error message on-screen during seamless provisioning. If the issue affects only a few devices while others provision successfully, the problem may be isolated to those specific devices.

Step 1: Wait and retry

The "Failed pushing device Details" error often resolves on its own within a few minutes, as it typically indicates a temporary network or server-side issue. Wait 5–10 minutes, then attempt provisioning again before proceeding with troubleshooting.

Step 2: Remove stale device registrations

If retrying doesn't work, remove the failed device registrations from the Esper Console:

Go to Devices & Groups → Device Details
Select the affected device by serial number
Click Remove Registration
Repeat for each device that failed to provision

Step 3: Re-add the device to seamless provisioning

Go to Provisioning → Seamless Provisioning
Add the device serial number again

Step 4: Perform a full factory reset

A standard recovery-mode reset may not clear all provisioning state. Use the Esper logo tap method instead:

On the device, locate the Esper logo on the provisioning screen
Tap the Esper logo 5–6 times
Select the factory reset option when it appears
Wait for the reset to complete

Step 5: Retry provisioning

After the factory reset completes, initiate the seamless provisioning flow again. The device should appear as a blue entry (pending/online) in Devices & Groups when enrollment succeeds.

If the issue persists across multiple devices

If all or most of your devices continue to fail with no recent changes to your setup, this suggests a backend or network infrastructure issue rather than a device-side problem. Collect offline Esper Agent logs for Esper Support to analyze:

Connect an affected device to a laptop via USB
Ensure ADB is installed on your laptop
Tap the device ID on-screen 5–6 times until a "Fetching logs" message appears

Pull the logs using the following command:

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

Include the affected serial numbers, error message, provisioning method, and your geographic region when submitting your support request

Still need help?

If you've completed these steps and the issue persists, contact Esper Support. provide the affected device serial numbers, the exact error message, your provisioning method, and any offline Esper Agent logs you've collected.