Apple App Store Review Guidelines, Common Rejection Cases, and Lessons Learned

Author Introduction : Claire works in iQIYI's Technology Product Center PMO. She has experience in Android/iOS development and now focuses on software project management and agile process improvement.

Overview : The iQIYI iPhone client often faces longer review times and more rejections than the iPad client due to higher functional complexity.

Apple Review Rules Overview

The review standards are divided into five categories: safety, performance, business, design, and legal. The following sections summarize key points and common pitfalls.

1. Safety

Guideline 1.1 prohibits offensive or harmful behavior, violence, pornography, and discrimination. Apps must not contain content that could cause physical harm or violate user privacy.

Guideline 1.2 requires user‑generated content (UGC) features to include reporting mechanisms and to remove offensive material.

Guideline 1.3 restricts charitable fundraising within the app unless the app is free and the fundraising occurs outside the app (e.g., via Safari).

2. Performance

Guideline 2.1: The submitted build must be the final version; no test or placeholder pages are allowed.

Guideline 2.3: Metadata (app name, screenshots, preview videos) must accurately reflect the app’s functionality. Preview videos must be captured from the app itself, not contain ads.

Guideline 2.4/2.5: Hardware compatibility and software requirements must be clearly described.

3. Business

In‑app purchases (IAP) must be used for unlocking features or consumables. All IAP items must be non‑expiring and have a recovery mechanism. Incorrect purchase type selection leads to rejection.

Promotional codes (coded gift packs) are prohibited. Gift packs must not be tied to downloading other apps or performing other actions.

Apps must not require users to rate, watch ads, or complete other tasks to access core functionality.

4. Design

Copying other apps or releasing duplicate apps is forbidden. HTML5 games are allowed only if they are not merely code distribution.

5. Legal / Privacy

Apps must provide a privacy policy, obtain user consent before data collection, and must not force login unless required for account‑based features. Collecting passwords or private data without consent results in removal from the Developer Program.

Common Rejection Cases

Metadata inaccuracies : Using popular drama titles in the app name caused rejections; the fix was to simplify the name.

Preview video violations : Including ads in preview videos led to rejection; the solution is to use only in‑app captured video.

In‑app purchase icon similarity : Identical icons for different IAP items were rejected; distinct icons are required.

Rating mismatches : A game was flagged for gambling content while the app’s rating indicated only mild content; the rating was corrected.

User‑generated content : Lack of a reporting mechanism caused a rejection; adding filters, reporting, and the ability to block offending users resolved the issue.

Lessons & Future Plans

1. Conduct regular training on Apple review guidelines across product and development teams.

2. Before each release, each business line reports potential review risks and prepares mitigation measures.

3. Build a knowledge base of past rejection cases to guide future development.

4. Focus upcoming reviews on privacy, IP, in‑app purchase handling, and game‑related features.

5. Strengthen communication between design, development, and compliance to reduce review rejections.

For the full Apple Review Guidelines, see: https://developer.apple.com/app-store/review/guidelines/cn