Question 1

Does TestFlight have the same strict criteria as if an app was being published live to the App Store?

Accepted Answer

According to Apple’s App Store Review Guidelines, any app submitted for beta distribution via TestFlight should be intended for public distribution and comply with the App Review Guidelines. This implies that the same rules apply as if the app were being published publicly on the App Store. However, the review process for beta builds, particularly for external testers, is generally less strict than a full App Store review. TestFlight reviews for internal testers are noted to have no waiting time as they do not undergo the same initial review process.

Question 2

Is TestFlight beginner-friendly?

Accepted Answer

TestFlight streamlines the process of app testing significantly, making it beginner-friendly for developers. It simplifies user onboarding by focusing on a user-centric model where you add users directly via email or invite links, eliminating the need to collect and manage device UDIDs. TestFlight also handles provisioning profiles automatically and offers robust features like crash reporting and feedback collection. While initially setting up beta testing might require some acclimatization with App Store Connect, TestFlight’s overall design is geared towards ease of use for distributing and managing beta versions of iOS apps.

Question 3

Does a version number update on TestFlight trigger a new review process?

Accepted Answer

Yes, when you submit a new version number for your app to TestFlight, it typically requires a new review by Apple. This review can take between 48 hours to 3 days in the worst-case scenarios. However, subsequent new build numbers within the *same* version do not require a new review. For example, if version 1.8 (build 50) is reviewed, builds 51, 52, etc., of version 1.8 will not need re-review.

Question 4

Are there different types of testers supported by TestFlight?

Accepted Answer

Yes, TestFlight supports two types of testers: internal and external. You can have up to 100 internal testers per app, each capable of testing on up to 30 devices. Internal testers must be registered App Store Connect users with specific roles (Account Holder, Admin, App Manager, Developer, or Marketing). For external testing, TestFlight supports up to 10,000 external testers per app, who can be invited via email or a shareable public link, and do not necessarily require an Apple ID.

Question 5

How long are TestFlight builds available for testing and can previous builds be accessed?

Accepted Answer

TestFlight builds are typically available for 90 days from the date they are uploaded to App Store Connect. Testers can install previous builds within this 90-day window, provided the developer has not manually expired them. This feature is useful for identifying whether bugs are new or existed in earlier versions of the app.

Question 6

How can testers provide feedback and report crashes using TestFlight?

Accepted Answer

TestFlight offers integrated mechanisms for feedback and crash reporting. Testers can submit feedback by taking a screenshot within the app, which then allows them to mark up the image and send it directly. Alternatively, feedback, with or without a screenshot, can be sent from within the TestFlight app itself. For crashes, TestFlight automatically prompts users to share crash reports with the developer after an app unexpectedly exits, providing valuable diagnostic information for improvement.

Test Flight（test）

Regulatory License

Account Information

Why Choose Test Flight（test）

Key Point 1

Key Point 2

Key Point 3

Key Point 4

Key Point 5

Key Point 6

Key Point 7

Key Point 8

Key Point 9

Key Point 10

Advantages

Disadvantages

Broker Details

More Brokers

Resources

Legal

Support