Mobile App WikiMobile App Wiki
WikiApp DiscoverDiscuss

Wiki

    mobileapp.wiki

    Wiki

    • ASO17
    • Monetization14
    • Store Policies20
    • Metrics15
    • Development25
    • Marketing15
    • Legal9
    • UI/UX14
    • Testing10
    • Infrastructure10

    mobileapp.wiki

    Home/Store Policies/Most Common App Rejections and How to Avoid Them
    Store Policies4 min read

    Most Common App Rejections and How to Avoid Them

    Learn the top reasons apps get rejected by Apple and Google, with practical fixes for each rejection type to save time on your next submission.

    Most Common App Rejections and How to Avoid Them

    Table of Contents

    Why Apps Get RejectedApple App Store: Top Rejection Reasons1. Guideline 2.1 - App Completeness (Most Common)2. Guideline 2.3 - Accurate Metadata3. Guideline 4.0 - Design (Minimum Functionality)4. Guideline 5.1.1 - Data Collection and Privacy5. Guideline 3.1.1 - In-App Purchase RequirementGoogle Play: Top Rejection Reasons1. Policy Violation - Misleading Claims2. Data Safety Declaration Issues3. Closed Testing Requirement4. Target API Level5. Permissions PolicyUniversal Rejection Reasons (Both Platforms)How to Minimize RejectionsRelated Topics

    Why Apps Get Rejected

    Both Apple and Google reject apps that violate their guidelines, but the specific rejection reasons differ between platforms. Knowing the most common pitfalls before you submit saves days or even weeks of back-and-forth with review teams.

    Here are the rejection categories ranked by frequency, along with how to fix each one.

    Apple App Store: Top Rejection Reasons

    1. Guideline 2.1 - App Completeness (Most Common)

    Your app feels unfinished to the reviewer:

    • Placeholder content, lorem ipsum text, or test data visible
    • Features mentioned in the description that do not work
    • Broken links or empty screens
    • Beta or debug labels still showing

    Fix: Test every screen and feature path before submission. Use a physical device, not just a simulator.

    2. Guideline 2.3 - Accurate Metadata

    Your store listing does not match the actual app:

    • Screenshots show features that are not in the app
    • Description promises functionality that does not exist
    • App name is misleading or uses irrelevant keywords

    Fix: Take fresh screenshots from the current build. Write descriptions that match exactly what the app does today.

    3. Guideline 4.0 - Design (Minimum Functionality)

    The app does not provide enough value:

    • Simple website wrappers (WebView-only apps)
    • Apps that replicate built-in iOS functionality without adding anything
    • Template apps with no meaningful customization

    Fix: Ensure your app offers a native experience with features that justify being a standalone application.

    4. Guideline 5.1.1 - Data Collection and Privacy

    Privacy violations:

    • No privacy policy provided
    • Collecting data without disclosure
    • Not implementing App Tracking Transparency when required
    • Missing privacy manifest entries

    Fix: Add a comprehensive privacy policy. Declare all data collection in your privacy labels. Include ATT prompts where needed.

    5. Guideline 3.1.1 - In-App Purchase Requirement

    Trying to bypass Apple's payment system:

    • Linking to external payment methods for digital content
    • Accepting payments through your own payment system for subscriptions
    • Directing users to your website to avoid the 30% commission

    Fix: Use StoreKit for all digital goods and subscriptions. Physical goods and services can use external payment methods.

    Google Play: Top Rejection Reasons

    1. Policy Violation - Misleading Claims

    Apps that overstate their capabilities or contain deceptive elements:

    • Claiming the app can do things it cannot
    • Fake system notifications as engagement tactics
    • Misleading install counts or social proof

    2. Data Safety Declaration Issues

    Mismatches between what your app actually does and what you declared:

    • Declaring "no data collected" while using analytics SDKs
    • Not disclosing third-party SDK data practices
    • Missing data deletion mechanism

    3. Closed Testing Requirement

    Since 2023, Google requires new personal developer accounts to complete closed testing (12 testers, 14 consecutive days) before publishing to production.

    4. Target API Level

    Submitting with an outdated target SDK version. As of 2026, API level 36 is required for new apps.

    5. Permissions Policy

    Requesting permissions without clear justification:

    • Requesting SMS or call log access without core functionality need
    • Using ACCESS_FINE_LOCATION when coarse location would suffice
    • Not providing a prominent disclosure for sensitive permissions

    Universal Rejection Reasons (Both Platforms)

    • Crash on launch - The app does not even start
    • Login wall without demo - Reviewer cannot access the app without an account, and no demo credentials provided
    • Intellectual property violation - Using trademarked names, logos, or copyrighted content
    • Broken third-party integrations - API keys expired, servers down during review

    How to Minimize Rejections

    1. Read the full guidelines for both platforms at least once a year
    2. Create a pre-submission checklist specific to your app
    3. Always include reviewer notes with demo credentials
    4. Test your app in airplane mode and on slow networks
    5. Have someone unfamiliar with the project try the app before submitting
    6. Check rejection forums and communities for recent trends

    Related Topics

    • Apple App Review Guidelines
    • App Rejection Appeal Process
    • App Launch Checklist

    How did you find this content?

    Share

    ← Previous

    Apple App Review Guidelines: What Every Developer Needs to Know

    Next →

    Google Play Developer Policy: The Complete 2026 Guide

    Related Content

    Apple App Review Guidelines: What Every Developer Needs to Know

    A complete breakdown of Apple App Review Guidelines covering safety, performance, design, legal, and business rules for App Store approval.

    Google Play Developer Policy: The Complete 2026 Guide

    Everything you need to know about Google Play Developer Program Policies, from content rules to billing compliance and enforcement actions.

    iOS Privacy Labels: A Complete Guide to App Privacy Nutrition Labels

    How to accurately fill out Apple privacy nutrition labels for your iOS app, covering data types, collection purposes, and common mistakes.

    App Tracking Transparency (ATT): The Definitive Guide for 2026

    Everything about Apple App Tracking Transparency framework, from implementation to opt-in strategies and its impact on mobile advertising.

    Content Ratings and IARC: Age Rating Your App Correctly

    How the IARC age rating system works for mobile apps, including questionnaire completion and what each content rating level means.