Android 14 beta devices fail to enroll/provision in Esper MDM: enrollment not supported on pre-release Android versions

Android

If your device is running an Android 14 beta or pre-release build, it cannot enroll in Esper. This article explains why and how to resolve the issue by updating to a stable Android version.

Before you begin

Esper only supports enrollment on stable, publicly released versions of Android. Beta, preview, or pre-release builds are not compatible with Esper's Esper Agent (Esper Agent) because these versions may contain API changes or provisioning behavior changes that break the enrollment process.

How to check your Android version

1. On your device, open Settings → About Phone.
2. Look at the Build Number field.
3. If it contains identifiers like beta, preview, QPR, or other non-final build tags, your device is running a pre-release version.

How to fix this

1. Update to a stable Android release. If your device is eligible for over-the-air updates, go to Settings → System → System update and check for the latest stable release. If your device cannot receive OTA updates, you may need to manually flash a stable factory image using ADB (Android Debug Bridge).
   • For Google Pixel devices, stable factory images are available at Google's Factory Images page. Download the appropriate image for your device model and follow Google's flashing instructions.
   • For other manufacturers, contact your device OEM for stable build availability.
2. Restart your device after the update completes.
3. Re-attempt provisioning using your standard Esper provisioning method (QR code, Zero-Touch Enrollment, KME, or the AFW #setup method).
4. Verify enrollment success by checking the Esper Console. Your device should appear as Online under Devices & Groups → Device Details, with its Esper ID visible and assigned policies applied.

If you cannot update to a stable version

If your device's bootloader is locked or your OEM does not provide stable builds, you will need to use a different device running a supported Android version while you wait for official support to be announced for your current OS version.

If provisioning still fails on a stable Android build

If you have confirmed your device is running a stable (non-beta) Android release and provisioning still fails:

1. Record a screen capture of where the provisioning process stalls.
2. Collect Esper Agent logs by running the following ADB command:

   adb shell logcat -b all > dpc_logs.txt

3. Contact Esper Support and provide:
   • Your device model
   • The exact OS build string (from Settings → About Phone → Build Number)
   • The provisioning method you used
   • The screen recording and Esper Agent log files

Still need help?

If you have further questions or your device is still unable to enroll, submit a support ticket with your device model, OS build string, and provisioning method.