Skip to content

Apple TestFlight

TestFlight distributes a beta build of an Apple app to testers and collects feedback before release.

Visit Apple TestFlight

What does TestFlight do after you build the app?

Upload a signed Apple build to App Store Connect, the place where your team manages its Apple app. TestFlight lets a tester install that beta build. It does not create the build or publish it on the public App Store.

An App Store release is a separate submission and review. Keep the editable project and signing setup with your team.

How are internal and external testers different?

Apple allows up to 100 eligible App Store Connect users as internal testers and up to 10,000 external testers. The first build for external testing goes to beta review. A TestFlight build can be tested for up to 90 days.

Choose who should receive the build and which version they should test. If using a public invitation link, check who can join before sharing it.

Which account pays for TestFlight distribution?

TestFlight is available through the Apple Developer Program. Apple lists US$99 per membership year or the local equivalent where available. The builder and other services can have separate charges.

Decide which person or organization should control the app listing and membership before uploading a build.

What should you keep from a tester’s report?

App Store Connect shows beta feedback such as screenshots, comments and crash feedback. Apple documents downloading individual feedback items. Record the build and device alongside the issue, and keep any private details out of a shared bug report.

The feedback helps you fix the app in your project. Keep source and build records outside TestFlight.

How would you prepare a beta on paper?

Draw a fictional checklist app and two test groups. Use no Apple account, upload or invitation.

  1. Name the build and job
    Write the pretend build number and ask a tester to reopen a checked item.
  2. Decide who can try it
    Mark the internal and external groups and add a beta review step before the first external group.
  3. Record useful feedback
    Write the expected result, device and actual result. Mark that a future installed test must use fictional data and separate test connections.