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.
Anyone know if there is anything you have to do as a developer of an app to get your app to be suggested form the lock screen in iOS 8 (I'm talking about when the app isn't installed, so it takes you to the app store)? The only information I've been able to find about this is speculative at best -- most seem to conclude that this is either based off of the "apps near me" that the app store has, or direct arrangements made with Apple. Anyone know for sure?
This can be achieved using Passbook
https://developer.apple.com/library/ios/documentation/UserExperience/Conceptual/PassKit_PG/Chapters/Creating.html#//apple_ref/doc/uid/TP40012195-CH4-SW53
I have an app in the App Store with a number of different soundboards. I release updates every once in a while with new content. Some content however is forbidden by Apple (foul language) resulting in updates being rejected. To make updating faster and easier, I'm building an update which automatically downloads new content from a server. So my question is; what will happen when content in an update is found inappropriate by Apple? Will my app be removed from the App Store? Will they ban my developer account? Will they even find out? The app is in Dutch and therefore it's quite hard te determine what is permissible by App Store policy and what is not. I had some explicit content accepted in updates, while other seemingly less explicit content got rejected.
Your app is never reviewed by the same person and so much depends on the reviewer. There is a Dutch review team so regarding not noticing due to language, I wouldn't rely on it.
Now I have released apps that breach API terms with youtube and the apps existed on the appstore for a long time. Once it was brought to Apple's attention, they removed the app but did not suspend my developer account (I imagine that you have to break policy repeatedly for this and do something much worse than simply having foul language in your app). In my opinion, If Apple notices that your app has foul language on it, they will simply remove it from sale and ask you to submit an update which addresses the issue as they did in my case.
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.
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.