How Long Does App Review Take? Wait Times and Rejections
Most apps clear App Review in under a day. Here is how long each stage takes, what slows it down, why apps get rejected, and how to plan a release around the wait.
You press Submit for Review, and then you wait. For a bug fix, a day feels like a week. For a launch you have already announced, it feels longer. The good news is that App Review is faster and more predictable than its reputation.
This post covers what the wait looks like today, what each status in App Store Connect means, what makes a review take longer, and the short list of problems behind most rejections.
What happens after you submit
Every version moves through the same statuses in App Store Connect. Each one tells you where the time is going.
- Waiting for Review. The build is in the queue and nobody has opened it yet. This is most of the wait, about 11 hours on a typical day.
- In Review. A reviewer installs the app, uses it and checks the listing against the App Review Guidelines. This part is short, about 2 hours on a typical day.
- Pending Developer Release. Approved, and held for you to release. You see this only if you chose to release the version yourself.
- Ready for Distribution. Approved and on its way to the store. It can take up to a day for every storefront to show the new version.
- Rejected or Metadata Rejected. The reviewer found a problem. The message names the guideline and usually the screen. Metadata Rejected means the problem is in the listing alone.
What makes App Review take longer
Most versions land close to the typical time. Four things push a submission to the long end.
The day you submit
The queue changes through the week. In recent figures, a build submitted on a Wednesday waited the least, about 7 hours, and one submitted on a Monday waited the longest, about 14 hours. If the date matters, leave a day of room.
The holidays
Apple posts a holiday schedule on its developer news page each year, and reviews around Christmas take longer. If you want a version live for the holidays, submit it in early December.
A new iOS release
The weeks around a new iOS release in September are the busiest of the year, as developers ship updates for the new version at the same time. Expect a longer queue.
What the reviewer has to test
A sign-in the reviewer cannot get past, in-app purchases, or a feature behind a server switch all lead to questions. Each question is a round trip, and the wait starts again when you reply. Put what the reviewer needs in the App Review Information notes before you submit.
Why apps get rejected
About 22% of submissions are turned down the first time, by Apple's own count. Most rejections come from a few guidelines, and you can check each one before you submit.
2.1 App Completeness
Crashes, broken links, placeholder text and features that do not work. The most common cause is a reviewer who cannot sign in. Add a demo account to App Review Information, and check that it works on the build you sent.
2.3 Accurate Metadata
Your listing has to match the app. Screenshots show the app in use, the name and subtitle carry no prices or names of other apps, and keywords go in the keyword field. The free title and subtitle checker and keyword field optimizer help you write both inside the limits.
5.1.1 Data Collection and Storage
You need a working privacy policy link, a clear reason in every permission prompt, and a way to delete the account inside the app if people can create one there. Ask only for the data the app uses.
3.1.1 In-App Purchase
In most storefronts, an app that unlocks digital content or features sells it through Apple's in-app purchase. Submit every product in the build alongside it, and check that restore purchases works.
4.2 Minimum Functionality and 4.3 Spam
A thin wrapper around a website, or a near copy of an app already on the store, gets turned down. Show what your app does that a web page cannot, and make it clearly your own.
A checklist before you submit
- Test the exact build you upload on a real device, signed in and signed out.
- Add a working demo account, and any codes the reviewer needs, to App Review Information.
- Explain anything that is not obvious in the review notes: hardware it needs, a feature behind a setting, a storefront it is built for.
- Check that every screenshot shows the current app.
- Open the privacy policy link, and check the privacy labels match what the app collects.
- Submit every in-app purchase in the build with it.
- Choose how the version goes live: as soon as it is approved, on a date, or by hand.
If your app is rejected
Read the message first. It names the guideline and often the exact screen. If the reviewer misunderstood something, reply in App Store Connect with a short explanation or a screen recording. Many rejections clear with a reply and no new build.
If the status is Metadata Rejected, fix the text or screenshots and resubmit with the same build. If you still disagree after you reply, you can appeal to the App Review Board.
When a fix cannot wait, such as a crash in a live version or a launch tied to an event, ask for an expedited review through Apple's contact page. Apple decides each request on its merits, so keep it for real emergencies.
Plan your release around the wait
Treat App Review as a step in your schedule. Submit two or three days before you need a version live, and set it to release by hand. It clears review on Apple's clock and goes live on yours.
This matters for your listing as much as your code. A new title, subtitle, keyword field or set of screenshots goes live only with a new version, so every listing change waits for review too. Promotional text is the exception, and you can change it at any time.
So plan the words with the release. Next Release picks the keyword worth going after and writes the listing for it, so the version you submit carries the fix and a stronger listing together.
Know the minute your app moves
ASO Studio Connect follows every version from submitted to live on your iPhone and iPad. It sends a push the moment the status changes and shows where you stand against today's typical wait.
See ASO Studio Connect