Forum Discussion
Play Protect Blocking Custom DPC Apps — How to Get Approval or Alternatives?
Hi Everyone,
After lot investigation I found the root cause. The app included certain sensitive permissions that are not allowed by Play Protect. Once I removed those restricted permissions, the app stopped getting flagged and worked as expected.
For more details, Google provides guidance on Play Protect warnings and how to avoid them here:
https://developers.google.com/android/play-protect/warning-dev-guidanceHope this helps anyone running into the same challenge!
I have just hit the same issue on an Android 12 device with our custom DPC. This is a configuration that has previously been working just fine.
"This app can install potentially harmful apps without your permission"
This is for fully managed devices only (Device Owner) in a strictly controlled environment.
Installing apps with minimal intervention is the main point.
Anybody got around this yet? Do we need to apply to Google for an exemption?
Is your DPC on Google Play steve_mdm? If not, publishing it there may help.
jasonbayton It is not on Play and the use case precludes it.
Basically the system including the DPC must be available on air gapped or intermittent networks so we must be able to download from a local source. This is also why we need the DPC to be able to install other apps from the same source. It's like an app store but only the content management part, not selling apps. Users will have mandatory apps and optional apps. All the apps will have license agreements in place and all third party developers will be aware of what is happening. All the users will also be fully aware. The Android devices will be fully managed and absolutely not for personal use.
Thinking about it, I suppose we could put it on Play as well but I'm not sure if it just being there but not downloaded from there would help.
I was leaning towards the final thought there really. Use-case aside, Play doesn't know the app, doesn't trust it, and can't necessarily verify it's legitimate. Noting the upcoming developer registration requirements also, eventually you're going to have to register the package in one of the two consoles they'll make available.. so.
I'm not saying it'll work, but in the conversations I've been having this *seems* to stem from a position of trust more than simply the ability to sideload apps.
Lizzie anything you can add here? If I'm wrong that's totally fine also :)
It's also worth noting that the app sideloads just fine, when obviously, it does not get DO permission. This is only an issue when installing via a QRCode scan from factory reset.
I will put it to our management to try uploading to Play. Don't think that will be a quick decision 😒
