The short version
App Store review times have become unpredictable: developers report apps and updates waiting three weeks or close to a month, even though Apple says the average is 1.5 days. Any team whose launch, client demo or hotfix depends on approval should build a review buffer into its iOS development and release plan instead of assuming a 48-hour turnaround.
What are developers reporting?
The Register, writing on October 22, pointed to a run of Apple Developer Forums threads with titles such as "Unusually long Apple 'waiting for review' time" and "Stuck in 'Waiting for Review' since October 8". One developer, D1 Tech, said it had been waiting since September 19. A Reddit post described a wait of almost a month. Many of the delayed builds were not new apps but bug fixes for apps that had already been approved.
Two days earlier, mobilegamer.biz collected similar accounts from game studios. One studio head said five of its apps had been waiting for review for over a week; another developer said reviews often take three to five days even when expedited, with feedback that is frequently vague. Third-party trackers such as Runway's review-times dashboard also show average times rising.
What does Apple say about review times?
Apple's published guidance still says App Review "typically" handles at least 50% of submissions in under 24 hours and 90% in under 48 hours. In a statement to mobilegamer.biz, Apple said its average review time is 1.5 days for all apps and 14 hours for minor updates, though some new apps take longer when they need additional scrutiny. It added that over the last 12 weeks its App Review team processed an average of 378,000 submissions a week, and that it continues "to evolve our review process to support that growth". The Register said Apple had not responded to its request for comment at publication.
Both things can be true at once. An average of 1.5 days hides a long tail, and the tail is where a launch slips. A median developer may see little change while a minority waits weeks, which is exactly the uncertainty that breaks release dates.
Why is the review queue backing up?
Apple has not named a cause, but the volume story is well documented. In April, The Information reported, and 9to5Mac relayed, an 84% year-over-year jump in new apps on the App Store as AI coding tools lowered the cost of shipping one. Business Insider had already flagged the surge of AI-coded apps in March. More low-effort submissions mean more apps that need closer inspection, and Apple has also tightened its rules: on October 16 it added guideline 2.5.19, which bans hidden or dormant features switched on after approval.
The timing adds pressure. iPhone Duo went on sale on October 23 with iOS 27.1, and Xcode 27.1 brought the SDKs and simulator for its foldable layout. Teams racing to ship Duo-optimized builds are joining the same queue as the flood of new submissions.
What it means for US & EU software teams
For companies that sell or depend on mobile apps, App Review has turned from an administrative step into a schedule risk. The exposure is largest in three places: launches tied to a marketing date or a client contract, hotfixes for production incidents, and regulated apps in FinTech or HealthTech where a security or compliance fix cannot wait three weeks.
Hotfix timing is the most serious gap. If a payment flow breaks or a data-handling bug surfaces, the fix cannot reach users until Apple approves it, and the expedited-review route is discretionary. That makes server-side mitigations, such as disabling a broken flow already in the reviewed build, more valuable, as long as they stay within what App Review has seen. Turning on new functionality after approval is exactly what guideline 2.5.19 now forbids.
EU teams have a partial alternative in alternative app marketplaces and web distribution under the Digital Markets Act, but those apps still go through Apple's notarization review, so they are not a clean bypass. Contracts with app development vendors should also stop promising fixed store-release dates and instead define delivery as "build submitted and passing pre-review checks".
How to plan iOS releases around slower review
- Add a review buffer. Plan one to two weeks between submission and any public launch or client commitment, and track actual review times per release.
- Decouple launch from approval. Submit early and use manual release, so an approved build waits for your date rather than your date waiting for approval.
- Get it right first time. Run a pre-submission checklist for metadata, privacy labels, demo credentials and review notes; every rejection restarts the wait.
- Keep a kill switch, not a feature switch. Build server-side ways to disable risky flows in the reviewed build, and do not use flags to enable unreviewed features.
- Reserve expedited review. Use it for genuine critical fixes so requests stay credible, and expect days rather than hours.
- Use TestFlight and phased release. Validate builds with external testers before submission and roll out risky updates gradually after approval.
Frequently asked questions
How long does App Store review take in October 2026?
Apple told mobilegamer.biz that its average review time is 1.5 days for all apps and 14 hours for minor updates, with some new apps taking longer when they need extra scrutiny. At the same time, developers on Apple's forums and Reddit report individual submissions stuck in Waiting for Review for three weeks or close to a month.
Why are App Store reviews slower?
Apple has not given a cause. It says its App Review team processed an average of 378,000 submissions a week over the last 12 weeks and that it continues to evolve the process to support that growth. Earlier in 2026, The Information reported an 84% year-over-year jump in new apps, which coverage links to the spread of AI coding tools.
Can I speed up an App Store review?
Apple lets developers request an expedited review for critical bug fixes or time-sensitive events, but it is granted case by case and developers report that expedited reviews can also take several days. The more reliable lever is planning: submit earlier, keep builds small and avoid needless resubmissions, because each new build starts its own wait.
Should we change our mobile release process because of the delays?
Yes, if a release date depends on approval. Add a review buffer of one to two weeks to launch plans, decouple marketing dates from submission, submit hotfix candidates early, use phased release for risky updates, and keep server-side configuration within what App Review has seen, since guideline 2.5.19 bans features switched on after approval.
Sources
The Register — Apple App Store review process hits a traffic jam (October 22, 2026)
mobilegamer.biz — App Store review times are being dragged down by a flood of AI-made apps and games (October 20, 2026)
9to5Mac — App Store sees 84% surge in new apps as AI coding tools take off (April 6, 2026)
Apple Developer — App Review