Your kit
Start here. Five steps, in this order.
Step 1 does most of the work — an AI squad reads your app and tells you what would get it rejected. Everything after that is acting on what it found.
Run the audit squad on your app
Nine agents read your code, your configuration and your App Store Connect listing. You get a report where every finding cites a file and a line, App Review Notes pre-filled from what was found, and reply drafts for the rejections you’re most likely to get. It runs on your machine, in the AI tool you already code with.
No Mac or AI coding tool? Do the same pass by hand with the pre-submit self-audit.
Fix what it found
Each finding names the guideline and the page that covers it. Start with the blockers.
- Search Fix Library The fix behind every rejection reason, guideline by guideline — code side and App Store Connect side.
- Guide Find your app type AI, subscription, WebView, no-code, crypto, UGC — the traps specific to your kind of app.
- Prompts AI prompt packs Targeted audits to paste into your AI when you want to dig into one area yourself.
Set up App Store Connect
The part no agent can do for you: the fields, the products and the assets, filled in correctly.
- Checklist Subscription & in-app purchase setup checklist Every field and agreement you must complete for your subscription to load, clear 'Missing Metadata', and pass review — with the money plumbing that silently blocks products.
- Field guide App Store Connect field guide Every field of the App Store Connect submission form explained tab-by-tab: what it is, its spec/limit, the common mistake, and the rejection risk.
- Field guide Screenshot & app preview specs The exact pixel dimensions, formats, and counts Apple accepts for screenshots and app preview videos in 2026 — the required 6.9-inch iPhone and 13-inch iPad sets, and why video is not the same size as a screenshot.
Submit
One last linear pass, then the Review Notes that tell the reviewer how to get into your app.
- Checklist First submission checklist A sectioned, before-you-click-Submit checklist covering account, build, metadata, assets, privacy, login, IAP and release — each item cross-linked to the fiche that goes deeper.
- Templates Review Notes & templates Paste the notes the audit generated, or start from a blank one.
- Field guide What's New / release notes How to write the What's New field so it doesn't draw a 2.3 rejection — the 4,000-character limit, the gotcha that your first version can't have release notes at all, and copy-paste templates you can generate from your git log.
If Apple rejects you
Start from their exact message. Most rejections are answered, not re-built.
- Search Rejection Decoder Paste Apple’s message or the guideline number and get the fix that matches it.
- Templates Reply & appeal templates What to write in the Resolution Center — including when you think Apple got it wrong.
- Support Ask for a fix Stuck on something the kit doesn’t cover? Send the rejection over.
Reference
Not steps — look these up when a field, a status or a term is unclear.
- Field guide App Store Connect statuses & build errors, decoded Every App Store Connect status and build/upload error, decoded with Apple's official red/yellow/green color legend into one plain answer: what it means and what — if anything — you need to do about it.
- Explainer App Store Connect & App Review glossary Every confusing App Store Connect and App Review term — statuses, IAP, build/signing, metadata, privacy, distribution — defined in one line and linked to the page that goes deeper.
- Explainer TestFlight vs App Store Clears up the confusion between TestFlight testing and a real App Store submission, and the version-number gotcha that trips up first-timers.
- Field guide Required-reason API codes Every approved reason code for the five required-reason API categories, what each one actually permits, which APIs trigger which category, and the five ways developers pick the wrong code — so you can answer ITMS-91053 without guessing.
- Field guide App Store Connect API keys & roles Create an App Store Connect API key the right way — Key ID, Issuer ID, the .p8 you can only download once — and decode the 403 Forbidden that means your key's role is too weak.
- Field guide Locales & language codes The canonical App Store locale codes that trip up first-timers — why it's ar-SA not ar, de-DE not de, zh-Hans not zh — and the rule that every required field must be filled for each language you add.
- Self-audit Pre-submit self-audit Answer a few yes/no questions about your app and get routed to the exact checks, fiches and templates that de-risk your specific submission.