TestFlight External Testing Waiting for Review: How Long?

TestFlight external testing shows Waiting for Review when the first build of a version is in Apple's Beta App Review queue, which normally takes a few hours to 48 hours. This is Beta App Review, a lighter check than the full App Store review, not the same thing. You cannot skip it for external testers, but there are two ways around the wait: internal testers, up to 100 people, skip review entirely and get the build in minutes, and after the first build of a version is approved, later builds of the same version often skip review.

Short answer

External testing needs Beta App Review, and it normally takes a few hours to 48 hours for the first build of a version. According to Apple's TestFlight page, only external testers require this review; internal testers do not. It is Beta App Review, not the full App Store review, so it is lighter, but Apple gives no guaranteed time. You cannot skip it for external testers, though internal testers get builds in minutes, and later builds of the same version often clear without a new full review. Resubmitting restarts the clock. Escalate only after you clearly pass 48 hours.

How long does external Waiting for Review take?

For external testers, Waiting for Review normally lasts a few hours to 48 hours for the first build of a version, and often much less. Apple does not promise a fixed time, so any figure is an average rather than a deadline. The first build of a new version sits at the longer end, because it needs a complete Beta App Review.

Plan around the upper bound, not the average. If you have a launch or a test session tied to a date, submit the first build a couple of days ahead, because a review that usually clears in a few hours can still take up to 48, and occasionally longer during a backlog. Building in that buffer is what keeps a Friday beta from becoming a Monday one.

Does external testing need a full review?

External testing needs a review, but not the full App Store review. It goes through Beta App Review, which is a lighter check meant for beta distribution, focused on major issues rather than the complete App Store evaluation your app faces when you submit it for public release. Passing Beta App Review is not the same as being approved for the App Store.

This distinction matters for expectations. Beta App Review is generally faster than full App Review, which is why external beta builds often clear within hours, but it is still a real review with a queue and no guaranteed time. Internal testing, by contrast, needs no review at all, which is the key to the skip question below.

Can I skip it? Three honest answers

You cannot skip Beta App Review for external testers, but there are three honest ways to get a build tested without waiting. The table below lays them out.

The short version is that external, first-build testing always needs the review, but internal testers avoid it entirely and later builds of a version usually avoid a fresh one. Choose the path that matches what you actually need: internal for speed within your team, external for real outside testers.

Why the first build waits and later builds may not

The first build of a version carries the full Beta App Review, which is why it waits, while later builds of the same version often skip a new full review. Once Apple has reviewed and approved the first build for a version, subsequent builds under that version number are frequently made available to testers much faster, because the version has already been assessed.

This shapes how you should sequence work. Get the first build of a version submitted and approved early, then iterate with additional builds that clear quickly, rather than starting a brand-new version right before you need to test. A new version string resets you to the slower first-build path, so save version bumps for when you actually intend a new release.

The internal-testers escape hatch

If you need a build tested immediately and cannot wait for external review, internal testers are the escape hatch. Internal testers are up to 100 people who have a role in your App Store Connect account, and they receive builds without any Beta App Review, usually within minutes of processing. For an urgent Friday test, adding a teammate as an internal tester is far faster than waiting on external review.

The trade-off is who they are. Internal testers must be part of your team with an account role, so this works for your own people, not for outside beta users. When you genuinely need external testers, you have to accept the review; when you just need someone to try the build now, the internal channel removes the wait entirely.

Does resubmitting reset the review?

Yes. Uploading a new build of the same version to replace the one in review restarts Beta App Review from the beginning, so an impatient resubmit usually lengthens the wait rather than shortening it. You lose your place in the queue and start over.

Resubmit only when you have fixed a real problem that would have caused a rejection. If the build is fine and simply waiting, leave it in place. If you need to test something right now while it waits, use an internal tester rather than replacing the external build, which keeps your review progress intact.

What normal vs abnormal looks like

Normal is a few hours to 48 hours in Waiting for Review for a first external build, with faster times common and longer ones possible during a backlog. The table below sets expectations across the statuses you will see.

Abnormal is clearly past 48 hours with no movement, especially when others are not reporting the same. That is the point to consider contacting Apple, after confirming the delay is really review and not, say, unanswered export compliance holding the build.

When to escalate

Escalate when you clearly exceed 48 hours in Waiting for Review with no change and none of the ordinary causes apply. Use Apple's Contact the App Review team page and ask about a review taking longer than expected, including your app name, the build, and the submission time. During the 2026 backlog, some developers reported longer external waits, as seen in an Apple Developer Forums thread, so a long wait is not always a problem with your build.

Keep expectations realistic. Escalation is right after 48 hours, but it does not guarantee an instant result, particularly during a general backlog. If you have a deadline, the internal-tester route is a more reliable unblock than hoping an escalation lands in time.

Scan before you submit so review is smooth

The smoothest external review is the one that does not get rejected, and a share of Beta App Review rejections trace to issues you can catch first, including security and privacy problems: an app requesting permissions it cannot justify, cleartext traffic, or an embedded secret. Each rejection sends you back to the queue you were trying to clear.

A scanner like PTKD.com analyzes your .ipa and returns findings ordered by severity and mapped to OWASP MASVS, so you fix these before you submit for external testing. To be clear about the boundary: PTKD does not speed up Apple's review or let you skip it, and it does not replace completing export compliance. It removes the preventable rejections that turn one external review into two.

What to take away

• External testing shows Waiting for Review for the first build of a version, normally a few hours to 48 hours.
• It is Beta App Review, a lighter check than full App Store review, but still a real queue with no guaranteed time.
• You cannot skip it for external testers, but internal testers get builds in minutes and later builds of a version usually clear fast.
• Resubmitting restarts the review; for an urgent test, use an internal tester instead.
• Scan each build with PTKD.com before submitting so a preventable rejection does not extend the wait.