Rejected by App Review. Now what?
A rejection is a decision with a stated reason, and that reason maps to a guideline. Most teams lose days re-submitting variations instead of reading the decision correctly once. Start with the free triage below, then buy the full diagnosis if you want it settled.
Diagnosis
US$99
Delivery target
Within 24 hours
Optional implementation
US$399+
Want me to make the changes too? Implementation starts at US$399 and is quoted against the plan you already have.
What you get
- Interpretation of the rejection message and the guideline it maps to.
- The probable underlying cause — not the surface symptom.
- A correction plan in priority order, with what changes in code, metadata or configuration.
- A drafted reply to App Review you can send as-is or edit.
- One follow-up clarification after you submit, at no extra cost.
Who this is for
Teams with a rejected iOS submission, update, TestFlight build, or in-app purchase review.
What this covers
- Payments, in-app purchase and subscription rejections
- Privacy, permissions, purpose strings and tracking
- Reviewer sign-in, demo accounts and gated content
- Metadata, screenshots and description mismatches
- App completeness, crashes and technical failures
- Minimum functionality and spam flags
What I need from you to start
- The complete rejection message from App Store Connect, including the guideline reference.
- Whether this is a new app, an update, a TestFlight build, or an IAP/subscription review.
- What changed since the last accepted submission, if anything.
Scope and limits
- Approval is decided solely by Apple and is never guaranteed.
- The 24-hour window starts when I have the full rejection message and your submission context.
- Implementing the corrections in your codebase is separate work, quoted against the plan.
Free · No sign-up
Free App Review triage
Paste the rejection message Apple sent you. You get a probable category, a likely resolution path, three prioritised actions and a drafted reply — immediately, with nothing to fill in.
Runs entirely in your browser. The text you paste is never sent, stored or logged — there is no request to transmit it.
⚠ Do not paste credentials, API keys, access tokens, personal data or proprietary source code. Paste the rejection message only.
Triage result
Paste the full message, including the guideline reference (for example: Guideline 2.1 - Performance - App Completeness)…
How it works
From blocked to a decision you can act on
No discovery calls to sell you a retainer. You send evidence, you get a written answer.
- 01
You send the evidence
The rejection message, the crash report, the failing build — whatever you already have. No forms, no lead-nurturing sequence.
- 02
I diagnose within the stated window
I work from your artefacts and, when access is granted, your code and App Store Connect record. The window starts when the evidence is complete.
- 03
You get a written plan
Probable cause, the correction plan in priority order, and — for App Review cases — a drafted reply you can send as-is or edit.
- 04
Implementation only if you want it
If you want me to make the changes, that is quoted separately against the plan you already have. Never a surprise on the invoice.
Still blocked?
Start with the free triage above, or go straight to the service that matches your problem. If you are not sure which one, write to me and describe the block in two lines.