Platform GuidesNovember 18, 2026

App Store Rejection Reasons: The 12 Most Common and How to Avoid Them

The most common App Store and Google Play rejection reasons, from crashes and privacy to payments and metadata, and how to avoid each one.

App Store Rejection Reasons: The 12 Most Common and How to Avoid Them
Quick answer

The most common App Store rejection reasons are crashes and bugs, incomplete information such as missing demo accounts, privacy issues with data collection or permissions, using non-Apple payment for digital goods, misleading metadata or screenshots, copycat or spam apps, and apps with too little functionality. Google Play rejections often involve policy declarations, permissions, data safety, deceptive behaviour and metadata. Most are avoidable with a pre-submission checklist.

Platform Guides app store rejection reasonswhy was my app rejectedApp Store rejectionGoogle Play app rejected

Common rejection reasons and fixes

ReasonTypical causeHow to avoid
Crashes and bugsUntested devices or OS versionsTest release builds on real devices
Incomplete informationNo demo account or unclear featuresProvide review notes and test credentials
Privacy and dataMissing privacy policy or unexplained permissionsAccurate privacy labels, policy and purpose strings
PaymentsExternal payment for digital goodsUse store billing where required
Misleading metadataScreenshots or claims not matching the appShow real app experience
Spam or copycatTemplate apps or duplicatesUnique value and one app per concept
Minimum functionalityThin wrappers around websitesNative features and real utility

Verdict: Most rejections come from preparation gaps rather than the app itself; a checklist prevents them.

Why apps get rejected

Stores review apps to protect users from crashes, privacy abuse, scams and low-quality content. Rejections usually cite a specific guideline or policy and explain what to fix.

See App Store review guidelines explained for the structure of Apple's rules.

1. Crashes and bugs

Apps that crash or have obvious bugs during review are rejected. Test release builds on several devices and OS versions, including older ones, before every submission.

Use TestFlight beta testing and Google Play testing tracks to catch issues early.

2. Incomplete information

If reviewers cannot log in or find features, they reject the app. Provide demo accounts, explain hidden features in review notes and make sure backend services are live during review.

Clear notes also shorten App Store review time.

3. Privacy and data collection

Missing privacy policies, inaccurate privacy labels, unexplained permission requests and data collection without consent are frequent problems. Explain why each permission is needed in plain language.

See app privacy policy guide and privacy labels and data safety.

4. Payments for digital goods

Selling digital content or features used in the app generally requires the store's in-app purchase system, with some regional and category exceptions. Physical goods and services use other payment methods.

Check the current rules for your markets before designing checkout.

5. Misleading metadata

Screenshots, descriptions or names that misrepresent the app, include irrelevant keywords or mention other platforms can cause rejection. Show the real app and make claims you can support.

See white hat vs black hat ASO.

6. Spam and copycat apps

Apple rejects apps that duplicate existing apps or are built from templates without unique value. Publishing many similar apps can also cause trouble on both stores.

Focus on one strong app per concept with clear differentiation.

7. Minimum functionality

Apps that are simply websites in a wrapper, or offer too little to be useful, may be rejected. Add native features, offline support or real utility beyond a mobile website.

Think about what the app does better than the web.

8. Sign in and account requirements

Apple requires apps that offer certain third-party sign-in options to also provide privacy-friendly alternatives such as Sign in with Apple in many cases, and apps with account creation must let users delete accounts in the app.

Check current account and sign-in rules before launch.

9. Content and age ratings

User-generated content needs moderation, reporting and blocking tools. Age ratings and content ratings must reflect the actual content.

See age rating and content ratings.

10. Google Play policy declarations

Google Play rejects or restricts apps with missing or inaccurate declarations for data safety, permissions, target audience, ads and financial features.

See the Google Play Console guide for where these live.

11. Intellectual property

Using trademarks, brand names, characters or content you do not have rights to leads to rejection or removal. Keep proof of rights for any licensed content.

