Kaziq he insists it's Google's fault
Kaziq I don't know whether it's really Google's fault (or GOS'), or the developer is mistaken and he is able to do something while still keeping the anti-piracy feature enabled.
It's complicated, but I'd say it's Google's fault. The Automatic Protection and Play Integrity "security" features are really checking two things: was the app installed using Google Play, and is the OS certified by Google where one of the requirements is GMS apps should be preinstalled and have privileged access. They're anti-competitive features that Google is passing off as "security" features.
Developers who really care about security would probably prefer their apps are running on a secure OS, like GrapheneOS, not some very insecure out of date OS on an insecure out of date device.
Kaziq Any ideas?
I'm not sure of how it all appears in the developer console, but they can disable Automatic Protection. Not sure, but they may also need to turn off integrity checks (do the opposite of this). To use the paid version of the app, the app will check Google Play for a valid license. They can at least know that the app was installed with Google Play in that case (since if it's not installed with Google Play it's not going to be licensed). It's my understanding that the license responses cannot be spoofed because they're cryptographically signed by Google.
In other words, Automatic Protection's only real purpose is to force users to install apps with Google Play, but that's required anyway to use the paid app. They get no real benefit from Automatic Protection.
Integrity checks are another way to restrict apps from running on devices not certified by Google. If you've paid, and the app verifies it's licensed, why do they care which OS it's on?