Talk to a person. We reply within one working day.

SEO and AI search
Web
AI
Resources
WorkAboutStart a project

App launch · 21 Nov 2026 · 7 min read

App store rejection: common reasons and how to respond

A rejection is a message from a reviewer about one specific problem. Most can be fixed and resubmitted once you read the message properly.

The short answer

App store rejection usually comes from a few causes: crashes or broken features, missing or unclear privacy information, a listing that does not match the app, login problems for reviewers, and policy conflicts. Read the exact guideline cited, fix or explain it, reply in the review thread, and resubmit. Appeal only when you believe the reviewer was wrong.

What an app store rejection actually is

An app store rejection means a reviewer at Apple or Google Play checked your submission against the store rules and found something that does not meet them. The app is not banned and your account is not in trouble. The build you submitted simply cannot go live yet.

The message names a rule, often with a section number, and usually describes what the reviewer saw. That message is the most useful document you will receive during launch. Founders who skim it and resubmit unchanged tend to be rejected again for the same reason.

Both stores publish their rules and keep them up to date. Apple calls its rules the App Review Guidelines, and Google Play has developer policies in the Play Console help pages. The wording and numbering change over time, so read the current version rather than a copy someone saved a year ago. If you are still planning the build, our mobile app development service covers how store requirements fit into the project from the start.

The common reasons apps get rejected

Reviewers see the same problems again and again. Grouped by what you can control, they look like this.

The app does not work during review

Crashes on launch, a screen that never loads, a button that does nothing, or a server that is switched off. Reviewers test on current devices and operating system versions, often on a network you did not test on. A backend that sleeps, expires its test data or blocks unknown regions will look like a broken app.

The reviewer cannot get past login

If your app needs an account, the reviewer needs working demo credentials and any steps for two-step checks. A one-time code sent to your own handset is a common cause of a stalled review. Put test details in the review notes field and check they work from a fresh install.

The listing does not match the app

Screenshots showing features that are not in the build, a description that promises something the app does not do, or a name stuffed with extra keywords all draw complaints. The listing is part of what is reviewed. Our guides on writing titles, subtitles and descriptions and on making screenshots and previews explain how to keep the listing honest.

Privacy information is missing or wrong

Both stores ask you to declare what data the app collects and why. If the declaration says one thing and the code does another, for example an analytics tool collecting more than you listed, you can be rejected. Apps that let people create an account are also expected to offer a way to delete it. Check the current documentation from each store for the exact wording.

Permission requests that make no sense

Asking for location, camera or contacts without a clear reason, or asking before the person has seen any value, can be flagged. The text shown in the permission prompt should explain the benefit in plain language.

Payments and content that break store rules

Digital goods and subscriptions have to go through the store's own purchase system in most cases, and the rules differ by store and by region. User-generated content usually needs a way to report and block abusive material. Apps that copy another product closely, or use another company's brand, can also be refused.

An unfinished or thin app

Placeholder text, empty screens, test labels and a single web page wrapped in an app shell are all signs of an unfinished product. Reviewers expect an app that does something useful on the device.

How to read the rejection message

Start with three things: the guideline or policy cited, the device and version the reviewer used if it is stated, and any screenshot or attached recording. Write down in one sentence what the reviewer says is wrong. If you cannot do that, the message is unclear, and the right first move is to ask a question rather than guess.

Check whether there is one issue or several. A message can list more than one guideline, and fixing one while ignoring another wastes a review cycle. Treat the message as a checklist and tick off each item with a note of what you changed.

Reproduce the problem yourself before changing anything. Use a clean install, the same operating system version if you can, and a network you do not usually use. If you cannot reproduce it, say so in your reply and attach what you did try. Sometimes the cause is a server setting, not the app code.

How to respond, resubmit or appeal

