It was using private APIs.
This is never acceptable as it undermines the entire security architecture.
Private APIs for security reasons? Sure.
For this? Garbage. There is not a single cogent reason that a color temperature API is a security gate. Or if you think there is, what is it?
Those APIs are only there because they're needed by some higher-level system library that your app is actually allowed to use.
Sure, you could have all libraries be simple shims, all calls be interprocess, and all security be guaranteed by process boundaries, but that would kill performance.
If you only accept signed code and have W^X protections that apps aren't allowed to disable, this way is simpler, faster and just as secure.
Even innocuous apps like a calculator can, and do, use them for that purpose.
The App Store process automatically checks for them and blocks submission.
Curious how apps are bypassing this and not sure why they would be trying to prevent debugging when it's not possible to do this.
