Single-use QR codes not supported for 6-Tap provisioning: use Seamless Provisioning (afw#esper) with serial-number pre-registration as a workaround

Android

By default, 6-Tap QR codes generated in the Esper Console are reusable, which means the same QR code can provision multiple devices. If you need to restrict provisioning to specific, known devices, use Seamless Provisioning with serial number pre-registration instead.

Before you begin

Gather the hardware serial numbers of the devices you plan to provision. You can find this information:

On the device packaging or documentation
Via ADB: adb shell getprop ro.serialno
In device Settings → About screen

Seamless Provisioning requires devices to have access to the Google Account sign-in screen during setup. Devices with Google Mobile Services (GMS) blocked or carrier-locked setup wizards may not support this method.

Step 1: Set up Seamless Provisioning in the Esper Console

In the Esper Console, go to Provisioning → Provisioning Methods.
Select Seamless Provisioning as your provisioning method.
Choose the target Blueprint and Group for the device.
Enter the device's hardware serial number. This creates a provisioning entry that will only match that specific device.

Step 2: Configure your Blueprint

Before provisioning, check your Blueprint's app configuration to avoid installation failures during setup.

In your Blueprint, review any apps that may conflict with system versions (such as Chrome or other pre-installed apps).
Set these apps to "Post Provisioning" instead of "During Provisioning". This prevents install errors that can halt the provisioning process.

Step 3: Provision the device

Factory reset the device.
Proceed through the Android setup wizard until you reach the Google Account screen.
In the Google Account field, enter afw#esper and proceed.
Follow the on-screen prompts to download and complete Esper provisioning.

Step 4: Verify provisioning succeeded

In the Esper Console, go to Devices & Groups.
Confirm the device appears as Active.
Verify that the pre-registered serial number entry has been consumed and now shows the live device.

Troubleshooting

Device stuck on "Device Onboarded" screen after provisioning

Check your Blueprint for apps configured as "During Provisioning" that may be failing to install. Error messages like INSTALL_FAILED_MISSING_SPLIT: Missing split for com.android.chrome indicate a version conflict. Switch those apps to "Post Provisioning" and attempt provisioning again with a clean factory reset.

Serial number doesn't match

Verify the serial number you entered in the Esper Console exactly matches the value reported by the device. Check via adb shell getprop ro.serialno or the device's Settings → About screen.

Seamless Provisioning flow fails to complete

Confirm the device is online and correctly pre-registered on the Esper Console with the correct serial number. If the issue persists, contact Esper Support.

You need true single-use QR codes

Single-use QR codes are not currently supported in the Esper platform. The serial number pre-registration approach provides device-scoped provisioning, which achieves similar access control by restricting provisioning to known devices. As an additional operational safeguard, pair this with your own warehouse inventory controls to prevent unauthorized device provisioning.

Important notes

Serial number pre-registration requires advance planning: You must know each device's serial number before provisioning. This may require adding a serial number recording step to your warehouse intake process.

GMS requirements: Seamless Provisioning requires devices to have Google Mobile Services (GMS) enabled and access to a Google Account sign-in screen during setup.

Still need help?

If you've followed these steps and continue to experience issues, submit a support ticket and include your device's serial number and the error message you're seeing.