Avoid competitor brand names in metadata.

12. Legal and regulated categories

Gambling, finance, health, VPN and other regulated apps may need licences, specific disclosures or organization accounts. Requirements vary by country.

Prepare documentation before submitting.

What to do after a rejection

Read the message carefully, fix the issue, reply in the resolution centre with a clear explanation and resubmit. If you believe the reviewer made a mistake, explain politely or appeal.

See app rejection recovery guide.

Key takeaways

Most rejections come from crashes, missing information, privacy gaps, payment rules, misleading metadata, spam and thin functionality. A pre-submission checklist catches nearly all of them.

Read the guidelines for your category, provide clear review notes and test thoroughly to launch on schedule.

Worked example: avoiding a login rejection

A fitness app requires an account. Its first submission is rejected because the reviewer cannot log in. For the next release, the team adds a demo account with sample data, writes steps to reach premium features and confirms the server is live during review hours.

The resubmission is approved quickly. The team adds review notes to its release checklist so future submissions do not repeat the problem.

Google Play review differences

Google Play reviews combine automated checks and human review, with policy enforcement that can also happen after publishing. Keep declarations accurate after launch, because changes in the app can make old answers wrong.

See the Google Play closed testing requirement for rules that affect new personal accounts.

Pre-submission checklist

Before submitting, test release builds, add review notes and demo access, check privacy policy and labels, confirm payment rules, review screenshots and metadata for accuracy, and confirm age ratings and any required licences.

Store this checklist with your release process so every version goes through it, not just the first launch.

Rejections after updates

Rejections are not limited to first launches. Updates can be rejected when new features introduce privacy changes, new payment flows or content that needs moderation, or when guidelines changed since your last submission.

Re-read relevant guidelines before major updates and plan buffer time in release schedules, especially before seasonal launches or marketing campaigns.

How to do it, step by step

  1. Test release buildsReal devices and OS versions.
  2. Prepare review notesDemo accounts and feature explanations.
  3. Check privacy and permissionsPolicy, labels and purpose strings.
  4. Review payments and metadataStore billing and honest listings.
  5. Check category rulesLicences and disclosures.

Before and after examples

Illustrative examples written for a generic app in this category, not client results. Swap in your own product, audience, and data.

Review notes
Before

Empty.

After

Demo login and steps to find key features.

Why it works: Reviewers can test.

Permission
Before

Location requested at launch with no reason.

After

Requested when needed with a clear explanation.

Why it works: Privacy compliant.

Screenshots
Before

Mockups of features not yet built.

After

Real app screens.

Why it works: Accurate metadata.

Action plan

  1. Test thoroughly
  2. Write review notes
  3. Be transparent on privacy
  4. Follow payment rules
  5. Keep metadata honest
  6. Respect IP

Metrics to monitor

  • First-submission approval rate
  • Time to approval
  • Rejections by reason
  • Resubmission count
  • Policy warnings

Record the baseline, release date, audience, markets, and external changes before interpreting movement. Rankings and conversion are useful signals, but a decision is stronger when activation, retention, and business value confirm that the page attracted the right users.

Frequently asked questions

What is the most common App Store rejection reason?

Crashes, bugs and incomplete information are among the most common.

How do I fix an App Store rejection?

Fix the cited issue, explain the change in the resolution centre and resubmit.

Can I appeal an App Store rejection?

Yes, if you believe the decision is wrong you can appeal through Apple's process.

Why do Google Play apps get rejected?

Often for policy declarations, permissions, data safety, deceptive behaviour or metadata.

Will a rejection hurt my app ranking?

A rejection itself does not affect ranking, but delays can affect launch timing.

How long does review take after resubmission?

Often similar to the first review; clear notes help.

Keep reading

More in Platform Guides

Browse all 17 Platform Guides guides

Work with ASOWin

Share

Turn your next ASO decision into measurable growth

Get a focused audit of visibility, conversion, ratings, and market opportunities.