Yeah, I'm disappointed that they dropped that line in there with zero explanation.
My understanding is that this should be impossible, as it could likely only be accomplished by calling private APIs. Calling a private API gets an app submission rejected automatically (it's caught by a computer, not a human).
>Calling a private API gets an app submission rejected automatically (it's caught by a computer, not a human).
Its rather arbitrary. In a lot of cases it doesn't because the checker is poorly coded. For e.g. if a selector name inside your OWN code clashes with that of a private API (which is not published or even something you should know) it causes the submission to fail. And then people just resubmit and it gets magically approved. People have also reported that it is possible to bypass the checker either using some dynamic runtime trick or figuring out a way to silence private API calls when the app detects its being looked at. (Usual cat and mouse game)
Thanks, I didn't realize that it was relatively easy to bypass. I did know it primarily relied on string matching, but always thought the solution was to rename your methods when you hit a conflict with Apple's private APIs
My understanding is that this should be impossible, as it could likely only be accomplished by calling private APIs. Calling a private API gets an app submission rejected automatically (it's caught by a computer, not a human).