{"slug":"testflight","title":"Release to TestFlight","summary":"Send a signed IPA to TestFlight from the Build panel, wait for Apple to process it, then add testers in App Store Connect.","body":"TestFlight is how iPhones install a build before it is on the App Store. Every App Store release also starts as a TestFlight build.\n\n## Before you start\n\n- The Apple account is connected with an App Store Connect API key. See [Connect store accounts](/docs/connect-store-accounts).\n- The app has a finished IPA. See [iOS builds](/docs/ios-builds).\n\n## Send the build\n\n1. Open **Build**, choose **iOS**, and find the finished IPA.\n2. Click **Send to TestFlight**. Clicking it is your approval for testing.\n3. The upload goes to App Store Connect. A release appears in **Publish**, **Releases** with the status **processing**.\n\nIf the app has no App Store Connect record yet, FluxNative creates it on this first upload.\n\n## Wait for processing\n\nApple checks and processes every upload. FluxNative asks for about a minute after the upload. Processing often takes longer, so open **Publish**, **Releases** and click **Check TestFlight status**. When Apple finishes, the release moves to **available for testing**. If Apple rejects the upload, it moves to **failed** and shows **Retry**.\n\n## Add testers\n\n1. In App Store Connect, open the app, then **TestFlight**.\n2. **Internal testing**: add up to 100 members of your App Store Connect team. They get the build right away.\n3. **External testing**: create a group and add testers by email or a public link. The first build for external testers goes through a short Beta App Review.\n4. Testers install the **TestFlight** app from the App Store and accept the invite.\n\n> [!NOTE]\n> App Store Connect may ask about export compliance (encryption) before a build is available. Answer it in App Store Connect under the build.\n\n## Sending again\n\nThe same file is never uploaded twice; clicking again returns the existing release. To ship a change, rebuild. The new build gets a higher build number automatically.\n\nNext: [Production release](/docs/production-release).","sectionSlug":"publish","sectionTitle":"Publish to stores","updatedAt":"2026-09-23T22:51:25.250Z","previous":{"slug":"store-readiness","title":"Store readiness checklist"},"next":{"slug":"google-play-testing","title":"Google Play testing"}}