2 ms·
I have never seen 1/3 of those reasons and I'd wager there is more to the story than is let on. The problem is you see a developer crying foul when we have no
by invisible 16y ago
I have never seen 1/3 of those reasons and I'd wager there is more to the story than is let on. The problem is you see a developer crying foul when we have no idea - and the app may go on to be "fixed" and then approved. Just because someone writes a blog post as soon as they freak out about being rejected doesn't mean they're correct.
- chc 16y agoI'm sure you have never seen 1/3 of those reasons. That was my point — Apple can and does reject apps for any completely unpredictable, off-the-wall reasons. It's not nearly as cut-and-dried as you made it sound. Also, can you give an example of a major rejection story where the developer "freaked out about being rejected" and wasn't right? I don't think that happens. Apple usually tells you in no uncertain terms when your submission has been rejected. And yes, the app may go on to be "fixed" and then approved, or it might not. That doesn't change the fact that it was rejected for a bizarre reason to begin with, in contradiction of your claim that only apps that use private APIs and illegal and confusing apps get turned down. There are many more reasons, a lot of which aren't written down and a lot of which don't exist yet. That's the scariest part — Apple will just change their minds. Remember the Great Skin Purge, where they deleted tens of thousands of apps for "showing skin"?