Guide

How to submit a build for TestFlight Beta App Review

Jul 19, 2026 Submit a TestFlight build for Beta App Review: when it is required, what Apple checks, What to Test notes, and how Helm keeps external betas unblocked.

External TestFlight distribution usually waits on Beta App Review. Internal testers on your App Store Connect team can often start sooner. External groups cannot until the build clears beta review (or reuses a prior clearance when Apple allows it). This guide walks the submission path and how Helm’s TestFlight tools keep builds, groups, and notes ready.

Beta App Review vs App Review

Beta App Review is the lighter gate for TestFlight external testing. Apple still checks that the build launches, that required metadata makes sense, and that you are not distributing something obviously non-compliant.

App Review is the full storefront review for a version you want Ready for Sale.

Do not treat beta clearance as a guarantee for the App Store submission. Still, a clean beta cycle surfaces crashes and missing review materials early. See submit an app for review when you are ready for the storefront path.

When you need to submit

Submit for Beta App Review when:

You invite external testers to a new build that needs clearance
Compliance or significant capability changes require a fresh look
Apple indicates the build is waiting on beta review before external distribution

Internal-only testing may not need this step. Confirm group type before you promise a Friday external drop.

Prep before you click submit

Build processed. Wait until App Store Connect finishes processing. Missing export compliance answers will block you; see export compliance and encryption.
What to Test filled. Reviewers and humans both benefit. Follow write What to Test so the first session is focused.
Demo access ready. If the app requires a login, provide a working account in beta review information.
Groups decided. Know which external groups get this build after clearance.
Contact info current. Stale review contacts slow everything when Apple has a question.

Submission steps

In App Store Connect or Helm:

Select the processed build.
Complete any missing compliance or beta review fields.
Attach or confirm What to Test for the groups that will receive the build.
Submit for Beta App Review.
Watch status until the build is cleared for external testing.
Enable the build for your external groups and send invites or public links.

Do not invite a wave of external testers while status is still waiting. You will create support noise for a build nobody can install yet.

What slows beta review down

Broken login or missing demo credentials
Crashes on launch
Placeholder What to Test (“test”, “asdf”)
Incomplete export compliance
Features that require special entitlements without explanation

Fix the binary or the review package, then submit again. Re-submitting the same broken package wastes a cycle.

After clearance

Add the build to external groups
Refresh invites or public links as needed
Update What to Test if the build focus changed since draft
Monitor TestFlight feedback and crashes before you scale the tester pool

When the beta is solid, reuse what you learned for App Review notes and What’s New.

How Helm helps

Helm shows builds with expiration and compliance context, keeps groups and What to Test visible, and helps you invite testers without reconstructing the story in a browser tab. External betas stall less often when compliance, notes, and group targeting live next to the build. Feedback can flow into GitHub or Linear when you connect those integrations; busy teams often prefer Helm Pro so integration limits do not interrupt a heavy beta week.

Checklist

Build processed and compliance answered
What to Test written for this build
Demo account verified today
External groups named and ready
Submit completed, status monitored
Invites go out only after clearance