TestFlight Beta Testing for Unity Games

TestFlight is the only sanctioned way to get your Unity game onto other people's iPhones before release. Here's how to run a beta properly.

Internal vs external testers

Getting a build into TestFlight

1. Build and sign with a distribution certificate and App Store provisioning profile.
2. Upload to App Store Connect. Each upload needs a unique, increasing build number.
3. Wait for processing — usually a few minutes.
4. Answer the export compliance question, or the build stays unusable.
5. Add testers or a group.

The 90-day expiry

Every TestFlight build expires 90 days after upload. Testers lose access when it does, and there's no way to extend it — you upload a new build instead.

For a long beta, plan a regular cadence rather than relying on one build indefinitely.

Beta review: what gets rejected

External beta review is lighter than App Store review, but not a rubber stamp. Common rejections:

• Crashes on launch on the reviewer's device.
• Placeholder content or obviously unfinished features.
• Missing or invalid test account credentials, if login is required.
• Beta description that doesn't explain what to test.

Getting useful feedback

TestFlight collects screenshots and feedback in-app, and crash reports automatically. To make it worth reading:

• Write a specific What to Test note per build — "check the new tutorial" beats "test everything".
• Ask for device model and iOS version; performance issues cluster by hardware.
• Bake a visible build number into your title screen so a screenshot tells you which build a tester was on. This is a small change that saves a lot of confusion.

Testing on older devices

Test on the oldest device your minimum iOS version admits, not just a recent one. Unity games are far more sensitive to thermal throttling and memory limits than native apps, and those problems only appear on older hardware.

Frequently asked questions