TestFlight for Mac internal and external testing build processing and beta review
Parent: macOS App Testing and Release QA · Published reference · snapshot 2026-10-02
↓ Facts as markdownall context files
Source-anchored research for TestFlight for Mac internal and external testing build processing and beta review. Run status: COMPLETED.
These notes link each claim to its source. Some citations identify archived research reports that are no longer hosted on this site. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.
Problems, failure modes and limitations
- Beta App Review requires a beta app description and feedback email in Test Information (Account Holder, Admin or App Manager can set it; also settable via the Beta App Localizations API). Managed Apple Accounts in reserved domains cannot be used to test. (high confidence) [source]
- Transporter uploads missing an application identifier fail TestFlight eligibility with error 90886, and the build then does not appear in the App Store Connect build list; the same version number cannot simply be re-uploaded (bump the build number). (low confidence) [source]
Facts and statements
- Internal testing allows up to 100 App Store Connect team members (Account Holder, Admin, App Manager, Developer, Marketing roles); external allows up to 10,000 testers per app; a tester can install on up to 30 devices. (high confidence) (verified as of 2026-10-02) [source]
- Builds are testable for up to 90 days; after expiry testers lose access. Mac builds require Xcode 13 or later. (high confidence) (verified as of 2026-10-02) [source]
- External testing requires an internal group to exist first, then external groups; the first build of a version gets full Beta App Review, later builds of the same version may skip full review; max 6 builds submitted per 24 hours; testers join by email, CSV, or public link (optional 1-10,000 cap, filter by OS version). (high confidence) (verified as of 2026-10-02) [source]
- Builds uploaded as 'TestFlight Internal Only' from Xcode or Xcode Cloud can only go to internal groups, skipping Beta App Review: use this for fast QA of a network monitor before an external round. (medium confidence) [source]
- A sandboxed Mac App Store app with only unrestricted entitlements (com.apple.security.app-sandbox) may ship with no provisioning profile, but TestFlight rejects it with ITMS-90889 'missing a provisioning profile'. Apple DTS fix: add a restricted entitlement such as an empty Keychain Sharing group so Xcode embeds a profile; for non-Xcode builds embed a Mac App Store profile and add com.apple.application-identifier and com.apple.developer.team-identifier to the main app only. (medium confidence) [source]
- A build stuck at Missing Compliance waits on the encryption export question; setting ITSAppUsesNonExemptEncryption in Info.plist avoids the prompt on every upload. (low confidence) [source]
- Processing normally takes about 25 minutes on average; internal testers can install right after. Developers reported macOS builds stuck in Processing for 5+ days in Nov 2025 (Xcode 26.1) with no Apple reply; the reporter's workaround was uploading to App Store Connect another way. (medium confidence) (verified as of 2026-07-01) [source]
- External first-build review waits per Runway's tracker via ptkd: about 9.5 hours total in May 2025 and about 17 hours in July 2026 (15h39m waiting plus 1h28m in review); worst cases of multiple days reported. (low confidence) (verified as of 2026-07-01) [source]
Children
- No children recorded.