Apple has a very strict approval process. As a result, it's inevitable that you'll face rejection—but a fixable one! Below, you'll learn how to check out rejection reasons through iTunes Connect, and we'll detail some of the most common ones we see.
Checking Your App's Rejection Message
- Read the reasoning behind Apple's rejection by logging into your iTunes Connect account.
- Click My Apps.
- Select your rejected app from the list to proceed to view the app listing page.
- The following red-highlighted message appears at the top of the listing:
App review has rejected this version. Visit Resolution Center
- Click the Resolution Center link to view the rejection message.
- Here you'll find a rejection code with a short description. Apple often attaches screenshots as well. If you understand the reason for the rejection, you can make any necessary changes within the app, then contact support so we may resubmit the application.
Note: Please do not republish the application through your dashboard, as you may be charged again. If you're unclear on the reason for the rejection, please email our support team with the app code and rejection description, and we will help you. We've seen (almost) every rejection in the book over the years, and we're more than prepared to help.
Common Rejections & How to Fix Them
For a full list of rejection reasons, refer to Apple Support article App Store Review Guidelines. We have listed the most common ones that we encounter below. If Apple rejects your App or you don't believe it can pass its review process, you can still publish for Android and Web App! Web App publishes are automatic, and Google tends to have less strict guidelines.
2.3 Customers should know what they’re getting when they download or buy your app, so make sure your app description, screenshots, and previews accurately reflect the app’s core experience and remember to keep them up-to-date with new versions.
- Your app’s location permission modal alert references GPS running in the background, which is not relevant to the app's functionality.
- We were unable to locate some of the features described in your metadata.
Fix: Disable the Walkthrough feature when publishing and re-enable when the app is published in the App Store, also ensure that the app features are related to the app name and purpose
2.3.6 Answer the age rating questions in App Store Connect honestly so that your app aligns properly with parental controls.
Translation: The rating you have selected is inconsistent with the content of your app. Example: Your app is rated as 4+ age but it allows filtered access to YouTube, where content with mature or suggestive themes can be accessed.
Fix: Change the age rating or disable the features that allow filtered access to content out of the age rating.
2.9: Apps that are “beta,” “demo,” “trial,” or “test” versions will be rejected.
Translation: Somewhere within your app is text that reads "beta, test, demo, trial, coming soon, etc." As a result, Apple thinks your app is incomplete and wants to see a finished product.
Fixes: Remove this text and put in real content—the more complete, the better. There should be no filler or demo text within an app when being submitted to Apple — taking the extra time to complete it in full means less time waiting for Apple's approval.
2.12: Apps that are not very useful, are simply web sites bundled as apps, or do not provide any lasting entertainment value may be rejected.
2.13: Apps that are primarily marketing materials or advertisements will be rejected.
Translation: Apple thinks your app focuses primarily on marketing & promotion of the business and doesn't foster user engagement. Having a lot of Info & Web Site features that highlight the business but don't provide functionality will often lead to one of these rejections.
Fixes: Try to remove or condense your Info & Web Site features (aim for 3 or less each), plus add as much native functionality as possible—while still being relevant to the business (no need for a car finder feature in an app for a DJ). Make sure there's a clearly illustrated purpose for the app, and it contains useful and dynamic content. Coupon, contact-based, and media-oriented features are easy wins.
2.16: Multitasking Apps may only use background services for their intended purposes: VoIP, audio playback, location, task completion, local notifications, etc.
Translation: Your app most likely included Audio Background Play, a setting that should only be activated if there's an active Music or Podcast feature within your app. Without these features, Apple sees the background play feature as irrelevant to your app.
Fixes: The app will need to be rebuilt and resubmitted without Audio Background Play. To avoid this, you can alternatively enable a Music or Podcast feature, and we can resubmit the existing app we built. Just write into us in with your preference, and we can take care of it. For the future, also make sure to leave this box unchecked in the Publish Step if it doesn't apply to your app.
Note: With metadata rejections, your app maintains its spot in Apple's queue, so the review timeline doesn't start from scratch. Generally, something needs to be changed in iTunes Connect.
3.1: Apps or metadata that mentions the name of any other mobile platform will be rejected.
Translation: Your app includes Android, Windows, or other platform mentions, either in text or image form. Usually, this applies to the app description, the background images, or the splash loading screen.
Fixes: You'll need to remove the problem mentions and resubmit. Usually, this is an easy fix, but we still suggest writing into us to confirm once you've resolved the issue so that we can verify and resubmit.
3.8: Developers are responsible for assigning appropriate ratings to their Apps. Inappropriate ratings may be changed/deleted by Apple
Translation: Your app contains images or text that warrants an elevated rating. The most common ones are alcohol/drug content, nudity, violence, etc., but there are some tricky ones, like unlimited access to web content (just providing a web link), that is a bit less straightforward.
Fixes: Simply upping the rating for the appropriate category will do the trick. Again, we can take care of this for you. Just send us the rejection message, and we can log in and adjust.
4.8 Apps that exclusively use a third-party or social login service (such as Facebook Login, Google Sign-In, Sign in with Twitter, Sign In with LinkedIn, Login with Amazon, or WeChat Login) to set up or authenticate the user’s primary account with the app must also offer Sign in with Apple as an equivalent option
Translation: Your app uses a third-party login service but does not also offer Sign in with Apple
Fix: An interim solution is to disable all Sign-in options during the publishing process and re-enable once the iOS app is published. Sign in with Apple Guidelines and Requirements
10.6: Apple and our customers place a high value on simple, refined, creative, well thought through interfaces. They take more work but are worth it. Apple sets a high bar. If your user interface is complex or less than very good, it may be; rejected
Translation: Apple thinks the quality/user experience of your app is lacking. This typically means the layout/ navigation is poorly structured, the pictures are highly pixelated or stretched, or it merely appears much time wasn't spent refining the design.
Fixes: Run through your app feature by feature using our native preview app.
- Low-quality images should be replaced, and any specific items they mentioned should be addressed as well.
- Make sure background images appear well, and your color scheme is simple & aesthetically pleasing.
- The text should be easy to read and not cut off.
- If your app was uploaded for iPhone and iPad, we could also try resubmitting for iPhone-only.
- Poor images will only look worse on the iPad as they're enlarged, and Apple places a bit less emphasis on iPhone-only apps. However, the previously mentioned tips are best.
Scraping and Aggregation
12.3: Apps that are simply web clippings, content aggregators, or a collection of links, may be rejected
Translation: Apple thinks your app provides a limited set of features and is a web congregate within an app shell. In other words, you have too many Web Site features in your app.
Fixes: Immediately condense or remove a good portion of your Web Site features. Add in as much native functionality as possible while still being relevant to the business.
Charities and Contributions
21.2: The collection of charitable donations must be done via a web site in Safari or an SMS
Translation: Your app contains a link to a site that allows users to make donations. Apple requires links like these to open in a browser, rather than within the app.
Fixes: Either remove the link or check the box for "Open in new browser" This checkbox is under the web view's settings in the Web Site feature. Once verified, the site will open in Safari, rather than within the app.