When to expedite App Store review
Apple considers expedited review when the cost of waiting is immediate and concrete. Its two published examples are a critical bug in a live app and a release tied to a time-sensitive event the app is directly associated with. For a bug, explain what users can no longer do and how to reproduce it in the current live version. For an event, give its name, date and time zone, and explain what users will need the app for. Apple’s App Review guidance
If an urgent compliance issue is driving the request, describe the specific deadline and what the submitted build changes. Apple gives no separate eligibility rule for legal issues in its expedite guidance and provides a dedicated route for App Store intellectual property disputes. Apple’s expedited review guide · App Store support
How to expedite iOS app review
1. Prepare the submission. Test the exact build and include any demo credentials, setup steps, and urgent context under App Review Information. Check that your listing shows the app in use and reflects the features in the build. If your update changes the UI, use the App Store screenshot generator to prepare a matching screenshot set before submission. Apple’s App Review Guidelines
2. Submit the app for review. In App Store Connect, add your version for review, then open the draft submission and click Submit for Review. A version marked Ready for Review is still a draft. Apple can only expedite a submission it has received. Apple’s submission instructions
3. Send the expedite request. Sign in to Apple Developer, open the Request an Expedited App Review form, and select the app and platform. State the impact, identify the submitted version, and explain any hard deadline. Check App Store Connect and the email associated with your submission for updates. Apple’s expedited review instructions
What to write in an expedited review request
Put the reason for urgency in the first sentence, then give the reviewer enough detail to verify it. For a critical fix, include reproduction steps for the live version and describe what the submitted build changes. Put the same reproduction steps in App Review Notes so the reviewer has them when opening the submission.
For example, a team fixing a checkout crash could write, “We’re requesting expedited review of iOS version 2.4.1, build 186. In the live version 2.4.0, users crash when they tap Pay with a saved card. To reproduce, sign in with the demo account, add an item to the cart, and tap Pay using the saved card. Build 186 fixes the crash. Demo access and test steps are in App Review Notes.”
What to do while you wait for Apple
Track the app under Apps → your app → App Review. There are two decisions to watch for. Apple can agree to prioritize the submission, then separately decide whether the build passes review. If a reviewer asks for details, reply to that message in App Store Connect.
If you still need a status update, contact Apple with the app ID, version, build number, original request date, and any case number. Follow up through the existing case when possible. Keep the build in the queue unless you need to replace it or fix the submission. Removing it and submitting again starts a new review. App Review support · Apple’s resubmission guidance
For a routine submission, check how long App Store review takes and what to do if your build stays in Waiting for Review.





