Skip to content
TAA

App Store rejection

Apple rejected your app. Here is how it gets back into review.

I read what App Review flagged, check the app against the guideline it cites, fix it and prepare the resubmission with a clear note to App Review. Nobody but Apple can promise approval. If the app is a website in a wrapper, I tell you honestly what it needs.

A guideline number, a short note and a launch date that slips. A rejection is frustrating, but it is rarely the end: most of the time it names exactly what Apple wants to see changed.

What I do with a rejection

Four steps, in this order:

  1. Read the rejection, including any screenshots and follow-up messages from App Review in App Store Connect.
  2. Check the app against the guideline it cites, and against the related rules that are likely to come up next time.
  3. Fix the app, or the store listing, whichever the problem sits in.
  4. Prepare the resubmission with a clear note to App Review that explains what changed and, where needed, a demo login.

Nobody but Apple can promise approval. What you get from me is a fix that addresses what was flagged, and a straight answer if more is needed.

Common reasons for a rejection

Most rejections fall into a handful of groups:

  • Incomplete app or information (guidelines 2.1 and 2.3): placeholder content, links that do not work, or a description, screenshots or settings in App Store Connect do not match what the app does.
  • Crashes and bugs: the app fails on the device the reviewer uses.
  • No demo access: the reviewer cannot get past the sign-in and therefore cannot test the app.
  • Privacy details: a missing privacy policy, data use information that does not match the app, or no way to delete an account.
  • In-app purchases: digital content or subscriptions sold outside Apple's purchase system where Apple's rules require it.
  • Minimum functionality (guideline 4.2): the app offers too little beyond a website.
  • Spam (guideline 4.3): several near-identical apps from one account, or an app that looks like many already in the store.

The wording of every rule is in Apple's App Review Guidelines, last updated by Apple on June 8, 2026.

When the app is a wrapped website

Then I tell you honestly. Guideline 4.2 expects an app to be more than a website in a frame, and guideline 4.2.6 covers apps created from templates or app generation services. Resubmitting the same thing rarely helps. The realistic options are:

  • add what makes it a real app for your users, for example offline use, notifications or device features that matter to them
  • rebuild it as a real app, with the website as the blueprint: a First Version (MVP) from $27,800
  • stay on the web, if an app adds nothing your customers need

If your app was built with an AI tool, the page on taking an AI prototype to production covers the other gaps such apps tend to have.

Why I know App Review

I run my own apps in the App Store and deal with App Review for them myself, from the first submission to every update. You can download them and judge them yourself: see my apps in the App Store.

If you think App Review got it wrong

Reply first, appeal second. Apple's guidelines name two routes: questions and extra information go to App Review as a reply in App Store Connect, and if you disagree with the outcome you can submit an appeal. For an app that is already live, Apple says bug fix updates are not held back over guideline issues, except those about legal or safety matters; you ask for this in App Store Connect and fix the issue in the next submission.

Google Play too

A rejection or policy notice from Google Play is handled the same way: read it, check the app against the cited policy, fix it and prepare the update. The decision there lies with Google. If Play Console refuses an update because of its Android target, see the Google Play target API level deadlines.

What it costs

You can start in two ways:

  • With the App Check at $2,000, if you also want to know who controls which account and what else could block the next update.
  • With a free call, if the rejection is the only open question.

The fix itself runs at a fixed price, agreed in writing before work starts: as part of an App Takeover from $10,500 or an App Rescue from $27,800, depending on how much has to change. All prices are net; the tax treatment is clarified before contract and stated in the offer.

The code sits in your repository from day one; with each paid milestone, the rights to everything delivered up to that point pass to you.

Confidential from the first call: we are happy to sign an NDA before we talk.

Professional liability insurance in place, proof on request.

Common questions

Can you guarantee that Apple approves the app?

No. Nobody but Apple can promise approval. What I can do is fix what the rejection names, check the rest of the app against the same guideline and send the resubmission with a clear explanation of what changed.

How quickly can the app be resubmitted?

That depends on what was flagged. A missing demo login or a wrong privacy detail can be fixed quickly; a missing core function takes longer. After looking at the rejection I give you a plan with a date for the resubmission. How long the review then takes is up to Apple.

Do you need access to our App Store Connect account?

Yes, as an invited team member with a role that fits the work. The account holder role stays with your company, and you can remove my access at any time.

Our app is a website in a wrapper, or it was built with an AI tool. Is that a problem?

Not automatically, but Apple expects an app to offer more than a website. If yours does not yet, I tell you honestly what it would take, and whether a real app is worth it for your case.

What does guideline 4.3 (spam) mean?

Guideline 4.3 covers two cases: several near-identical apps under different bundle IDs, and an app that cannot be told apart from what is already widely available, for example one built from the same template as many others. Resubmitting unchanged rarely helps; the app needs something of its own, or the variants have to become one app.

What does guideline 2.1 (app completeness) mean?

Apple wants a final, working version: no placeholder content, links that work, no crashes, and a demo account if the app has a sign-in, with the back end switched on. A built-in demo mode instead of an account needs Apple's approval in advance. Many 2.1 rejections are fixed with a working demo login and a clear note to App Review.

Can I appeal an App Store rejection?

Yes. If you have questions or more information, reply to App Review in App Store Connect. If you disagree with the outcome, Apple's guidelines point to an appeal through its contact form. An appeal makes sense when the app really does meet the guideline; otherwise fixing it is faster.

Google Play rejected our app or sent a policy notice. Do you handle that too?

Yes, the same way: read the notice, check the app against the policy it cites, fix it and prepare the update. The decision there lies with Google.

Send me the rejection.

30 minutes, free: you share the message from App Review; you leave knowing what it means, what has to change and whether the fix is small or a bigger step.

Free 30-minute call, no obligation

You talk to Marcel directly, the architect who is accountable for the work. No sales rep, no pitch.

The calendar is served by Cal.com. It loads only after you click (data goes to Cal.com, US). Privacy policy

Prefer to write first? Describe your situation, with a link to your app, repository or questionnaire. You get an answer within one business day.