| As someone who has had a number of rejections from Apple (most of which have been corrected and thereafter accepted), I disagree with the comment. Every time I have gotten a rejection, I have been pointed directly to the app store guidelines the specific bullet point or line item(s) as the reason for the rejection. Most of the time, reading thru those bullet points were enough for me to figure out the "error" in my ways (although, some may argue that the guidelines themselves may be a bit draconian, but that's definitely a topic for another conversation...), and I was able to make the proper corrections, resubmit, and it was accepted. Only on two occasions, was that not enough -- one time I disagreed with their assessment, and on the other time, I was confused as to how the guideline applied. Both times I submitted an appeal, and both times I received a response from an actual person / case manager who explained in much more detail what was going on. (Now, whether or not the responses were timely is another issue... but I again, I digress...) So, at least from my experience (3+ years of iOS development now), I haven't seen any cases where an app I was working on was rejected, without enough information to make the necessary corrections to fix the problem. Sure, it'd be nice and incredibility useful to the innovation curve if the information was dispatched a more time efficient manner... but to say that the information was "lacking" and "curt" just hasn't been the case, at least for me and my experience. |