Usually to be fair the applications I've made (several to date) simply expire without a change in status. Here was not the case!

Sure, and it'll continue through sideloading. You've bought into Google's GMS ecosystem and they're enacting control over what they make easily available within it. You could always take your hardware to Lineage, Graphene, or /e/ and still utilise Android without Google's restrictions I guess

Ironically it affects me the least in enterprise because there are exemptions, but I have personal devices also. My view is if you're legitimate you'll register the application into the Google ecosystem. It's no more controlling than hurdles for bootloader unlock imo. Still a farce though..

For all we know this is their chosen path for getting better: block it at the human element and take out risk en-masse. I agree they're not as good as it could be though, and with all data from the app defense alliance as well..

I don't think you're being prevented, I think it adds an extra step.

I'm not, it's all the more protection against rampant PHA abuse through social engineering, phishing, and ignorance. No more "cracked apps" being 3 taps away from gaining control of device or data, no more package spoofing, and all effort sits with the dev rather than the user.

This! This exactly summarises my feelings on it too. Every interaction leaves a pang of stopping a step before the finish line and it bothers me constantly. How hard is it to launch an intent?! 😆

Ask and you shall receive!

developer.android.com/reference/an...

Reminds me of the provisioning extra KEEP_SCREEN_ON which only worked for Android 13 😅

Here's a MC payload as the Android Management API expects it. The app receives these and configures things automatically.

bayton.org/projects/man...

Idk if it'll work the same way (i.e. without user interaction) for creating pairs, but it would be useful!