a collection of common criteria for rejection to the App Store
Hi guys,
we're starting a blog to collect rejection criteria - starting with our own 4 rejections. Hopefully it will help some of you avoid extra weeks of waiting by letting you avoid the common rejection pitfalls.
we're starting a blog to collect rejection criteria - starting with our own 4 rejections. Hopefully it will help some of you avoid extra weeks of waiting by letting you avoid the common rejection pitfalls.
Great idea, I'll contribute my experiences at your blog (and no doubt here as well) if I have a rejection. As we pass day 15 waiting on my new project, I've come to assume they're going to reject it. Don't they always come back with a rejection after the long delays?
In other words, has anyone ever waited 2 or 3 weeks for an approval? Seems like they'll be < 1 week to approve, and >2 weeks to reject. If that's true, then I wonder why.
we waited 10 days on our first app, and are 9 days and counting for a new one now... It seems completely variable. However, they DO work through the weekend, as two of our apps were approved on Sat and Sun, respectively. Go figure...
in order to use core animation, for instance, you need to add the Quartz Core framework. In other words you 'link against' the framework. There are lots of other frameworks you could link against that could give you a bunch of potentially useful functionality. If that framework is listed as private, however, Apple won't accept your app into the store.
A private framework, in my understanding, is an Apple framework that isnt documented or a part of the official SDK??? Its not one of my own or 3rd party frameworks right??
so for instance, to play sound, I need to link to 'AudioToolbox.framework', and to show a table, 'CoreGraphics.framework'. Is that the same thing? How does anyone make an app that doesnt link to these services? How would one produce sound? I couldve save myself hours of contemplating a gun on tableviews if I had known this
Quote:
If that framework is listed as private
where is this listing to be found?
This seems very strange to me on the surface and I hope more is posted on this subject. (needless to say I have sounds in the app im developing).
What would be the point of Apple saying "Heres a great sdk go have fun, oh and half the stuff we show you how to do, you cant actually use in a finished App!"
cheers.rob
Last edited by roberthuttinger; 09-23-2008 at 04:21 PM.
Reason: sprayed windex on the posting
we're starting a blog to collect rejection criteria - starting with our own 4 rejections. Hopefully it will help some of you avoid extra weeks of waiting by letting you avoid the common rejection pitfalls.
2) Linking to private frameworks. This is obvious, but somehow in playing around with stuff we had linked to the MoviePlayer.framework. That’s a no-no, and cost us about ten days while we unlinked that framework, recompiled, and then resubmitted.
What does this really mean? How are you suppose to play a movie?? What are private frameworks?
Lastly, I have not submitted an app yet!.. What exactly do you have to give to them, the compiled app or the actual code? How does apple know what frameworks you're using?
Apple should clarify all these procedures.. Cheers
Last edited by cooljayman; 09-24-2008 at 01:02 AM.
Surprisingly my first app was originally accepted with a slightly different app icon and app store icon. It was similar, maybe if you looked fast it seemed close enough...but it was pretty obvious if you knew. My update that was accepted explicitly stated that I was changing the app icon to match the app store icon, lol.
A private framework, in my understanding, is an Apple framework that isnt documented or a part of the official SDK??? Its not one of my own or 3rd party frameworks right??
+1 on this question. mbruun, did you find out the answer?
Does anyone know if 3rd party framework is allowed by app store??
a collection of common criteria for rejection to the App Store
Don't they always come back with a rejection after the long delays?
Linear Mode
