EasyApp

Common Apple Review Rejection Solutions

Learn about common Apple review rejection solutions

During the App Store review process, many developers encounter various rejection situations. This document summarizes the most common review rejection reasons and their corresponding solutions to help you quickly identify issues and resolve them effectively.

Quick Navigation

Click the categories below to jump to the corresponding issue:

Technical Issues: Crashes/Incomplete | Private API

Privacy Compliance: Privacy Policy

Payment Issues: Payment Violations | Subscription/EULA

Content Issues: Copyright | Too Simple | Misleading | Screenshots | UI Innovation

Special Categories: Children's Apps

Review Process: Test Accounts

App Crashes or Incomplete Functionality (Guideline 2.1)

Issues

  • App crashes, shows white screen, or key features don't work during review
  • Contains test data, unfinished placeholder content

✅ Solutions

  • Test coverage for all iOS versions and devices (especially latest iPhone and iPad)
  • Remove test accounts, temporary data to ensure reviewers can use it normally
  • Check backend service stability to avoid API unavailability during review

Privacy Policy Non-compliance (Guideline 5.1)

Issues

  • No privacy policy provided, or policy doesn't clearly explain data collection methods
  • Collecting sensitive information without user authorization (like location, camera, contacts)

✅ Solutions

  • Add privacy policy links in App Store Connect and within app (must clearly explain data usage)
  • All permission requests must include explanations (add NSLocationUsageDescription etc. in Info.plist)
  • Check third-party SDKs (like ads, analytics tools) for compliance

Payment Method Violations (Guideline 3.1)

Issues

  • Virtual goods, subscription services don't use Apple In-App Purchase (IAP), instead use WeChat, Alipay etc.
  • App guides users to bypass IAP (like suggesting "cheaper on official website")

✅ Solutions

  • Digital content, membership subscriptions must use Apple IAP (Apple takes 30%/15% cut)
  • Physical goods or offline services (like food delivery, ride-hailing) don't need IAP
  • Avoid mentioning external payment methods in app, otherwise will be rejected

Subscription Compliance Issues (Guideline 3.1.2 - Business - Payments - Subscriptions)

Issues

  • Missing "Terms of Use (EULA)" link
  • Paywall/subscription page doesn't display terms of use link
  • App Store Connect description doesn't include terms of use link
  • Subscription terms are unclear or incomplete

✅ Solutions

  • Add terms of use link on paywall/subscription page, users must see it before purchasing
  • Add terms of use link in App Store Connect description, format as follows:
Terms of Use: https://www.apple.com/legal/internet-services/itunes/dev/stdeula/
Privacy Policy: [Your privacy policy link]
Terms of Service: [Your terms of service link]
User Agreement: [Your user agreement link]
  • Use Apple Standard EULA, link: https://www.apple.com/legal/internet-services/itunes/dev/stdeula/
  • Provide terms of use entry in app settings page

Required Locations for Terms of Use

  1. Paywall/Subscription Page: Display "Terms of Use" link near the purchase button
  2. App Store Connect Description: Add terms of use link at the end of app description
  3. In-App Settings Page: Provide entry to view terms of use
  4. App Store Connect > App Information > License Agreement: Fill in EULA link

Issues

  • App name, icon, content allegedly copies other well-known products (like "TikTok cracked version")
  • Using copyrighted materials without authorization (like movies, music, game characters)

✅ Solutions

  • Ensure app name, icon, UI design are original, avoid misleading users
  • Don't use unauthorized brand names (like "ChatGPT official version")
  • If using open source materials, follow corresponding licenses (like CC BY, MIT)

Functionality Too Simple (Guideline 4.2)

Issues

  • App is just a web wrapper (like pure H5 page)
  • Functionality duplicates system built-in apps (like calculator, flashlight)

✅ Solutions

  • Add unique features (like AI assistance, social interaction)
  • Optimize user experience, avoid submitting "template" apps

