I have uploaded a build 4 months ago, and this is my fifth update. All builds approved seamlessly before, however surprisingly apple gave me today surprise reason of City and Profession(from signup form). Now as I don't have any choice, I made some major changes :(
My issue is, why this issue came suddenly, though apple takes such a long tenure of checking and validation(4 days in my case) also we are pledging good amount, unlike android which is far faster and convenient.
Or should I consider, apple indeed failed to work as per their own guidelines at initial level and troubling developers
#iOS developers please comment
It is a common occurrence for Apple to miss something that violates the guidelines initially and reject an app later because of it. I've personally seen a reputable app get rejected for the app icon even though that icon had been in use for months prior to the rejection.
You have to realize that app reviews are done by humans and not nearly as automated as the play store review process. Humans are prone to error and bias. You may have one reviewer that says an aspect of your app follows the guidelines, while another disagrees. You may have a reviewer that doesn't notice an issue at first, but does months later.
The review process can be annoying and inconsistent but it does help Apple to enforce some level of quality in the App Store.
I developed an iOS application where in that application can rate and review other users in 3 sectors like:
Dating
Personal
Professional
The entire application was completed and built in 1.0, i have submitted the application to the app store but the application was rejected due to 1.2 guidelines.
As per the 1.2 guidelines i have implemented
Block/Unblock
Terms & Condition
User Objection Features in 1.1 build
and resubmitted it to the app store but still rejected by the app store.
I'm getting issue from apple like this
Your app still includes features that objectify real people, which
could be interpreted as being offensive or mean-spirited.
Next Steps
Please remove all offensive and mean-spirited content from your app
and submit your revised binary for review.
Please see attached screenshots for examples of objectifying content.
can you point it out to me what is the mistake i am doing and should be revised?
Please help me on this Thanks in advance.
What options do you present for taking the input on rating? May be the wordings you use are being considered offensive.
Taking user rating is not an offensive feature, you need to look into the next level of details which is causing rejection.
I'm developing an iOS app and I'm not sure if some of the things I've done will be approved by Apple. Sometimes the reasons of rejections are very hard to predict and I'd like to know if something is wrong earlier.
Does it make sense to submit an unfinished app to Apple Store with a release date couple months in the future just to get some valuable feedback from Apple? I'm pretty sure they'll reject such an app, because they don't allow beta versions to be submitted to Apple Store. But, will they provide me some valuable feedback, that certain parts of the app or of the implementation need to be changed for the app to be approved when it's finished? Or, will they just reject it because it's not finished and won't provide any feedback about the already implemented parts?
Thanks,
Michal
Tricky. In my experience, if they reject it, they'll reject it for the first problem they find. They won't give you a list of reasons. They won't review it thoroughly once they've seen a reason to say no.
So, while I can't see any harm in doing it, there's no guarantee you'll be rejected in a way that gives useful feedback. More likely they'll pick you up on a simple point, and you'll be no wiser.
Updated
Plus, bear in mind, the review system isn't wholly consistent. I've had apps accepted by one reviewer, only to be rejected next time because the later reviewer is more thorough. You could have your alpha app accepted, only to see the polished version rejected after months of work.
A better approach might be to discuss the specific rule you might be breaking on the Apple Dev Forum.
Prior approval of an app, or a type of app, creates no precedent for future app approvals. Developers have submitted bug fix updates and had that app update rejected for violating some App store rule or guideline completely unrelated to the changes.
However an app rejection will give you valuable feedback. So if you think your app is on the edge of acceptability, a rejection might provide useful information regarding the risk of continued development.
For any submission, you need to make sure the app won't be rejected outright for bugs or crashes or other reasons unrelated to the feedback you are seeking.
And if you are a featured high profile or famous developer, then Apple might contact you regarding feedback on your apps under development.
it's almost never checked for critical bugs, it's checked for using private APIs, breaking license agreements and so on.
What shoud I do/know before I'll send my first ios app to Apple App store? Thak you.
Test the App
Let others test your App (try to find people with different devices and iOS versions)
Check the official guidelines and make sure your App does not use private API's
And, most important: be patient, review may take more time than expected.
Be ready to wait. Patience is a virtue.
Follow official documented guidelines and you will be unlikely to encounter any problems. 99% of bad stories you've heard about the app submission process are from people who didn't.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 9 years ago.
Improve this question
Can anybody help me out to know the possible reasons for which Apple store can reject or raise objection to submit any iPhone application.
Here are possible reasons (unofficial, from here):
Vibration. It is not permitted to use continuous vibration in your apps - short bursts as warnings is all that is allowed. Don’t bother trying to set up a timer to keep the vibration going, it will cause your app to be rejected.
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.
Improper handling of editing in tableview cells. Also obvious, but be aware that if you enable table cell editing, you’ll have to manually specify which cells should respond to editing controls and which should not. We had some random prefs cells in one of our early apps that were able to be swiped to bring up a ‘delete’ badge. Of course it didn’t do anything, but Apple justly considered this poor design and rejected our app.
Icons. Make sure the 57 pixel icon is identical to the 512 pixel version. Also, use a different icon if you are creating ‘lite’ and ‘pro’ versions of your app (i.e., free and paid). Using the same icon for both sends your app straight to … you guessed it … the bin.
Copying existing functionality. This one is much more subtle and insidious, and has probably affected the great percentage of developers. In addition to the widely publicized Podcaster debacle, reports from user comments indicate that Apple is casting a wide net when looking for duplicated functionality. Mini web browsers, or apps that essentially show web pages, seem particularly vulnerable, even if they add new and/or useful functionality. Stay away from email clients as well.
Using appropriate keyboard type. If your app asks for a phone number or other numeral-only input and you present a keyboard that also includes the possibility of entering standard alpha-numeric input … yep. (Thanks Jeremy1026)
Version numbers. If your app is currently at version 0.99 or below, you’d better consider giving it a promotion as Apple seems to prefer 1.0 and above. One of ours was recently rejected for being .016, with a message suggesting that our version number wasn’t even numeric. When we resubmitted the same app from scratch as version 1.0, it went through.
Network Reachability. If your app requires any type of network access you need to make sure it works when that access isn't available. If it doesn't it will be rejected. Apple provides sample code to test this which you can use as-is in most cases: https://developer.apple.com/library/content/samplecode/Reachability/Introduction/Intro.html
And last, but not least:
Flatulence Don’t even try. ;-) UPDATE: sorry, this seems to be outdated by now. Apple makes a lot of money now with "fart apps": see this article.
Edit:
Here is a link to a recent article about ten iPhone Apps That Didn't Make Apple's App Store.
And a tip: Apple has a Mac app called Application Loader that you could install. Once you install it, it analyzes your app's zip file. It verifies all the certificates, icons, and other things are correct before submitting to Apple. Using the Application Loader minimizes your chances of app rejection.
Another interesting resource: App Store Roundtable: Transparency and the Approval System (appleblog.com)
Yet another edit:
New rules by February 2010: "No Swimsuits, No Skin, And No Innuendo" (source: TechCrunch article, Wobble author's blog)
By the way: during the iPhone 3.0 preview event (march 2009), an Apple spokesman told that 96% of all submitted application were approved.
Apple have now (as of 9th September 2010) published their official list of app store review guidelines:
appstore approval guidelines
(apple developer login required)
or a mirror here:
app store guidelines
Will apple want to create an app like that in the future? If (yes) reject.
Do you have a really awesome idea that apple may want to use in the future if(yes) reject
Here's the video of the SDK announcement that describes Apple published list of rejection criteria:
SDK Announcement
As others have noted, Apple also seem to have a bunch of other conditions that they don't publicise. Note that rejection notices are now covered by the NDA.
I can't confirm this but it makes sense, but people are reporting their apps being rejected for being too simple or too trivial.
Just got a bounce for handling network outages badly. If you connect to the network, be prepared to handle any error conditions that may come up.
My paid version of app was rejected by appstore.
After Purchasing and downloading app first screen was "User Agreement" and when user taps on " I agree" only then he is able to continue using app.
Apple described the reason of rejection "when user purchased app from appstore and download in phone then you must not restrict user to Agree with Agreement" instead display your agreement before downloading app in iTunes.
Amazingly, apps can get rejected for trying to keep their interface consistent with Apple's own apps. (ie, using pinch zoom/expand gestures)
There is a site I know which can help you generate great advertising ideas with iPhone. see this site:
http://itunes.apple.com/app/adpack/id359562015?mt=8
I submitted a paid app to app store but get rejected and i learned another possibility of app rejection
My app was Game Center enabled. When app starts first screen was login screen that prompt user to login through GameCenter to continue.
They rejected the app giving reason- As user will not be able to get services of your app unless he is not logged in with Game Center although he paid you to download app. You cannot restrict user to login through Game Center each time before app starts.
From 1st May,2013 onwards if we don't support iPhone 5, your app will be rejected.So iPhone 5 support is must.