Let Apple distribute your beta app to testers for you using TestFlight Beta Testing. You upload your builds to App Store Connect and then use App Store Connect to manage the builds, invite testers, and see tester engagement.
Important: Rigorously test your app on a variety of devices and operating system versions. Because different kinds of devices and releases have different capabilities, it’s not sufficient to test your app on a device provisioned for development or on a simulator. A simulator doesn’t run all threads that run on devices, and launching apps on devices through Xcode disables some of the watchdog timers. At a minimum, test the app on all devices that you support and have available. In addition, keep prior releases installed on devices for compatibility testing. If you don’t support certain devices or releases, edit the deployment info settings accordingly.
First prepare your app for distribution and then create an archive of your app.
Validate the archive of your app and if it passes App Store Connect tests, upload it to App Store Connect.
Go to Viewing builds and file sizes and View and edit app information in App Store Connect Help.
Important: After your app is uploaded or released, you can’t change some of this metadata, so it’s important to choose your settings carefully. To learn which properties can be edited at any time in App Store Connect, go to Required, localizable, and editable properties.
To add, invite, and view testers in App Store Connect, go to TestFlight beta testing overview in App Store Connect Help. If you invite external testers, your app is submitted to Beta App Review.
Tip: To test the variants that the App Store builds before you release your app, invite internal testers (your team’s App Store Connect users) only and download the variants using TestFlight.
Testers install the free TestFlight app on their devices. Then testers use TestFlight to redeem invitations, install your app, send feedback, and get updates. Testers download and install thinned variants of your app.