Store expedited review requests around festival launches: when they work

Festival launches collide with review queues. Apple’s App Review page states that on average, 90% of submissions are reviewed in less than 24 hours, and separately documents expedited reviews for extenuating circumstances: fixing a critical bug, or releasing an app to coincide with an event you are directly associated with. The request form is linked as Request an expedited review.

For event-related apps, Apple recommends planning and scheduling the release in App Store Connect, and says you may request expedite if the app is still in review and the event launch is quickly approaching. The request must include the event, the date of the event, and the app’s association with the event. Critical-bug expedites should include reproduction steps on the current live version.

When expedite is the wrong plan

“We want to ship for Black Friday / CNY because UA is booked” is not, on Apple’s page, a listed expedite category. Incomplete metadata, placeholder content and missing demo accounts remain common rejection causes on the same App Review page. Expedite does not replace a complete submission.

Operator implication

1. Submit festival binaries and metadata with buffer days, assuming the average path—not an approved expedite.
2. Use expedite only when you meet Apple’s bug or event-association criteria and can document them.
3. Treat Google Play review separately; this brief body-reads Apple’s App Review page only.

Download the evidence table.

Research checked 20 September 2026. Local draft; human editorial review pending. No CMS write performed.