Short answer: to add external testers in TestFlight, create a group in App Store Connect, add a build, fill in your beta app description and beta app review information, and wait for App Review to approve the first build for TestFlight. Then invite people by email or with a public link. Apple allows up to 10,000 external testers. Here's each step and what trips people up.
External vs internal, in one line
Internal testers are up to 100 members of your App Store Connect team with specific roles. External testers are anyone else: customers, friends, community members or a testing service's testers. They don't need to be on your team.
Step 1: add test information
In App Store Connect, open your app, select the TestFlight tab and add test information: what you want testers to try and a feedback email. Apple says the beta app description and beta app review information are required before you share with external testers.
Step 2: create a group and add a build
Groups are how you distribute builds. Create an external group, for example "Public beta", and add the build you want tested. Apple says builds are automatically sent for review once they're added to a group.
Step 3: pass beta app review
Your first build for external testers must be approved by App Review for TestFlight. Help the reviewer: describe what's new, explain how to reach the main features, and provide a demo account if the app has sign-in.
Step 4: invite testers
By email
Best when you know exactly who you want. Each person gets an invite with a link to install your beta in the TestFlight app.
By public link
Best when you don't have contact details, for example sharing in a newsletter or on social media. You can set criteria such as device type and OS version, and see how many people viewed and installed your beta.
Remember to disable the link when you reach your limit, as Apple suggests, so people who try to join know it's closed.
Step 5: keep them testing
Testers can take screenshots and send feedback directly from the app, and you receive crash reports. Read them in the TestFlight section of App Store Connect, filter by platform or OS version, and ship fixes as new builds to the same group.
The official TestFlight facts
From Apple's TestFlight overview:
- You can add up to 100 internal testers from your team (Account Holder, Admin, App Manager, Developer or Marketing roles).
- You can invite up to 10,000 external testers by email or public link.
- External testing needs a beta app description and beta app review information, and your first build in an external group must be approved by App Review for TestFlight.
- You can share up to 100 builds, and testers can use your betas on up to 30 devices.
- Public links can have criteria such as device type and OS version, and you can see how many people viewed and installed from the link.
- Testers send screenshot feedback and crash reports, which you read in the TestFlight section of App Store Connect.
Quick checklist before you invite external testers
- [ ] Beta app description written in plain language: what's new and what to try.
- [ ] Beta app review information filled in, including a demo account if the app needs sign-in.
- [ ] A feedback email you actually check.
- [ ] Separate groups for different goals (for example, a new-feature group and a regression group).
- [ ] Public link criteria set if you only want certain devices or OS versions.
- [ ] A tester brief with three or four concrete tasks.
- [ ] A plan to read screenshot feedback and crash reports at least every other day.
- [ ] A note of what you'll change before submitting the final build for App Store review.
Mistakes that slow down a TestFlight beta
- Sending the first external build without review notes. Reviewers need to know how to reach each feature.
- A demo account that expires. Check it works the day you submit.
- One giant group. Separate groups keep feedback focused and avoid sending risky builds to everyone.
- Leaving a full public link open. Apple suggests disabling it once you reach your limit.
- No "What to test" notes. Testers who don't know what changed rarely find what you care about.
- Ignoring crash reports until launch week. Read them every few days while testers still remember what happened.
- Asking testers for App Store reviews. Keep beta feedback private and honest; TestLancer never sells reviews or ratings.
FAQ
Do external testers need an Apple Developer account?
No. They install the TestFlight app and accept your invite.
Does every build need beta review?
Apple says builds are sent for review automatically when added to a group, and the first build must be approved. Check App Store Connect for the status of each build.
How many devices can a tester use?
Apple says testers can use your betas on up to 30 devices.
Next step
If you need real people to test your iOS build on their own iPhones and iPads, TestLancer's iOS app testing recruits testers for TestFlight builds and returns bug reports with steps to reproduce. TestLancer does not sell reviews, ratings or installs, and nobody can promise that App Review will approve a build. You can start a project at testlancer.com.
Top comments (0)