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.
Related
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 2 years ago.
Improve this question
Apple started to reject our app because they can't access our app because of geo-restriction. We have also a video which shows our app's demonstration in the review process. And Apple Review Team can't access app in U.S.A. It's a gambling app and it must be geo-restricted according to the App Store Review Guidelines.
5.3.4 Apps that offer real money gaming (e.g. sports betting, poker, casino games, horse racing) or lotteries must have necessary licensing and permissions in the locations where the App is used, must be geo-restricted to those locations, and must be free on the App Store. Illegal gambling aids, including card counters, are not permitted on the App Store. Lottery apps must have consideration, chance, and a prize.
We show a pop up to user which says basically that they could not access to the app because of the geo-restricted.
Apple Review Team's Response:
5.3.4 Guideline 2.1 - Performance - App Completeness
We discovered one or more bugs in your app when reviewed on iPhone running iOS 13.5 on Wi-Fi.
Specifically, upon launch, your app displayed an error message. All apps submitted to the App Store must function correctly and provide access to all features and content at the time of review, regardless of network, device capability, location, etc.
Next Steps
To resolve this issue, please run your app on a device to identify any issues, then revise and resubmit your app for review.
If we misunderstood the intended behavior of your app, please reply to this message in Resolution Center to provide information on how these features were intended to work.
For new apps, uninstall all previous versions of your app from a device, then install and follow the steps to reproduce the issue. For updates, install the new version as an update to the previous version, then follow the steps to reproduce the issue.
How can we make the app geo-restrict and also provide access to all features?
Thank you.
Specifically, upon launch, your app displayed an error message.
Was your error message clear to the user, explaining what had happened and what they must do to resolve the issue? Did you explain this restriction in your App Store description (particularly if you're submitting to any store where the restriction would apply), and in your App Store submission? Even if the user cannot proceed, they should have a good experience. It shouldn't just be an alert saying "go away." A legitimate user might launch your product while traveling, and it should be clear that they need to wait until they get home.
If we misunderstood the intended behavior of your app, please reply to this message in Resolution Center to provide information on how these features were intended to work.
This is the key point. Contact them. You may need to give them a backdoor that unlocks it for the Apple site. You may need to give them a special login. They may work with you in other ways. But contact them.
When you say "keeps getting rejected," that suggest more to the story. Did you contact them and did they tell you other things? Did you just keep submitting?
even though your app is geo restricted,you need to implement code for testing purpose so that they can test all the functionality of the app.i suggest you create a user for testing that will bypass the geo restriction and specify the name and password at notes in app submission.
Some iOS apps that have not yet launched on the iOS app store now (Super Mario) have the ability for users to click a button on the app store listing to be notified when the app becomes available. How is this done? This will obviously impact a large number of apps/developers. If this is not yet possible for general release apps from the general developer community, only for apps that have specially arranged it with Apple, please update answers to this question when/if this becomes generally available, which seems likely.
Please do not downvote this question as 'off topic' given that the answer to this will obviously be important to a lot of iOS developers who turn to SO for answers (like I just did).
Thanks
This is not a feature part of the Apple Developer Program.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
an app I have been working on got rejected by Apple,
here is the message I got from Apple when it got rejected:
From Apple
22.2 - Apps that contain false, fraudulent or misleading representations or use names or icons similar to other Apps will be rejected
22.2 Details
Your app or its metadata contains misleading content.
Specifically, the app screenshots and splash screen are from a well known TV show belonging to Keshet without the rights to use it.
We’ve attached screenshot for your reference.
Next Steps
Please remove or revise any misleading content in your app and its metadata.
Since your iTunes Connect Application State is Rejected, a new binary will be required. Make the desired metadata changes when you upload the new binary.
NOTE: Please be sure to make any metadata changes to all App Localizations by selecting each specific localization and making appropriate changes.*
some background,
I did develop this app for Keshet with permission, but I did not include any kind of permission from Keshet when submitting.
Yes, my bad, I just didn't know it was required.
Anyway, my question is,
would replying to Apple through the resolution center and including a document from Keshet's legel dept. be enough to resolve this issue?
or do I need to go through the whole process again, submitting a new binary etc.?
or perhaps something else?
Also, does this kind of rejection means that every other aspect of the game I submitted is okay?
because they only reacted to the rights to use Keshet's properties.
You should follow the instructions Apple gave you. (For example: "Since your iTunes Connect Application State is Rejected, a new binary will be required.")
Apple never promises that every other aspect is ok. Ever. Even the fact that you're updating an existing product doesn't promise that there won't be rejection due to things that were tacitly approved in previous versions. The only approval that really matters is when you see your app on the app store, and even then they sometimes retroactively reject apps that are already there. There are no guarantees in life.
StackOverflow isn't going to be able to give you any better information or advice than Apple will. If you have questions about their current process (which changes from time to time anyway), you need to speak with Apple.
Please follow App Store Review Guideline before you submit your App to App Store. In your case of Copyright issue follow section number 22 - Legal Requirements.
If you have copyrights to use particular Image , Logo or content then send that reference while submission to App Store.
After removal of objectionable content from project create new build and upload it again to App Store submission process.
After reading documentation about glances i can't define how they will appear on the glances screen. Will it be automatically after installation or user must manually add glance to the screen (like today widget)?
Glances will not be added automatically. There will be an AppleWatch companion app on the phone where you can opt in to add your Glance to the watch - much like Today Widgets
We don't have any formal guidance from Apple about how this will be managed at this point.
However, it seems highly unlikely that they will be automatically added to the Watch, without at the very least a prompt to the user asking them if they want to install them. It is less clear whether Watch glances and apps would be like third party keyboards, that sit silently in their companion app unless you visit settings to install them, or whether the installation might be a more prompted experience, such as when an app asks for permission to enable location services.
I think the most likely scenario is that configuration will be primarily (or almost entirely/entirely) on the phone, as per Joseph DeCarlo's response. However, this could also be handled akin to location services (prompt in-app on the phone to approve install, modify in Settings) as described above, or like third party keyboards solely via the (increasingly broad, and a bit confusing) Settings app. I hope that's not the case and we get a dedicated app for managing the watch, but at this point we do not have information to know for sure.
I would imagine it is automatic after installation. But only shows if the user has your app open on the watch.
I am basing this on the scenario's shown in the documentation. E.g.
while the glance for an airline app might display gate information for an upcoming flight
and how I use my Pebble, in that the application I have open is one that is meaningful to me at that time. E.g. The music controls when I am playing music on my phone. Or the Misfit App when I am walking to see how I am doing.
Until we can get our hands, or wrists, on an Apple Watch, we can't know for certain.
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.