Short answer: before external testers can install your app, Apple requires a beta app description and beta app review information, and the first build in an external group must be approved by App Review for TestFlight. Make the reviewer's job easy: say what to test, how to reach each feature, and give a working demo login if the app needs one.
What Apple asks for
Apple's TestFlight page says your beta app description and beta app review information are required to share a beta with external testers, and your first build must be approved by App Review for TestFlight. Builds are automatically sent for review once they're added to a group.
Writing the beta app description
This text appears in testers' invites, so it does two jobs: tells reviewers what the app does and tells testers what's new. Keep it plain: "Habit tracker for students. This beta adds reminders and a weekly summary. Please test both."
Beta app review information
Contact details
A person and email App Review can reach.
Demo account
If the app requires sign-in, provide a working username and password for a test account. Make sure it doesn't expire during review.
Notes
Explain anything unusual: hardware needed, features behind a paywall, regions where content differs, or how to trigger a feature.
Common causes of delay
Apps that crash on launch, login details that don't work, placeholder screens, and features that can't be reached. Test the exact build with an internal tester before adding it to an external group.
After approval
Invite external testers by email or public link. Watch screenshot feedback and crash reports in App Store Connect. When you're ready, select the build and submit it for App Store review. Apple's review for the App Store is separate from beta review, so approval for TestFlight doesn't guarantee App Store approval, and no testing service can guarantee it either.
Using a testing service with TestFlight
If you work with a service such as TestLancer, you share a TestFlight invite or public link after the build is approved. Testers install it through the TestFlight app; you never need to share your Apple ID or App Store Connect login.
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
Does every new build go through review?
Apple says builds are sent for review automatically once they're added to a group, and the first build must be approved. App Store Connect shows each build's status.
What if beta review rejects the build?
Read the message in App Store Connect, fix the issue or add the missing information, and resubmit.
Does internal testing need beta review?
Apple describes the review requirement for external testing.
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)