Skip to main content
LAKSHAYNE
LAKSHAYNE
Level 1.6: Donut
September 19, 2026
Question

Play Protect blocks Google's Test DPC 9.0.12 during QR provisioning: "App blocked to protect your device"

  • September 19, 2026
  • 1 reply
  • 22 views

Since 19 Sep 2026, QR (6-tap) provisioning of Test DPC on a factory-reset device fails. After "Getting ready for work", Play Protect shows "App blocked to protect your device - Test DPC" with only an OK button, so provisioning cannot continue. The same flow worked before that date and nothing changed on our side.

Setup: provisioning QR with PROVISIONING_DEVICE_ADMIN_COMPONENT_NAME com.afwsamples.testdpc/com.afwsamples.testdpc.DeviceAdminReceiver, an HTTPS download location for the APK, and the signature checksum.

APK: com.afwsamples.testdpc 9.0.12 (versionCode 9012), unmodified, signed by CN=testdpc, O=Google Inc. Signing certificate SHA-256: 8090f6630b4e8962479123249087cb4658feaae36a1b57dbeafd74d109b333dc. File SHA-256: aad38c1f608b1c7289405c4e866977f5d231502643ce2e2401a7c305808f9c00 (on VirusTotal, 1/67, a generic AdLibrary heuristic).

I found the approved-DPC allowlist page (https://support.google.com/work/android/answer/16694822) and other threads about custom DPCs being blocked, but nothing about Test DPC itself.

What I have done: opened https://github.com/googlesamples/android-testdpc/issues/283 and submitted a Play Protect appeal for com.afwsamples.testdpc.

Questions: 1) Is Test DPC on the approved-DPC allowlist? 2) Is anyone else seeing this with Test DPC, and did a newer build or a different provisioning method fix it? 3) Is there a supported way to provision Test DPC on test devices now?

    1 reply

    jasonbayton
    jasonbayton
    Level: 4.1: Jelly bean
    September 19, 2026

    I believe this is intentional as the app is supposed to be a reference only, but only Google can confirm. ​@Lizzie 

    Terms & ConditionsAccessibility statement