Misleading Users or Keyword Stuffing (Guideline 4.3)

Issues

  • Title or description contains many irrelevant keywords (like "Free VPN 2024 best speed super fast no ads")
  • Functionality doesn't match promotion (like claiming "AI drawing" but no such feature)

✅ Solutions

  • App Store description should be concise and authentic, don't exaggerate features
  • Avoid keyword stuffing, title under 30 characters is better

Using Private APIs or Security Vulnerabilities (Guideline 2.5.2)

Issues

  • Calling unpublished private APIs (like getting device UDID)
  • Code has security vulnerabilities (like SQL injection, unencrypted transmission of sensitive data)

✅ Solutions

  • Use Xcode's API checking tools (like nm or otool)
  • Ensure network requests use HTTPS, encrypt sensitive data storage

Children's App Non-compliance (Guideline 1.3 & 5.1.4)

Issues

  • Not complying with COPPA (Children's Privacy Protection Act), collecting minor data
  • Contains ads or content unsuitable for children

✅ Solutions

  • Prohibit collecting children's personal information (like location, device ID)
  • Ad content must be suitable for children (avoid in-game purchase inducement)

Not Providing Test Accounts or Poor Review Communication (Guideline 5.6)

Issues

  • Reviewers can't log in (no test account provided)
  • Not responding promptly or incomplete modifications after rejection

✅ Solutions

  • Submit test accounts in App Store Connect (if app has login functionality)
  • After rejection, explain modifications in detail through Resolution Center

App Screenshots Inconsistent with Actual App (Guideline 2.3.3 - Performance - Accurate Metadata)

Issues

  • App Store screenshots don't match the actual app interface
  • Screenshots show non-existent features or interfaces
  • Content in screenshots doesn't match the current app version
  • Using screenshots from other apps or template screenshots

✅ Solutions

  • Ensure screenshots accurately reflect current app functionality, don't show unimplemented features
  • Use the latest version of the app for screenshots, ensure interface consistency
  • Avoid using template screenshots or placeholder images, use actual app interfaces
  • Screenshot order should match app usage flow, help reviewers understand the app
  • Check that text, buttons, and features in screenshots all exist and work properly

Intellectual Property Issues / Lack of UI Design Innovation (Guideline 5.2.5 - Legal - Intellectual Property)

Issues

  • App interface design is highly similar to other well-known apps
  • UI layout, color scheme, and interaction methods lack innovation
  • Suspected plagiarism or imitation of other apps' design styles
  • Using unauthorized design elements or icons

✅ Solutions

  • Redesign the UI interface to ensure unique visual style and brand characteristics
  • Modify the color scheme to use different color combinations from competitors
  • Innovate interaction methods to provide unique user experience rather than simple copying
  • Use original icons and design elements, avoid using others' design resources
  • Reference design guidelines rather than plagiarize, follow Apple design guidelines but with your own characteristics
  • Hire professional designers to create a recognizable brand visual system

Design Resources Recommendations

If you need to redesign the UI, you can refer to the following resources:

Continuously Updating

This document will be continuously updated with the latest review rejection cases and solutions. Bookmark and check regularly.

💡 Prevention Tips

📋 Pre-submission Preparation

  • • Thoroughly test on various devices and iOS versions
  • • Remove all test data and placeholder content
  • • Ensure screenshots match actual app

📖 Compliance Requirements

  • • Regularly read Apple review guideline updates
  • • Maintain app originality and uniqueness
  • • Digital content must use IAP

🔒 Privacy & Security

  • • Provide clear privacy policy
  • • Include explanations for all permission requests
  • • Use HTTPS for encrypted transmission

💬 Review Communication

  • • Provide complete test accounts
  • • Respond promptly to review feedback
  • • Explain in detail through Resolution Center

Friendly Reminder

Apple's review purpose is to ensure high-quality, secure and reliable apps in the App Store. Following these guidelines not only increases approval rates but also provides better experience for users.

Last updated on