QR code (6-tap) provisioning: step-by-step breakdown of what happens after a device scans the Esper QR code

Android

Title: QR code provisioning fails or stalls — understand the full 6-tap enrollment flow

When provisioning an Android device using the 6-tap QR code method, the device executes a fixed sequence of steps between scanning the Esper QR code and completing enrollment. If provisioning stalls or fails, knowing exactly which step broke down tells you where to focus your troubleshooting.

Why this happens

The 6-tap method triggers Android's built-in Device Owner provisioning flow. Android orchestrates the entire sequence — network connection, APK download, Device Owner grant, and enrollment — before handing control to the Esper Agent. A failure at any point in this chain stops all subsequent steps, so the symptom you see on screen often reflects a problem one or two steps earlier.

Prerequisites

• The device is running Android 7.0 or later and supports Android Enterprise Device Owner provisioning.
• The device has been factory reset and is sitting at the Android Welcome or language selection screen.
• You have a provisioning QR code generated from the Esper Console. Find it at Provisioning Templates → [Template Name] → QR Code.

The full provisioning sequence

1. Trigger the QR scanner. On the Android Welcome screen, tap the screen exactly six times in rapid succession. Android detects this gesture and opens the built-in Device Owner provisioning camera. Some devices display a brief prompt or camera preview before the scanner activates.
2. Scan the Esper provisioning QR code. Point the device camera at the QR code from Provisioning Templates → [Template Name] → QR Code in the Esper Console. Hold the device steady until the scanner confirms a successful read. The QR code carries all provisioning parameters in JSON format, including your tenant token, blueprint ID, and optional Wi-Fi credentials.
3. Confirm or establish a network connection. If Wi-Fi credentials are embedded in the QR code, the device connects automatically. If no credentials are included, Android displays a network selection prompt — connect to a network before provisioning can continue. A reliable network connection is required here because all subsequent steps depend on it.
4. Wait for the Esper Agent APK to download. Android's provisioning framework uses the download URL extracted from the QR code to fetch the Esper Agent APK directly from Esper's CDN over HTTPS. Download time depends on network speed. The device screen may show a progress indicator or remain at a provisioning splash screen during this step.
5. Wait for Device Owner rights to be granted. Android installs the Esper Agent and automatically assigns it Device Owner privileges. This is a silent, system-level operation — no Google account, user confirmation, or interaction is required. Once granted, Device Owner status cannot be removed without a factory reset.
6. Wait for the Esper Agent to register the device. The Esper Agent launches automatically, reads the provisioning parameters, and contacts Esper's cloud backend to register the device against your tenant and provisioning template. You can monitor this in the Esper Console under Devices & Groups — the device will appear with a Provisioning status while this step is in progress.
7. Wait for the Blueprint to apply. After enrollment is confirmed, the Esper Agent downloads and applies your blueprint. This covers all policies, restrictions, kiosk configuration, wallpaper, and settings defined in your provisioning template. Policy application typically completes within a few minutes on a stable connection.
8. Wait for apps to install. The Esper Agent installs all applications defined in the blueprint — including private APKs from your Esper app repository and managed Google Play apps. Installation time varies depending on the number and size of apps and available network bandwidth.

Verify: Provisioning is complete when the device exits the provisioning flow and displays the expected home screen or kiosk interface. In the Esper Console under Devices & Groups, the device status should change from Provisioning to Active within 10–15 minutes on a standard connection. The Activity Feed for the device will show a Device enrolled successfully event.

If this doesn't resolve it

If the device stalls, errors out, or does not appear in the Esper Console after 20 minutes, collect the following before contacting Esper Support:

• The exact step number above where the device stopped progressing, and any on-screen error message.
• The Android version and device manufacturer/model.
• A screenshot of the QR code provisioning screen at the point of failure.
• The provisioning template name from Provisioning Templates in the Esper Console.
• Whether the issue occurs on multiple devices or a single unit.

Contact Esper Support with this information to expedite diagnosis.

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.