External TestFlight testing waits on a review. Internal testing does not.
A build you want people outside your company to install has to be approved by TestFlight App Review first. A build your own team installs does not. Apple draws that line in its build status reference, where Ready to Submit means the build can be distributed to internal testers, or can be submitted to TestFlight App Review for external testing. Same build, two doors. The caps either side of that line are 100 internal testers and 10,000 external testers per app, both figures read on Apple's own pages on 21 October 2026.
The thing nobody tells you is how long the wait is, and the reason is that Apple never says. Below is what the review actually looks at, the two submission limits that decide how many attempts you get, what a rejection costs, and the one figure Apple does publish about review times, which is not about beta builds at all.
Check whether your build needs itThe short version
One gate, on the first build of a version, and only for external groups.
Apple calls it TestFlight App Review. The status you watch in the build table reads In Beta Review, and the older name Beta App Review is still what most people type into a search box. It is one thing with three labels. It reviews the build and the test information you wrote for it, and it stands between your external tester group and the install.
The review is not per build forever. Apple says the first build you submit requires a full review, and that later builds for the same version might not. Might not is the whole promise, so a release plan that assumes every later build walks straight through is a plan with a gap in it. A new version number puts you back at the start.
Does external TestFlight testing need App Review, and does internal testing?
External does. Internal does not. The cleanest statement of it is in Apple's App build statuses reference, read on 21 October 2026, which describes the Ready to Submit status as a build that can be distributed to internal testers, or can be submitted to TestFlight App Review for external testing, or to App Review for distribution to customers. Three destinations, one of which needs no approval from anyone.
Two statuses in that table exist only on the external path. Waiting for Review means the build has been submitted to TestFlight App Review and will need to be approved before you can begin external testing. In Beta Review means it is being reviewed right now. There is no internal equivalent, and the App Store Connect Help page for adding internal testers does not mention a review anywhere in its procedure. I read that page on 21 October 2026. It goes: create a group, invite eligible users, add a build, and the users you chose get an email inviting them to test.
Two sequencing rules catch people before the review does. The first is that to create an external group for external testing, you must first create an internal group for internal testing. The second is about the build. A build uploaded as TestFlight Internal Only from Xcode or Xcode Cloud is marked as internal under the build number, and Apple says it can only be added to internal tester groups, so it cannot go to external testers or to customers at all. If an external group refuses to accept the build you just uploaded, check that flag before you check anything else.
On Android the shape of this is different enough that the habits do not transfer. Google puts its own friction on the track rather than on the build, which is why google play closed testing has rules about who is on your list rather than a queue your build sits in. If you are shipping both platforms off one release, plan for two different gates on two different clocks.
Apple, App Store Connect Help, Invite external testers, read 21 October 2026
Check yours
Does this build need a review before anyone installs it?
Pick who you are handing the next build to. Every answer below comes from Apple's own App Store Connect Help pages, read on 21 October 2026.
Nothing picked yet. The short rule: internal groups install straight away, external groups wait for an approval.
How many testers can each track take?
As of 21 October 2026, Apple's figures are 100 and 10,000. The TestFlight overview page states both in one sentence: you can add external testers, up to 10,000 people, and internal testers, up to 100 App Store Connect users with access to your content. The page for adding internal testers repeats the 100, and the page for inviting external testers repeats the 10,000 and adds that it is per app.
The number is the less interesting half. What an internal tester is matters more: an App Store Connect user with access to your content. Apple's TestFlight page puts it as members of your development team who hold the Account Holder, Admin, App Manager, Developer or Marketing role. So every one of those 100 is a person you have added to your account and given a role, which is a decision about access to your business, not a line on a mailing list. External testers are the opposite: no account, no role, nothing but an email address or a link they clicked.
Two limits bite long before the tester cap does, and both are about submissions rather than people. Apple says you can only have one build of each version in review at a time, and that once that build is approved you can submit additional builds. It also says you can submit up to six builds for TestFlight App Review within a 24-hour period. On a day when the first build comes back rejected, those two sentences decide how many more attempts you get. If you are using a public link, you can also set your own ceiling on it, anywhere between 1 and 10,000, which is worth doing before you post the link anywhere public.
Apple's caps are maximums. The number that trips people up on Android is a minimum, because Google asks for a specific count of real testers over a specific stretch of time before a personal developer account can publish at all. The google play twelve testers rule covers that one. Nothing on the Apple side asks you to find a minimum number of testers.
Apple, App Store Connect Help, Invite external testers, read 21 October 2026
How long does TestFlight App Review take?
Apple does not say. That is the honest answer, and it is worth knowing because the figure everyone quotes is real but comes from somewhere else. On Apple's App Review page, read 21 October 2026, the line is that App Review works around the clock, typically reviewing at least 50 percent of submissions in less than 24 hours and 90 percent in less than 48 hours. App Review Help repeats it as a goal on its page about tracking a submission's review status, and adds that most submissions are reviewed within 48 hours. Neither page contains the word TestFlight outside its navigation, and neither mentions beta builds.
I then read the four pages that do cover beta review, on the same day: the TestFlight overview, Invite external testers, Provide test information, and the App build statuses reference. None of them states a number of hours or days for TestFlight App Review. So the widely repeated 24 to 48 hours is Apple's published performance on App Store submissions, borrowed and reapplied to a different queue. It may well be the right rough expectation. It is not a commitment Apple has made about your beta build, and nobody is breaking a published promise when your build sits in Waiting for Review all afternoon.
What you can plan against is the clock that does have a published number on it. A build is testable for up to 90 days, and the Expired status in Apple's own table says the build cannot be used for testing because it has passed its 90-day availability window. That window belongs to the build, not to the approval, so every hour in review is an hour off the end of it. The testflight build expiry rules are the ones to build a schedule around.
Two practical things shorten the gap between approval and somebody actually testing. First, tick Automatically notify testers when you add the build, because Apple says that if you leave it deselected you must manually distribute the build to testers after it is approved. Second, know who gets told. The approval email goes to users on the account with the Admin role, so if the only Admin is on holiday, an approved build can wait a day for no reason at all.
What does the review look at, and what happens if it says no?
It looks at the build and its accompanying metadata. That is Apple's phrasing, and the metadata half is the part people forget. The Provide test information page, read 21 October 2026, says that when you distribute your app to external testers you need to enter additional TestFlight test information for TestFlight App Review. The Beta App Description field is required. The Feedback Email is where testers reach you from inside the TestFlight app, and it is also the reply-to address on the invitation emails. Both are reviewable, and both can be changed at any time after approval.
A rejection is heavier here than on the store side. Apple's status reference says a build rejected by TestFlight App Review can no longer be used in TestFlight, and that to begin testing you upload a new build. There is no fixing the description and resubmitting the same binary. You read the reason by clicking App Review in the App Store Connect sidebar under General, where the rejection details for the beta build sit. Apple's own answer on appealing is a single line in the help page's FAQ: to appeal your beta build being rejected, contact TestFlight App Review.
Apple publishes no breakdown of why beta builds get rejected. What it does publish, on the App Review page, is that over 40 percent of unresolved issues are related to guideline 2.1 on app completeness on average, which covers crashes, placeholder content and incomplete information. That figure is about App Store submissions rather than beta builds, so treat it as a hint and not a statistic about TestFlight. The hint is still useful: a beta is allowed to be unfinished in features, and a build that will not launch or that shows a screen of filler text is a different kind of unfinished.
Getting through beta review buys you testers, and nothing more than that. The build still goes to App Review when you want customers to have it, under the full guidelines, with screenshots and pricing and age ratings attached. Our walkthrough of how to publish to app store picks up at that point. Apple's build table makes the same point in passing: testers who received an invitation keep their access even after the app is live for customers.
Internal and external testing, on the figures Apple publishes
| The question | Internal testing | External testing | Same on both |
|---|---|---|---|
| Who a tester can be | An App Store Connect user with access to your content | Anyone with an email address or your public link | No |
| Cap per app | 100 internal testers | 10,000 external testers | No |
| Approval before anyone installs | No review step on Apple's page | TestFlight App Review on the first build | No |
| Role needed to set it up | Account Holder, Admin, App Manager, Developer or Marketing | Account Holder, Admin or App Manager | No |
| How long a build stays testable | Yes | Yes | 90 days on both |
| Getting new builds out without clicking | Enable automatic distribution, set on the group | Automatically notify testers, set when you add the build | No |
| What a rejection costs you | Nothing to reject | The build is finished, upload a new one | No |
Every cell above comes from App Store Connect Help or Apple's TestFlight page, read on 21 October 2026. Where a row says no review step on Apple's page, that means the page for adding internal testers describes the whole procedure and never mentions one.
Where this lands if a builder generated your app
The review gate does not move because a tool wrote the code. A builder can get a signed build into App Store Connect for you. Moving that build into an external group and clicking Submit Review is an App Store Connect action, and Apple requires the Account Holder, Admin or App Manager role to do it. That is you, on your account.
Newly is an AI app builder. You describe an app in plain English and it writes a real React Native and Expo project that you own, with two-way GitHub sync so the code is never trapped anywhere. It uploads iOS builds to TestFlight, publishes to Google Play internal testing, and can build a standalone Android APK. It is paid, from $25 a month, with no free tier. What it does not do is submit to the App Store on your behalf, because App Store Review Guideline 4.2.6 rejects apps created from a commercialized template or app generation service unless they are submitted directly by the provider of the app's content.
In practice that splits the work in a useful way. The build and the upload are automated. The internal group, the external group, the test information and the submission are yours, and they are the parts that need a human who knows what the app is for. The fastest honest route is to get the first build to your own team the day it exists, since that path has no queue, and send the external group for review while they are still finding things.
Questions people ask about TestFlight external testing review
Yes, for the first build. App Store Connect Help says that after you submit your build to TestFlight App Review, Apple reviews the build and its accompanying metadata, and that the first build you submit requires a full review while later builds for the same version might not. The build status reference is blunter: Waiting for Review means the build has been submitted to TestFlight App Review and will need to be approved before you can begin external testing. Read on 21 October 2026.
Get a build to your own team before you queue for anything
Internal testing has no review and no waiting. Write the Beta App Description and the Feedback Email the same week, so that when you do submit the external group, the metadata half of the review is already done.
Start building