To take advantage of TestFlight, you’ll need to upload at least one beta build of your app to App Store Connect, and invite testers using their email addresses or by sharing a public link. Testers can get started by accepting your email invitation or following the public link. To install your app and provide feedback, testers will use the TestFlight app for iPhone, iPad, iPod touch, Apple Watch, and Apple TV.
Add up to 100 members of your team who have been assigned the Account Holder, Admin, App Manager, Developer, or Marketing role to quickly test beta builds as you iterate on your app. Each member can test on up to 30 devices. Internal testers can access all of your beta builds available for testing.
External Testers and Groups
Invite up to 10,000 external testers using their email address or by enabling and sharing a public link, which creates an open invitation for anyone to test your app. Simply create a group of testers and add the builds you’d like them to test. You can also create multiple groups and add different builds to each one, depending on which features you want them to focus on. When you add the first build of your app to a group, the build gets sent to beta app review to make sure it follows the App Store Review Guidelines. Testing can begin once your build is approved.
Using Email to Invite Testers
If you know a tester’s email address, you can email an invitation with a link to install your app and start testing. If you have an existing set of external testers or specific people you’d like to invite to test, email can be an effective way to share beta versions of your app.
Using Public Links to Invite Testers
Public links let you share your app with people outside your development team without email or other contact information. You can share your public link on social media, messaging platforms, email campaigns, and more to expand the visibility of your beta test. If you don’t have an established group of external testers, using public links can be an effective way to increase your app’s reach and grow your test audience.
To enable a public link, go to your app’s TestFlight page, click an existing group, and click Enable Public Link. You can then copy the link and share it outside your organization. When you share your public link, many social media platforms will display your app icon, name, and supported device. To help give potential testers additional context, consider including details about your app and TestFlight. Remember not to localize the name TestFlight or create custom badges to promote your app on TestFlight.
If you’d like, you can limit the number of testers that can use the public link to join the group. Depending on your team’s resources, you may want to start small and increase the limit over time. If the group limit is reached or if you disable your public link, anyone trying to become a tester will see a message that your beta is full or no longer accepting new testers. To ensure a good user experience for potential testers, be thoughtful about where you share your public link and when it may be appropriate to remove your public link.
When sharing your app with external testers, you’ll need to let them know what to test and any other important information relevant to testing. Enter these details in your app’s Test Information page in App Store Connect. You should also provide an email address that you monitor so you can receive and respond to feedback that testers provide. Test information is optional when distributing your app to internal testers.
With TestFlight 2.3 or later on iOS 13 or later, testers can send feedback directly from your app simply by taking a screenshot. They can also provide additional context about an app crash immediately after it occurs. To view this feedback, go to your app’s TestFlight page in App Store Connect, and click Crashes or Screenshots in the Feedback section. Feedback from testers on tvOS or earlier versions of iOS will be sent to the email address you provide in Test Information.
TestFlight supports apps for iOS, watchOS, tvOS, and iMessage. Up to 100 apps can be tested at a time, internally or externally, and multiple builds can be tested simultaneously. Builds remain active for 90 days after upload.