The two grounds Apple accepts
Apple approves an expedited app review under two specific circumstances: fixing a critical bug or hitting an unmovable calendar event. Regular marketing deadlines, missed internal schedules, or a general desire to launch quickly do not qualify.
A critical bug means an issue that breaks core functionality for existing users. Examples include immediate crashes on launch, data corruption during database migration, or broken in-app purchases. When my app shipped a regression that broke login for every returning user, I submitted under Critical Bug Fix and received approval within three hours. Minor cosmetic bugs or layout discrepancies limited to a specific screen size do not qualify.
A time-sensitive event requires hard evidence of an external deadline. Acceptable events include live conferences, sports tournaments, festival schedules, or coordinated media appearances. You must provide a publicly accessible website proving the date and explaining how the app integrates with that gathering. Internal promotional dates that you set yourself do not count as external events.
Reviewers verify claims against real telemetry and production data. If you claim that version 1.4 crashes for all users, but crash logs or store ratings show normal operation, your request will be rejected immediately. Clear, honest evidence is the only basis for approval.
Steps to take before submitting the form
You must submit your binary and metadata in App Store Connect before opening the request form. The app version status must display Waiting for Review. You cannot expedite a build that is still processing, in validation, or sitting in draft status. Submitting the request form while the build is processing leads to an automated denial.
Confirm all metadata and credentials inside App Store Connect. If your app requires an account, provide a working test login in the App Review Notes. If a reviewer opens the build under an expedited window and cannot log in, they reject it immediately, consuming your opportunity. Verify that two-factor authentication is disabled on the test account so that the reviewer can enter the app without friction.
Document the reproduction path for the bug on physical hardware. The review team needs to confirm that the reported crash occurred in the live version and that the replacement build resolves it cleanly. Keep a written list of exact steps ready so that you can supply them in both the review notes and the expedited request form.
Double check that your release setting matches your rollout plan. If your request is approved and the app passes review, it will release automatically if you selected manual release. Choose manual release if you need to coordinate the update with a server migration.
Exact text to write in the request
Navigate to the Contact the App Review Team page on Apple Developer and select Request an Expedited App Review. Provide your app name, App Store ID, platform, and contact phone number including your country code.
State the issue directly without introductory apologies or pleasantries. Write in English. Submitting in other languages adds translation handoffs that delay assignment to an available specialist. Give the reviewer the exact reproduction steps and the version affected.
For a critical crash, use this structure:
This update resolves a critical crash on launch affecting version 2.1.0. The crash occurs when users upgrade from version 2.0.0 due to an unhandled schema change in Core Data. Steps to reproduce in 2.1.0: Launch app on iOS 18, app terminates immediately. Steps to verify in 2.1.1: Launch app, database migrations complete without interruption. We verified the fix on physical devices.
For a time-sensitive event, use this structure:
This app supports attendees at the Independent Creators Meetup scheduled for October 12, 2026. The app handles session check-ins and venue maps. Event schedule and venue details are published at https://example.com/meetup2026. We request an expedited review to ensure attendees can install the build before registrations open on October 11.
What happens after submission
Apple typically responds by email within two to twelve hours. If approved, the status in App Store Connect changes from Waiting for Review directly to In Review shortly after the confirmation email arrives.
If the reviewer rejects the expedited build for an unrelated guideline issue, do not cancel the submission. Fix the issue, upload a new build under the same version, and reply directly inside the Resolution Center. State that this build addresses the rejection issued during an approved expedited review. The assigned team re-evaluates the build without returning you to the back of the queue. If you cancel and start a new submission, you lose your expedited status entirely.
If Apple denies the expedition request, accept the outcome. Denials state that the submission will proceed through standard review. Replying to argue the decision will not reopen the expedite request and may delay ordinary processing. Standard reviews typically finish within 24 to 48 hours, so you will still receive feedback relatively soon.
The cost of abusing expedited reviews
Apple does not publish a numeric limit on annual expedite requests. However, requesting priority treatment for regular version updates leads to automatic denials on subsequent attempts.
I once saw a studio request expedited reviews for three routine feature releases in a single quarter. Their fourth request, sent during a genuine billing failure, was rejected within minutes with a canned notice stating that expedited reviews are reserved for extreme emergencies. Treat this process as an emergency reserve rather than a regular deployment step.
To minimize critical emergencies, use Phased Release for automatic app updates. Phased release rolls out an update over a seven-day period starting with one percent of your active user base on day one. If a critical regression appears, you can pause the phased rollout in App Store Connect before the broken build spreads to your entire audience.
Check that your build has entered the Waiting for Review state, ensure your reviewer credentials work, and send the expedited review request only when your users face real harm.