I have submitted an update for my already approved app on Apple store yesterday. It got rejected with this message
"Your app icon and screenshots include content which is too similar to
iPad and iPhone, which creates a misleading association with Apple
products."
The app is available on iPhone as well as iPad. I did not get this issue when I submitted the app the first time as well as 5 updates after that. I can change the screenshots but do I need to have seprate App icons for iPhone and iPad?
How can I resolve this?
They are complaining that your icons look too much like Apple's own icons. Make entirely new ones.
Yes, as apple says:
Every app must supply both small and large app icons. The small icons are used on the Home screen and throughout the system once your app is installed. The large icon is used by the App Store.
You can read more about it here:
https://developer.apple.com/ios/human-interface-guidelines/graphics/app-icon/
Apple has rejected my App stating that
Reasons
22.2 - Misleading
22.2
We found that one or more of your submitted In-App Purchase products, and/or its metadata, contains content that could be misleading to users. This does not comply with the App Store Review Guidelines.
It will be appropriate to remove the dot lock password option within the App. This is misleading to users. A screenshot is attached for your reference.
What does this mean. I have put both the dot lock and passcode lock options in my app. The users can switch between the two from settings of my app. I don't know how this could be misleading to users?
This is the screen shot
If you haven't done so I would suggest you to read up on the iOS Human Interface Guidelines Like #Matt said in the comments, Apple is extremely picky when it comes to UI .
Unlike Android, apple wants you to design your app in a way that the user can use your app like any standard one. In your case a passcode inside of your app could be misleading.
Yes I know how you feel I had few apps rejected for things similar to this.
They must be a different way you can design this.
The icon was not shown when archiving for distribution. though, it was shown when testing on a device.
I faced no errors, the process went smoothly and the app was uploaded successfully to the App store.
I keep reading question about (icon is not shown in archives) but I can't understand why such thing is important which lead me to my question.
So, the question is: Will the icon be shown when the users download the app? and if yes, why should I care if the icon is shown or not while archiving??
You shouldn't really care for that, it'll be shown to the users when downloaded from the app store
Can I submit to App Store an app that only launch Safari with one specific url?
If the answer is "yes": Can I hide default image, that is, can I launch Safari inmediatly from Main without show deafault image? (I can do it in BlackBerry and Windows Mobile)
I know.. is a horrible app but is what I have to do..
Thanks!
See section 2.12 of the App Store Review Guidelines:
Apps that are not very useful, are
simply web sites bundled as apps, or
do not provide any lasting
entertainment value may be rejected
And section 12.3:
Apps that are simply web clippings,
content aggregators, or a collection
of links, may be rejected
In short, the answer is: Yes, you can submit whatever you like. My guess based on the guidelines above, though, is that such an app is unlikely to pass the review process.
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.