There are three routes, and they suit different situations.

  1. Fix and resubmit. Use this when the reviewer is right. Change the build or the listing, add a short note saying what changed, and submit again.
  2. Reply and ask. Use this when the message is unclear, or when you think the reviewer missed something that is already in the app. Reply in the review thread in the store's developer console, stay polite and factual, and point to the exact screen or setting.
  3. Appeal. Use this when you believe your app meets the rules and a reply did not settle it. Apple has a formal appeal route to its App Review Board, and its help pages say to reply to the message first and to point to the specific requirements involved. Google Play has its own appeal route for policy actions. Check the current documentation for how each one works today.

Appeals are slower than fixes and do not always succeed. If a small change would satisfy the rule, make the change. Save appeals for real disagreements about how a rule applies.

Tone matters because a person reads your reply. Keep it short, quote the guideline number, say what you did, and give the steps to see it. Skip arguments about how much work the app took or how many people want it.

A reply template you can adapt

A useful reply has four parts: what you understood, what you changed, where to look, and what the reviewer needs to test it. For example: "Thank you for the review. We understood the issue to be that the account screen could not be reached without a code. We have added a demo account in the review notes with no extra checks. Open the app, tap Sign in, and enter the details in the notes. We have also updated build 1.2.1 to fix the crash on the settings screen."

Notice what is missing: no complaint, no deadline pressure, no list of past approvals. A reviewer deals with many apps and appreciates a clear path to confirming the fix.

How to prepare so you are rejected less often

Most rejections are avoidable with a short routine before every submission.

  • Test the exact build you are uploading on a real device with a clean install, and use a simulator only as a second check.
  • Read the current store guidelines for each area your app touches: payments, accounts, user content, location, children, health or finance.
  • Make the privacy declarations match the code. List every analytics, advertising and crash tool the app includes.
  • Prepare review notes: demo login, how to reach hidden features, and any hardware the reviewer needs.
  • Keep the backend live and unrestricted for review dates.
  • Match the listing to the build. Remove screenshots of features that are not shipped.
  • Remove placeholder content and test labels.

Plan some slack in your launch timeline. Review times vary and a second round is common on a first submission, so avoid fixing a marketing date before the app is approved. Beta testing through the store's own testing tools can also surface problems before the formal review. If you are pairing the launch with a visibility push, read about app store optimisation basics and titles, keywords and ratings as well.

When the rejection comes after launch

Updates are reviewed too, and an update can be rejected even when the first version passed. Rules change, and a new version may use a permission, a payment method or a data tool the old one did not. Treat every update as a fresh submission with its own checks.

If you need old versions to keep working while you fix a rejected update, the way you handle version numbers and update prompts matters. We cover that in app versioning and update prompts.

Related guides

Questions and answers

Why do apps get rejected from the App Store or Google Play?

The common causes are crashes or broken features, a reviewer who cannot log in, a listing that does not match the app, missing privacy information, unclear permission requests, and payment or content rules. The rejection message names the rule that applies, so read it before you change anything.

How long does it take to fix a rejection?

It depends on the cause. A listing change can be quick, while a bug fix or a privacy change needs a new build and a new review. Review times vary, so check the current documentation and avoid fixing a public launch date before approval.

Should I appeal or just resubmit?

Resubmit when the reviewer is right or a small change would satisfy the rule. Reply in the review thread if the message is unclear. Appeal only when you believe the app meets the rules and a reply did not resolve it.

Can I be rejected for something that passed last time?

Yes. Rules change, and a new version may add features, permissions or data collection that the old one did not have. Each update is reviewed separately, so keep your checklist current.

What should I put in the review notes?

Give working demo login details, steps to reach any hidden or paid feature, and notes about hardware or regions the reviewer needs. Make sure the backend is switched on and that no one-time codes go to your own device.

Does a rejection hurt my developer account?

A single rejection for a fixable problem is a normal part of publishing. Repeated serious breaches of store policy are a different matter, so read the policies for your area and ask the store if you are unsure.

Tell us what you are building.

A short call, a written plan and a fixed quote. No obligation.

Get a free quote