Avoiding common issues
We’ve highlighted some of the most common issues to help you better prepare before submitting for review. On average, more than 40% of unresolved issues are related to Guideline 2.1: Application Integrity, which covers crashes, placeholder content, incomplete information, and more.
See “Tips for prevent common review issues”
Drops and bugs
Submit items for review only when they are complete and ready to be published. Make sure you do extensive testing on devices running the latest software and fix any bugs before shipping. See guideline 2.1.
Broken links
All links in your application should work. All apps require a link to user support with up-to-date contact information and a link to their privacy policy. See guideline 2.1 and guideline 5.1.
Placeholder Content
Finalize all images and text before submitting for review. Items that are still in progress and contain placeholder content are not ready to distribute and cannot be approved. See guideline 2.1.
Incomplete information
Enter all necessary details for the review in the App Review Information section of App Store Connect. If some features require login, please provide a valid demo account username and password. If there are any special settings to set, please include the details. If the features require an environment that is difficult to replicate or require specific hardware, be prepared to provide a demo video or the hardware. Also, make sure your contact information is complete and up to date. See guideline 2.1.
Specific documentation is required for certain scenarios and types of applications. Here are some examples:
- If the app is for kids and contains third-party ads, please provide a link to the ad services’ publicly documented practices and policies for apps in the Kids category, including human review. of ad creatives by age. See guideline 1.3.
- If the app works with medical hardware, please provide a copy of the regulatory clearance for the locations where the app is available. See guideline 1.4.
- If the app features third-party trademarks or copyrighted content or allows users to stream or download third-party content, please provide permission to do so. Examples include streaming video and marketing that uses images of celebrities, sports, movies, or music. Please refer to guideline 4.1 and guideline 5.2.
- If the app supports services that require a license, such as real money gambling and gambling, lotteries, raffles, and VPN licences, please provide permission to do so. Please note that license requirements may vary by region. See guideline 5.
Privacy policy issues
Please ensure your privacy policy complies with guideline 5.1 and:
- Identify the data the app collects, how it collects that data, and all uses of that data.
- You confirm that any third parties with which the app shares user data provide the same or equal protection of the user data that is established in the privacy of the application. policy.
- Explains your data retention and deletion policies and describes how a user can revoke consent and/or request deletion of their data.
Requests Unclear Data Access
When requesting permission to access user or usage data, you must clearly and fully describe how your application will use the data. Including an example can help users understand why your app is requesting access to their personal information. See guideline 5.1.
If your app’s code references one or more APIs that access sensitive user data, your app’s Info.plist file must contain a $!{infoPlistKey} key. with a user-facing purpose string that clearly and fully explains why your application needs the data. All apps submitted to the app store that access user data must include a purpose string.
More about asking for permission
Inaccurate screenshots
Screenshots must accurately communicate value and functionality. Use text and image overlays to enhance the user experience, not obscure it. Please make sure that the UI and product images match the corresponding device type in App Store Connect. See guideline 2.3.
Substandard User Interface
Apple places a high value on clean, polished, and easy-to-use interfaces. Make sure your user interface meets these requirements by planning your design carefully and following our design guides and user interface design dos and don’ts.
Web snippets, content aggregators or a collection of links
Your app should be attractive and useful, and take full advantage of unique iOS features. Websites served in an iOS app, web content that is not formatted for iOS, and limited web interactions do not constitute a quality app. See guideline 4.2.
Submitting Similar Apps Repeatedly
Submitting multiple apps that are essentially the same blocks the app store review process and risks your apps not pass the reviewImprove your review experience, and the experience of your future users, by carefully combining your apps into one. See guideline 4.3.
Deceiving users
Your application must work as advertised and must not give users the impression that the application is something it is not. If your app seems to promise certain features and functionality, you should deliver on them. See guideline 2.3.
Not enough lasting value
If your app doesn’t offer many features or content, or only applies to a small niche market, it may not get approved. . Before you create your app, take a look at the apps in your category on the App Store and consider how you can provide an even better user experience. See guideline 4.2.
Submitted by the wrong entity
Certain types of applications must be submitted by the legal entity providing the services rather than an individual developer. These applications include, but are not limited to, those that require sensitive user information or provide services in highly regulated fields such as banking and financial services, cryptocurrency, healthcare, gambling, and air travel. If you need to provide documentation or partnership authorization, please attach the files in the Attachments section in App Store Connect and provide descriptions or links in the Release Notes field. See guideline 3 and guideline 5.1.1.
.