ClearedToShip
Scan with GitHub

Run a free ShipCheck before you resubmit. Paste a public GitHub link or upload a zip. ShipCheck names each issue with the guideline, a short label, how serious it is, and how many places. It checks things like in-app account deletion (5.1.1(v)), the privacy manifest (5.1.2), In-App Purchase (3.1.1), Sign in with Apple (4.8), and broken or placeholder links (2.1). No account needed. A fix is $9, or 3 for $19, paid first. Run a free ShipCheck

It can't see your App Store Connect answers or screenshots, so it won't speed up the queue. It helps the build pass once a reviewer opens it.

App stuck in "Waiting for Review": what to do

If your build has sat in Waiting for Review for a week or more, you're not alone. A lot of indie devs posted about long queues this week, including first apps, updates and public TestFlight builds.

What the status means

  • Waiting for Review: your submission is in the queue. Nobody has opened it yet.
  • In Review: a reviewer has it. This part is usually short compared to the wait.
  • Pending Developer Release / Ready for Distribution: approved.
  • Rejected or Metadata Rejected: you'll get a message in App Store Connect explaining which guideline was cited.

Public TestFlight links also need Beta App Review, so external testing can sit in a queue too.

What you can do while you wait

  1. Check the submission is complete. Fill in the App Review Information section: contact details, a working demo account if the app has a login, and notes that explain anything a reviewer might not find on their own. Missing demo logins are a common reason a build bounces once it's finally opened.
  2. Request an expedited review if you have a real reason. Apple's contact form has an expedite option for things like a critical bug fix or a time-sensitive event. Give a specific reason. Apple can say no. https://developer.apple.com/contact/app-store/?topic=expedite
  3. Contact Apple if it's been unusually long. If there's no movement for weeks, open a case through App Store Connect's Contact Us page and include your app's Apple ID and the submission date.
  4. Use the time to test a fresh install. Reviewers start from a clean install with no data. Test on a real device, and on iPad if your app runs there, with an empty account.

What usually makes it worse

  • Pulling the build and resubmitting. Removing a submission to "bump" it generally doesn't help and can put you back in line.
  • Bundling extra changes into a resubmission after an info request. If Apple asked a question, answer it. New changes give the reviewer more to look at.
  • Submitting with no review notes. If a feature needs setup, a login or hardware, say so.

FAQ

Is a long wait a sign I'll be rejected? No. Waiting time and outcome aren't linked in anything Apple publishes.

Does an expedited request reset my place? Apple doesn't document that it does. It's a separate request on the same submission.

My TestFlight external build is stuck too. Same thing? Yes, external TestFlight builds go through Beta App Review. Internal testers don't need it.