App Store review checklist: prepare your evidence

1. Preserve the submitted metadata

Record the app name, subtitle, description, keywords, category, storefronts, support and privacy links, release notes, version and build. Use the material from the submission under review so that your investigation does not accidentally mix different versions.

Check that the store listing describes what the build actually provides. A screenshot from a future design and an interface present in the current build are different kinds of material.

2. Map the relevant pages and flows

Collect real screenshots and name the screens. Add navigation paths and the account state for each one. Include login, settings, paid features or account deletion where those flows apply to the case.

Keep review-message screenshots separate from in-app screenshots. For behavior that cannot be established with a static image, prepare a verification task or a recording rather than claiming that the screenshot proves success.

3. Record review history and reproducible behavior

Keep the complete current rejection or question, earlier rounds and your responses. Add relevant logs and reproduction steps with their date, build and environment. Distinguish your own test observations from statements reported by Apple.

Write down the exact changes you have made and which ones have been verified in the next build. If you have only planned a fix, leave it as planned work.

4. Explain related apps when the review raises overlap

When a review asks about similar apps or cites a spam concern, collect relevant apps from your portfolio and explain their actual purpose, audience, content and workflows. Use concrete, supported differences.

A shared layout alone does not establish a violation. A new color scheme alone also does not demonstrate a distinct product. Read the particular feedback and the applicable current guideline before deciding what evidence or product work is needed.

5. Prepare three outputs

• Issue report: the concern, applicable reference, evidence, verification steps and unknown facts.
• Modification tasks: what to change, why it addresses the concern and how to verify the result.
• Resubmission material: an English reply, Review Notes, an executable walkthrough and a list of demonstration assets to capture.

Check every output against the actual submission. Keep statements about completed fixes conditional until you have verified them.

6. Keep the evidence private and the references current

Use synthetic data in demonstrations where possible. Remove production customer information and passwords from screenshots and logs. Never publish a private app dossier as an SEO page.

The Apps Launch workspace stores drafts in your current browser. When you explicitly run AI analysis, selected text and resized images are sent to Cloudflare Workers AI. Export a backup before clearing browser data or switching devices.

Consult Apple’s current App Review Guidelines and Apple’s App Review guidance before acting on a policy interpretation. This checklist organizes evidence; it does not run your app or certify compliance.