Take advantage of TestFlight by uploading a beta build of your app or App Clip to App Store Connect. Testers will use the TestFlight app to install your app and provide feedback. TestFlight supports apps for iOS, iPadOS, macOS, tvOS, watchOS, and iMessage, as well as automatic updates to ensure that testers always test the latest available build. 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.
You can designate up to 100 members of your team who hold the Account Holder, Admin, App Manager, Developer, or Marketing role as beta testers. You can also create multiple groups and add different builds to each one, depending on which features you want each group to focus on. While you iterate on your app, each member can quickly test beta builds on up to 30 devices and access all of your beta builds available for testing.
External testers and groups
Invite up to 10,000 external testers using their email addresses 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. Before testing can begin, the first build of your app must be approved by TestFlight App Review. This build is automatically sent for review when you add it to a group.
Using email to invite testers
If you know a tester’s email address, you can email them 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 are an effective way to connect with people who can test your app if you don’t have an established group of testers. No contact information is needed. Simply 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 on social media, messaging platforms, email campaigns, and more. Remember not to localize the TestFlight name or create TestFlight badges to promote your app.
You can also limit the number of testers that can join using the public link. If the group limit is reached, or if you disable your public link, a message will notify anyone trying to join that your beta is no longer accepting new testers. To ensure a good user experience, be thoughtful about where you share your public link and when it may be appropriate to remove it.
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. Provide these details on 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 from testers. Test information is optional when distributing your app to internal testers.
With the TestFlight app for iOS, iPadOS, and macOS, 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. You can view this feedback by going to your app’s TestFlight page in App Store Connect, and clicking Crashes or Screenshots in the Feedback section. Feedback from testers on iOS 12 or earlier, tvOS, or watchOS will be sent to the email address you provide in Test Information.
When testers are invited to beta test your app, they’re prompted to install the TestFlight app from the App Store on their iPhone, iPad, iPod touch, Mac, or Apple TV if they don’t already have it installed. The TestFlight app makes installing betas simple, and you don’t need to keep track of UDIDs or provisioning profiles.
Documentation and help
For step-by-step instructions on creating groups, inviting testers, and adding builds in TestFlight, read App Store Connect Help.