Testflight Adding an external test person

internal testers: No need to provide all metadata

External testers: To enable external personnel to test the app's pre-release build, you must provide the following metadata

What to test

APP description

Feedback Email

Marketing URL

Support URL

Privacy policy URL (optional)

Beta App Review Contact information

Beta App Review notes (optional) If you haven't provided Metada before, you can now add or edit metadata

Open the App details page

Select Activity.

Select all the builds of the corresponding platform you want to edit

Select the build number you want to test

On the Test Information page, provide information such as what to test, app description, and more. Includes app review information, contact information, demo account information, and any specific build information. This information is only for beta app review, and is different from the app review contact information you submitted to the App Store.
Adding and inviting External testers you can invite 2000 external user places. You usually need to give each user an email address and their name. Your app must be review through the Beta app before inviting external testers to test. This build only has a 60-day available period after the invitation is issued.

add an external test person

On the TestFlight page, select External test

Select the + next to the external tester immediately.

Enter the name of each external tester, email address

Select Import CSV file to import mailing address list

First name, last name, email address

You can also add testers to the group by selecting the Add to Groups option to add

Invite External Testers

In order to add an external tester, each build must pass Apple's audit

Test by selecting Add Build from external testing pane

Select the build version number you want to test

Select Add

If you do not provide the test information, you will need to provide your build to wait for the Beta app to review. Until at least one build has been audited, this version will be displayed as not Available for testing.

Once your build has been reviewed, you will have the option to add an external tester to participate in the test.

The status of build is programmed testing and displays the available term. The external tester will receive the invitation letter.

60 days after expiration in order to continue the test, you need to upload another build. When a new version is uploaded, the internal tester automatically receives the message. In order to publish the version of the letter to an external tester, you will need to submit this version again for review. Once approved, you can select a new build and click Start Test to get a new build.

For more information on managing external testers, read managing external testers and organizing external testers into Gro Ups.

Only the first version will require full review, and the subsequent build version does not require full review.

Submitting the app to Bata app review is not the final submission to the App Store. (this means, as shown in the diagram below, that this effect can be achieved by selecting manual release)
The final note: the difference between internal and external testing is that the internal drive has a limit of 25 people and requires an Apple ID to register a mailbox that can reach 2000 external and does not enforce a mailbox that requires an Apple ID registration, but the version must be approved by Apple. It takes a while to wait, this is not recommended in the case of urgent projects, 25 test equipment can basically meet the requirements.