// answer

What to submit before inviting external testers in TestFlight

Short answer

Submit your beta test information, beta app review details, and a build to App Store Connect, then wait for TestFlight App Review approval before sending external invitations.

Knowing the number is the easy part. Finding people who actually stay opted in is the rest of it: Get testers

What do I need to submit before inviting external testers in TestFlight

You need to submit a beta build in App Store Connect, complete the required TestFlight test information, and provide the beta app review details Apple asks for. Your first external build must be approved by TestFlight App Review before you can invite external testers.

The part people get wrong is thinking that uploading the build is enough. It is not. Apple says external testing requires a build, an external group, and the first build approved for TestFlight beta testing. Apple also says you need beta app description and beta app review information before sharing with external testers.

Start in App Store Connect, then open the app’s TestFlight tab and enter the test information. Apple’s help page says this includes the beta app description and a feedback email address, and that the information can be added when you create the app record or before you invite external testers. If you skip it, the submission is incomplete for external review.

You also need the beta app review details that Apple uses to review the build. Apple’s documentation says beta app review details can include a demo account login and contact details in case the reviewer has questions. That is the inconvenient part many teams forget, because a private or signed-in app often works for you but not for Apple’s reviewer.

After the build is uploaded, add it to an external group and submit it for TestFlight App Review. Apple says your builds are automatically sent for review once they are added to a group, and the first build of a version requires a full review. Later builds for the same version may not need the same level of review, but the first one does.

If your build uses Apple-hosted asset packs, submit the latest versions of those asset packs too. Apple calls that out directly in the external tester flow, and it is one of the easiest reasons a review stalls even when the app binary itself is ready. The build review is about the package testers will actually receive, not just the archive you uploaded.

You can create the external group only after you have an internal group. Apple says the external group depends on first creating an internal group for internal testing. That order matters when a team tries to move fast, because people often upload a build first and discover later that the external distribution path is not fully set up.

For a clean setup, use this sequence: create the app record in App Store Connect, fill in TestFlight test information, prepare beta app review details, upload the build, create the internal group, create the external group, add the build, then submit for TestFlight App Review. Once Apple approves the first build, you can invite external testers by email or public link.

If you want a fast place to keep tester coordination organized, DevConnect keeps the workflow on your side of the process, which is the part you control: https://devconnectplatform.com. Apple still requires the same submission steps in App Store Connect before external testers can join.

Do not confuse internal testing with external testing. Apple says internal testers are members of your App Store Connect team, while external testers are people you invite who are not App Store Connect users. Apple also says builds marked TestFlight Internal Only can only be added to internal tester groups, not external ones.

One more thing people miss is that Apple can reject either the build or the metadata. If the review fails, the build status becomes Rejected and you need to inspect the App Review details in App Store Connect, fix the issue, and submit again. The fix is often not code, it is missing review information, a bad login, or a build that cannot reach the reviewer’s path.

A practical example: if your app requires a demo account, create one before submission and write the credentials into the beta app review details. Then test the flow on a clean device, not just on your logged-in phone. That usually catches the mistake where the reviewer lands on a login screen with no way in, which blocks approval even if the app itself is stable.

The short version is simple. Before inviting external testers in TestFlight, you submit a build, complete the TestFlight test information, provide beta app review details, and get the first external build approved by TestFlight App Review. After that, external invitations are allowed.

What counts as TestFlight test information

Apple’s TestFlight help says the test information includes the beta app description and a feedback email address. The description tells testers what to look for, and the feedback email becomes the reply-to address for invitations and the contact route inside TestFlight.

What is beta app review information

Apple’s beta app review detail documentation says the review package can include a demo account login and contact information. Use that when the reviewer needs to get past authentication, feature flags, or private content. If the reviewer cannot reproduce the app the way you intended, approval usually stops there.

Do I need approval every time I upload a new build

Apple says the first build of a version requires a full TestFlight App Review, while later builds for the same version may not need one. Even so, Apple still reviews builds added for external testing, so do not assume a later upload is automatically ready to distribute.

Can I invite external testers before the build is approved

No. Apple says you need the first build approved for TestFlight beta testing before external invitations go out. You can prepare the group and the submission, but the external invite step waits on approval.

Sources

  • Apple Developer, Invite external testers: https://developer.apple.com/help/app-store-connect/test-a-beta-version/invite-external-testers
  • Apple Developer, Provide test information: https://developer.apple.com/help/app-store-connect/test-a-beta-version/provide-test-information
  • Apple Developer, TestFlight: https://developer.apple.com/testflight/
  • Apple Developer, TestFlight App Review glossary: https://developer.apple.com/help/glossary/testflight-app-review/
  • Apple Developer Documentation, Beta App Review Submissions: https://developer.apple.com/documentation/appstoreconnectapi/beta-app-review-submissions?changes=_7
  • Apple Developer Documentation, Beta App Review Detail: https://developer.apple.com/documentation/appstoreconnectapi/beta-app-review-detail?changes=_9%2C_9

Frequently asked questions

What is the difference between internal and external TestFlight testers

Internal testers are members of your App Store Connect team. External testers are invited people who are not App Store Connect users.

Can I share a public link for external testers

Yes. Apple supports public invitation links for external testing, after the build and TestFlight review steps are complete.

What happens if Apple rejects the build

The build is marked Rejected in App Store Connect, and you need to fix the problem in the build or the submitted metadata before resubmitting.

Know someone stuck on this? Send them the answer.

Sources

Every link here was fetched and confirmed to resolve before this page went live.

More on this topic: App testing

Related questions

Not the question you had?

Ask it. Every source gets fetched and checked before anything goes up, so it takes a day or two, and questions that cannot be answered honestly do not get a page at all.

No account, no email address needed.

Still stuck on the 14 days?

DevConnect is a tester exchange: you test someone else's app, they test yours. No payment, no fake installs. You can also count your days without an account.