Device Stuck in Policy Application State After Provisioning: Factory Reset and Reprovision

Android

When a device completes provisioning but remains in POLICY APPLICATION IN PROGRESS status in the Esper Console, the device appears online but never transitions to Active, making it unusable for Blueprint deployment and app management.

Why this happens

During provisioning, the Esper Agent applies device policies in a background convergence process. If the agent loses network connectivity mid-convergence, encounters a configuration mismatch, or terminates prematurely, policy application stalls and the device cannot complete its transition to an active managed state.

Before you begin

Allow 5–10 minutes after provisioning completes before taking any action. The Esper Agent may still be applying policies in the background. Check Devices & Groups → [Device Name] in the Esper Console — if the status already shows Active, no further steps are needed.

Steps

1. Check whether the "no seamless info" message is your only symptom. Navigate to Devices & Groups → [Device Name] and open the device actions menu. If you see the message This device does not have seamless info associated with it but the device status shows Active, this is expected behavior — it appears on all devices provisioned via USB debugging or QR code rather than Android Zero-Touch Enrollment or Esper Seamless provisioning. Blueprint and app deployment work normally. No further action is required.
2. Confirm the device is genuinely stuck. In Devices & Groups → [Device Name], verify the status still shows POLICY APPLICATION IN PROGRESS after the 5–10 minute wait. If the status has not changed, proceed to the next step.
3. Factory reset the device. On the physical device, perform a factory reset using the hardware recovery menu or Settings → General Management → Reset → Factory Data Reset. This clears the incomplete provisioning state so the device can start a clean provisioning attempt. The device will disappear from Devices & Groups once the reset completes.
4. Prepare for reprovisioning before retrying.
   • If provisioning via USB debugging: confirm the Esper Provisioning Tool is on the latest available version before retrying.
   • If provisioning via 6-tap QR code: verify the QR code is generated from the correct template and that the device has a stable network connection throughout the provisioning flow.
5. Reprovision the device using the same method used initially. Keep the device on a stable network and do not interrupt the process once policy application begins.
6. Repeat the factory reset and reprovision cycle if needed. If the device is still stuck after the first attempt, repeat steps 3–5. Most devices resolve after one or two additional cycles.

Verify: After reprovisioning, navigate to Devices & Groups → [Device Name] and confirm the device status shows Active. Then push a Blueprint or app command from the device actions menu and confirm it executes without error. The device should reach Active status within 10 minutes of provisioning completing.

If this doesn't resolve it

If the device remains in POLICY APPLICATION IN PROGRESS after 2–3 factory reset and reprovision cycles, contact Esper Support and include the following information:

• Device ID and serial number (found in Devices & Groups → [Device Name] → Device Info)
• Provisioning method used (USB debugging, 6-tap QR code, etc.)
• Device model, Android firmware version, and Esper Agent version
• Whether multiple devices of the same model are affected
• ADB logs captured immediately after the stall occurs:

  adb shell logcat -d | grep -i "esper\|policy"

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.