Provisioning fails silently on Android 14 devices: Android 14 not yet supported by Esper Esper Agent

Android

If you're trying to provision an Android 14 device into Esper and see a Failed pushing device details error, this article explains what's happening and how to proceed.

Before you begin

Check your device's Android version to confirm whether this issue applies to you.

On the device, open Settings → About Phone → Software Information.
Look for the Android version field.

If your device is running Android 14

Esper does not yet support Android 14. The provisioning process fails because Esper's Esper Agent (Esper Agent) has not been updated to handle the changes introduced in Android 14's Device Owner and Device Admin provisioning APIs.

You have two options:

Use an Android 13 (or earlier) device instead. Android 13 and below are fully supported by Esper. This is the recommended approach if you have devices available.
Downgrade the device to Android 13 or earlier. If the device supports OS downgrading (typically through a firmware flash via the manufacturer's tools), verify the target firmware is Android 13 before attempting. This option depends on your device model and manufacturer.

How to re-provision after switching or downgrading

Confirm the device is now running Android 13 or below by checking Settings → About Phone → Software Information.
Return to Devices & Groups in the Esper Console and re-attempt provisioning using your standard method (QR code, Zero-Touch, KME, or manual Esper Agent).
After successful enrollment, the device should appear in Devices & Groups with a status of Online or Provisioned. The Failed pushing device details error should not recur.

If you're on Android 13 or below and still see the error

The Failed pushing device details error can have other causes beyond Android version compatibility. Try these steps:

Check your network. Verify that your network or firewall is not blocking Esper endpoints. Contact your IT administrator if needed.
Verify your provisioning method is configured correctly. If using Zero-Touch or KME, confirm your configuration in the manufacturer's portal.
Collect Esper Agent logs for troubleshooting. Use ADB to pull offline logs: adb shell run-as com.esper.devicemanagement. These logs can help identify the exact issue.

Preventing automatic OS updates before provisioning

To avoid devices upgrading to Android 14 (or other unsupported versions) before enrollment:

Disable automatic OS updates on devices before provisioning them into Esper.
This prevents the device from upgrading past a supported Android version before MDM lockdown is applied.

Still need help?

If you've tried the steps above and provisioning still fails on a supported Android version, contact Esper Support. include:

Device model and manufacturer
Exact firmware or One UI version (if applicable)
Your Esper tenant ID
The provisioning method you used (QR code, Zero-Touch, KME, or manual)
Any Esper Agent logs you collected