TL;DR: To test an app with TestFlight, archive a release build in Xcode, upload it to App Store Connect, add internal or external testers, install the beta on a compatible device, and use feedback to fix issues before App Store submission.

TestFlight is Apple’s beta testing path for iOS apps. The usual flow is straightforward: build a release archive, upload it to App Store Connect, add testers, and use their feedback to fix issues before submission. If you want the timing side of the process, see How Long Can an App Stay on TestFlight?.

Apple’s TestFlight overview and Distributing Your App for Testing describe the official path.

Build an archive in Xcode

TestFlight starts with an archive. In Xcode, select a generic iOS device as the run destination so Archive becomes available, then build the app as a release archive.

Apple documents this setup in Distributing Your App for Testing. A practical walkthrough of the same flow also notes that switching the destination to Generic iOS Device enables Archive.

Upload the build to App Store Connect

After you archive the app, validate it and distribute it to App Store Connect. In Xcode, the flow is usually:

  1. Open Organizer for the archive.
  2. Validate the app.
  3. Distribute the app to App Store Connect.
  4. Choose the upload path for an iOS app.

After upload, App Store Connect still needs time to process the build. That is normal. In App Store Connect, the build moves from uploaded to processing and then into the available builds list in TestFlight. Testers usually cannot install it until processing finishes.

Add testers in TestFlight

Apple supports two tester paths: internal testers and external testers. Internal testers are App Store Connect users on your team, which makes them useful for quick checks while you are still fixing obvious issues. External testers are everyone else, invited by email or through a public link, which helps when you want feedback from people outside your App Store Connect account.

External testing may require beta app review before wider access. Apple covers that in its TestFlight materials and App Store Connect guidance, so expect an extra step if you plan to share the build beyond your team.

Install the app on a test device

From the tester side, the process is short:

  1. Accept the invite or open the public link.
  2. Install the TestFlight app if it is not already on the device.
  3. Open the beta build in TestFlight.
  4. Install it on a device that meets the app’s requirements.

That last step matters. If the build needs a certain iOS version, device capability, or region, the test device has to match. TestFlight will not fix an incompatible setup.

Test the app against the review checklist

Before you submit to App Store review, use TestFlight to check the parts that tend to fail later:

  • Launch and startup behavior
  • Sign-in and account creation
  • The core user flow
  • Permission prompts and the app’s response when permissions are denied
  • In-app purchases, if your app has them
  • Feature claims, labels, or metadata that need to match the live build

This is where TestFlight saves time. You catch awkward edges before a reviewer does, which is easier than dealing with a rejection after the fact.

For a broader submission checklist, How to Evaluate an App Before Submission covers the same review mindset from another angle.

Collect feedback and ship a new build

TestFlight lets testers send feedback directly from the app, and developers can use that feedback to fix issues, rebuild, and upload a new version for another round. That loop is normal in beta testing.

After each change, archive again in Xcode, upload the new build, wait for processing, and recheck the updated version before submission. If the crash is gone but the sign-in screen is now doing something odd with a loading spinner, that is still useful feedback.

Worked example: a first TestFlight pass for a small iOS app

A solo developer is preparing a first beta of a simple journaling app.

First, they switch Xcode’s run destination to Generic iOS Device, archive the app, validate it, and upload the build to App Store Connect. Once processing finishes, the build appears in TestFlight.

Next, they add one internal tester from App Store Connect and invite one external tester by email. The internal tester checks the app quickly, while the external tester tries it on a real device outside the development setup.

The feedback points to a crash on launch after the app restores saved data. The developer fixes the issue, makes a new archive, uploads a new build, waits for processing again, and asks both testers to try the updated version. After the app stays stable through the same flow, it is in a much better place for submission.

When TestFlight is not enough

TestFlight is useful, but it does not replace the rest of App Store prep. You still need a build ready to upload, plus final metadata, screenshots, and compliance checks that match the app you are shipping. TestFlight can help you catch problems in the build itself. It cannot fix a sloppy listing or missing review details.

If you are building the full launch checklist, return to the broader first App Store review preparation guide.