This documentation is available as Markdown for AI agents and LLMs. See the full Markdown index or append .md to any documentation URL.

Learn how to get an iOS build onto testers' devices with TestFlight, and when to use internal versus external TestFlight testing.

TestFlight is Apple's internal and beta app distribution service. After you create an iOS production build, your app can reach testers' devices through TestFlight before the app is released publicly on the App Store.

There are two kinds of testing and the difference decides how quickly your build reaches your app users. Internal testing goes to your own App Store Connect team and is available as soon as the build finishes processing. External testing reaches anyone else. However, you have to add the build to a group in App Store Connect, and the group's first build must clear Apple's Beta App Review process.

Quick start

If you have an Apple Developer account and nothing else set up yet, you can create an app record on App Store Connect, build a production .ipa, and submit it to TestFlight with a single command:

The rest of the guide covers internal and external testing in more detail.

Internal versus external testing

Before you can publicly release your app on the Apple App Store, you can distribute it to testers through TestFlight in two ways: Internal testing and External testing. The difference is how quickly your build reaches your testers:

Internal distribution is not internal testing. Both of these terms sound identical. EAS internal distribution produces an ad hoc or enterprise-signed build, which is installed from a URL and are limited to registered unique device identifiers (UDIDs). TestFlight internal testing needs "distribution": "store" and goes through Apple.

Set up internal testing

Internal testing goes to your own App Store Connect team and is available as soon as the build finishes processing.

2

Wait for processing

Apple processes the build before it can be distributed. This usually takes 5 to 10 minutes, though there is no guaranteed time. After processing, Apple notifies you by email.

After your app is processed, log in to App Store Connect, select your app, and go to TestFlight. You should see the build listed under iOS Builds.

3

Create an internal testing group

Skip this step if you already have an internal testing group. You can add testers to an existing group instead.

In App Store Connect, go to TestFlight > click the plus (+) icon next to Internal Testing > enter the name of the Internal Group > click Create.

Then, click the plus (+) icon next to Testers to add testers to the group. You can add testers from your App Store Connect team by selecting their emails and clicking Add. Testers will receive an email invitation to test your app.

Tip: You can also target internal groups directly from the EAS CLI if you have pre-existing internal testing groups. For example, the command eas submit --platform ios --groups "QA Team" --what-to-test "New onboarding flow" targets the internal testing group named "QA Team" and sets the "What to Test" description for the build.

Set up external testing

External testing reaches people outside your App Store Connect team.

You must create an internal group before App Store Connect will let you create an external group.

1

Create an external group

In App Store Connect > TestFlight > click the plus (+) icon next to External Testing > enter the name of the External Group > click Create.

2

Use an existing internal build

You can use an existing internal build for external testing. Click Add Builds > under Select a Build to Test, select the build you want to use > click Next.

3

Fill in test information

External testing requires a beta app description and a feedback email before Apple accepts the build for review. If your app has a login, enable Sign-in Information and provide a test account for Apple to use. Click Next.

4

Submit for Beta App Review

Provide the information requested under What to Test and click Submit for Review. Apple reviews the build and notifies you by email when it is approved.

5

Invite testers

Once approved, invite by email, import a CSV, or turn on a public link. A public link can be open to anyone or filtered by device and OS version.

FAQs

{
  "ios": {
    "config": {
      "usesNonExemptEncryption": false
    }
  }
}

jobs:
  build_ios:
    name: Build iOS
    type: build
    params:
      platform: ios
      profile: production

  testflight:
    name: Distribute to TestFlight
    type: testflight
    needs: [build_ios]
    params:
      build_id: ${{ needs.build_ios.outputs.build_id }}
      internal_groups: ['QA Team']
      external_groups: ['Public Beta']
      changelog: |
        What's new in this release:
        - New features
        - Bug fixes