Blueprint JSON provisioning applies only partial settings + QR code provisioning fails due to missing Device Owner: full resolution flow

Android

When provisioning Android devices through Esper, you may see two related failures: a Blueprint's settings apply only partially to an enrolled device, or QR code provisioning does not complete because the Esper Agent is never granted Device Owner permissions. Both issues leave devices unmanaged or misconfigured.

Why this happens

Partial settings usually mean the Blueprint is not linked to the device group, so only a subset of policies reaches the device at enrollment. QR code provisioning failures occur when the Esper Agent cannot claim Device Owner status — most commonly because the device was not in a clean factory-reset state, or because an existing account on the device blocks Device Owner assignment.

Fix 1: Blueprint applying only partial settings

Open the Esper Console and navigate to Devices & Groups.
Select the device group that is receiving incomplete settings.
Click Link and select the Blueprint that contains your full JSON configuration. Linking ensures every device in this group inherits the complete policy set, not just the defaults.
Choose Link Only to apply the Blueprint to newly provisioned devices going forward, or select the option to push settings to already-enrolled devices immediately if you need to correct existing devices.
For devices not yet enrolled, confirm this Blueprint is selected under Provisioning > Provisioning Method before generating the provisioning QR code or template, so the full configuration is applied at enrollment time.

Verify: Navigate to Devices & Groups → [Group Name], open the linked Blueprint, and confirm every expected settings section is present and populated correctly. Enrolled devices should reflect all policy changes within 5 minutes.

Fix 2: QR code provisioning fails — Device Owner not set

On the affected device, tap the Esper logo several times on the provisioning screen to reveal the reset option, then initiate a factory reset. Allow the device to reboot fully to its out-of-box setup wizard before proceeding.
Scan the provisioning QR code again from the setup wizard. The Esper Agent requires a completely clean device state to claim Device Owner permissions during first-time enrollment.
If provisioning fails again, connect the device to a computer that has ADB installed and run the following command:
```
adb shell dpm set-device-owner com.example.app/com.shoonyaos.shoonyadpc.receivers.AdminReceiver
```
Once the command completes successfully, retry the provisioning flow on the device.

Verify: The device should appear as enrolled under Devices & Groups in the Esper Console with its Blueprint configuration fully applied within 5 minutes of completing provisioning.

If the ADB command returns an accounts error

If the command above returns Not allowed to set the device owner because there are already some accounts on the device, a Google or device account is blocking Device Owner assignment.

Perform a full factory reset using the device's Android recovery mode — not the Esper reset menu — to ensure all accounts and data are completely removed.

Once the device is back at its out-of-box state, re-run the ADB command:

adb shell dpm set-device-owner com.example.app/com.shoonyaos.shoonyadpc.receivers.AdminReceiver

Retry the provisioning flow.

If the command still fails after a clean factory reset on a specific device model, the device manufacturer may restrict Device Owner assignment via ADB. Collect the full ADB error output and the device make, model, and Android version before contacting support.

If Blueprint settings are still incomplete after successful provisioning

In the Esper Console, export the Blueprint that was applied to the device.
Compare it field-by-field against your original JSON file to identify which settings are absent or overridden.
Check that no conflicting Blueprint is linked to a parent group, as parent-group policies can override child-group settings.

Verify: After correcting the Blueprint and re-linking it, trigger a policy sync from Devices & Groups → [Device Name] → Actions and confirm all expected settings appear on the device within 5 minutes.

If this doesn't resolve it

Contact Esper Support with the following information:

Your original Blueprint JSON file
A list of the specific settings that are not applying
The device make, model, and Android version
The full ADB error output if Device Owner assignment failed
Screenshots of the device's status in Devices & Groups and the Activity Feed for the affected device

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.