Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
DPC - How to test code paths for QR/Zero Touch Device Owner setup?
See original GitHub issueSorry to any googlers as this likely isn’t the right venue.
Can anyone explain exactly how the app is launched in Zero Touch and Device Owner QR Code enrollment? I understand that an intent is sent, and will contain the PROVISIONING_ADMIN_EXTRAS_BUNDLE - that’s all quite straightforward, but I’m not sure exactly where the intent should be handled, given that provisioning happens immediately upon device startup and it’s not feasible to debug.
Any advice - intent filter, class, etc. would be helpful.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Back in Android 10, TestDPC was updated in accordance to this guide. In summary, there are 2 entry points to TestDPC: the
android.app.action.GET_PROVISIONING_MODE, which requests the DPC to return the desired provisioning mode (work profile or device owner), andandroid.app.action.ADMIN_POLICY_COMPLIANCE, which allows the DPC to set itself up after it has been made a profile owner/device owner. This is the case for ZeroTouch and QR enrollment, and we’re migrating all of the other flows to follow this pattern as well. For managed account provisioning, pre-Android 12 it’s only launched after provisioning it’s launched via theandroid.app.action.PROVISIONING_SUCCESSFULintent, and from Android 12 onward it’s started just like ZeroTouch and QR enrollment. For NFC provisioning it’s also only started viaandroid.app.action.PROVISIONING_SUCCESSFUL, which will also be updated in the upcoming Android release to be like ZeroTouch and QR enrollment.Create a local server that serves your custom TestDPC or upload it somewhere publicly Make sure you can actually access the TestDPC apk from the phone Get the SHA-256 checksum of the apk; on Linux you can use sha256sum path/to/TestDPC.apk Create a QR code with the following content: { “android.app.extra.PROVISIONING_DEVICE_ADMIN_COMPONENT_NAME”: “com.afwsamples.testdpc/com.afwsamples.testdpc.DeviceAdminReceiver”, “android.app.extra.PROVISIONING_DEVICE_ADMIN_PACKAGE_CHECKSUM”: “apk checksum from step 3”, “android.app.extra.PROVISIONING_DEVICE_ADMIN_PACKAGE_DOWNLOAD_LOCATION”: “url that serves your TestDPC” } From the SetupWizard Welcome screen tap 6 times to launch the QR code scanner Scan QR code