Skip to content
AppDues
Log in
Contact salesSign up

App Store Review Preparation: A Practical Checklist

App Store review is a gate, not a formality. Most rejections are avoidable, but not all of them are, and the process can feel opaque while you wait. This guide turns the review guidelines into a submission checklist, explains what reviewers need to test an app, and separates a genuine rejection from a review that has simply stalled.

Start with the review guidelines

Apple publishes the App Store Review Guidelines, a long document organised into five sections: Safety, Performance, Business, Design and Legal. A rejection will normally cite a specific section, so knowing the structure helps you locate the rule, fix the issue, or dispute it with a precise reference.

The guidelines also list a set of pre-submission duties that apply to almost every app:

  • Test for crashes and bugs.
  • Make all app information and metadata complete and accurate.
  • Keep contact information current so App Review can reach you.
  • Supply an active demo account and any hardware or resources needed to test the app, such as login credentials or a sample QR code.
  • Keep backend services live and reachable during review.
  • Explain non-obvious features and in-app purchases in the App Review notes, with supporting documentation where useful.

These look obvious on paper. In practice they are where most avoidable rejections originate, so treat each one as a checklist item with an owner and an artifact.

Test the release build for crashes and bugs

Crash rejections are among the least subjective, and among the hardest to fix, because you are debugging a release build rather than your development build. Use TestFlight across as many devices and OS versions as you can. A TestFlight install is the closest experience to the App Store build, so a build that survives TestFlight is unlikely to crash for a reviewer. Submit in-app purchases for review together with the app submission rather than leaving them for later.

Complete and accurate metadata

Metadata is a frequent source of rejections, partly because it is usually the last task before submission and gets rushed. Check that the title, subtitle, description, tags and "what's new" text are filled in, accurate, and free of guideline violations. Fastlane's precheck action can scan metadata and in-app purchases for warning signs such as swear words, placeholder text, unreachable URLs, references to other platforms, or mentions of Apple product bugs.

A useful habit is to draft metadata early and revise it as the app evolves, so the final submission step is a review rather than a writing sprint.

Keep contact details current

A standard rejection arrives by email to your Apple ID and as an App Store Connect notification. Occasionally App Review will phone instead. Make sure the contact information on the account is current so a call reaches someone who can answer questions about the build.

Provide a usable demo account

If the app requires login, create a reviewer account that is already populated with realistic data. A reviewer testing many apps should not have to build a fresh account from scratch for each one. A well-prepared demo account shortens the review and reduces the chance of a rejection based on an untested path.

Explain non-obvious features in the review notes

The App Review notes are where you close the gap between what the app does and what a first-time reviewer can infer. This matters most for unusual authentication, integrations, or purchase flows.

A concrete example from the supplied evidence: an app that used the App Store Connect API through iOS Shortcuts could not be reviewed with a username and password, because that API uses public/private key authentication. The developer created a dedicated API key for reviewers and attached it in a ZIP file. Rejections continued because the reviewer did not know where to find the key or how to use it inside the app. The fix was to add two demo videos to the same ZIP: one showing how to create and download the key, and one showing how to use it in the app. That ZIP was then attached to every subsequent update, including small ones, so any new reviewer had the same context.

The lesson generalises: assume the reviewer has never seen your product and has limited time. Attach the key, the credentials, the QR code, and a short walkthrough.

When review seems stuck

A build sitting in "Waiting for review" or "In review" gives no position in the queue and no lever to speed it up. In the supplied account, one app stayed in review for 35 days.

There are two distinct situations here, and they should not be confused:

  • A rejection is a decision. You receive a reason, you fix or dispute it, and you resubmit.
  • A stall is the absence of a decision. Nothing is wrong with the build; it simply has not been picked up yet.

For a stall, the documented route is to contact Apple through the Contact Us – Status form and ask for the status of the review. In the supplied account this did not shorten the wait, but it confirmed the request had not been lost. Cancelling and resubmitting has been reported by developers as sometimes moving a build along, but the mechanism is speculation, and the same account warns that repeated cancellation could draw attention to the account. It is not a recommended method.

Two ways to reduce uncertainty before submitting

Even with the guidelines read and the metadata checked, some uncertainty remains. Two techniques help.

Compare with similar apps. If comparable apps are already live, that is evidence the category can pass review. It is not a guarantee: rules change, and Apple sometimes stops approving certain kinds of app. Differentiation also matters, because the App Store rejects clones.

Try a stealth release. Ship a minimal version first to get feedback from App Review before investing further. This is not an official early-review service; it is a way to test the waters with a small build. Early user ratings can be reset through App Store Connect if the minimal version attracts reviews you do not want to keep.

Pre-submission checklist

Use this as a final pass before you press submit. Each row maps a guideline duty to the artifact that proves it.

Rejections are not fully avoidable

No checklist removes the possibility of rejection. What it does is shrink the avoidable share: test the release build, write metadata carefully, keep contact details current, give reviewers a working account and clear notes, and keep backend services available. When a build stalls, use the status contact form rather than repeated cancellation. When a rejection arrives, read the cited guideline section and respond to that specific point.

Pre-submission checklist
CheckArtifact to have ready
Release build testedTestFlight runs on multiple devices and OS versions
In-app purchases submittedPurchases included in the same submission
Metadata completeTitle, subtitle, description, tags and what's new reviewed
Metadata cleanprecheck run, or a manual scan for placeholders, bad URLs and platform references
Contact details currentApple ID contact information verified
Demo accessReviewer account with realistic data, plus any QR code or hardware notes
Backend liveServices reachable during the review window
Review notesExplanation of non-obvious features and purchases, with attachments
Similar apps checkedCategory precedent noted, differentiation clear
Stealth option consideredMinimal build plan if the category is uncertain

Frequently asked questions

How should I test an app before App Store review?

Use TestFlight on as many devices and OS versions as possible. A TestFlight build behaves much like the App Store build, so crashes are more likely to surface there than in a development build. Submit in-app purchases for review at the same time as the app.

What metadata does App Review check?

Title, subtitle, description, tags and the "what's new" text all need to be complete and accurate, and none may violate Apple's guidelines. Fastlane's precheck action can flag swear words, placeholder text, unreachable URLs, references to other platforms and mentions of Apple product bugs.

Do I need a demo account for App Review?

If your app requires login, yes. Create an account pre-populated with realistic data so the reviewer can exercise the app without building an account from scratch. Include any other required resources, such as a sample QR code or hardware notes.

What can I do if my app is stuck in review?

Use Apple's Contact Us – Status form to ask for the status of the review. This does not usually shorten the wait, but it confirms the request has not been lost. Cancelling and resubmitting has been reported to sometimes move a build along, but the mechanism is speculation and repeated cancellation could draw attention to the account, so it is not the recommended route.

What is a stealth release?

A stealth release means submitting a minimal version of the app first to get feedback from App Review before investing further in the full product. It is not an official early-review service. If the minimal version attracts user ratings you do not want to keep, they can be reset through App Store Connect.