QR Code (6-Tap) Provisioning Fails on Android 13 Devices While EDP Provisioning Succeeds

Android

Title: QR Code provisioning fails on Android 13 — remove embedded Wi-Fi credentials

When provisioning Android 13 devices using the 6-tap QR code method, the device fails to complete provisioning even though the same template provisions successfully via the Esper Device Provisioner (USB cable method).

Why this happens

Android 13 changed how Wi-Fi credentials embedded in a provisioning QR code are handled during device setup. When Provisioning Wi-Fi credentials are included in the QR code payload, Android 13 rejects or ignores them in a way that breaks the provisioning flow. Earlier Android versions are not affected by this change.

Steps to resolve

Confirm USB provisioning succeeds first. Before making any changes, verify the device provisions correctly using the Esper Device Provisioner (USB cable method). If USB provisioning also fails, skip to If this doesn't resolve it — this is a separate issue that requires deeper investigation.
Open your provisioning template in the Esper Console. Navigate to Provisioning Templates and open the template you are using for Android 13 devices.
Remove all Provisioning Wi-Fi credentials from the template. In the Provisioning Wi-Fi section, delete every configured SSID. Removing these credentials forces the device to prompt for Wi-Fi manually during setup, bypassing the Android 13 handling issue.
Save the template. Confirm the Provisioning Wi-Fi section is empty before saving.
Generate a new QR code from the updated template. The new code will not contain embedded Wi-Fi credentials.
Provision the Android 13 device using the 6-tap method with the new QR code. When the setup flow prompts for network access, enter your Wi-Fi credentials manually on the device, then continue provisioning as normal.

Verify: The device should appear in Devices & Groups with a status of Online within 5 minutes of completing provisioning. Open the device record and confirm the correct group assignment and that the Esper Agent has checked in.

Large-scale deployments

If manual Wi-Fi entry is impractical for provisioning more than a small number of Android 13 devices, use the Esper Device Provisioner (USB cable method) as your primary provisioning method for this batch. USB provisioning is not affected by this Android 13 credential-handling change and does not require any template modifications.

If this doesn't resolve it

If the QR code still fails after removing Wi-Fi credentials, or if both QR code and USB provisioning are failing, contact Esper Support with the following information:

Device manufacturer and model
Android 13 build number and security patch level
Esper Agent version, found at Devices & Groups → [Device Name] → Device Details → System Info
A screen recording of the provisioning failure
A bug report from the affected device, requested via Devices & Groups → [Device Name] → Actions → Request Bug Report

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.