iOS app beta testing with TestFlight

TestFlight is how almost every iOS app gets into beta testers' hands before the App Store. This guide explains how TestFlight testing works, what to check on iPhone that differs from Android, and how to run an AI beta test on a real iPhone from an uploaded .ipa build.

Who it’s for

  • iOS developers about to send a build to external TestFlight testers
  • Cross-platform teams checking the iPhone build of a Flutter or React Native app
  • Founders preparing an App Store launch
  • Teams testing a major update before submitting for review

Updated 2026-10-19.

What iOS app beta testing involves

iOS app beta testing is the stage where you give a pre-release build of your iPhone or iPad app to beta testers, find what breaks, and fix it before the App Store release. Most teams run their iOS beta test through TestFlight, Apple's official beta distribution service, because testers install builds the same way they would install a real app.

A good iOS beta does two things: it catches crashes and broken flows across iPhone models and iOS versions, and it gives you a preview of what App Store review and real users will run into.

How TestFlight beta testing works

  • Internal testers are members of your App Store Connect team, up to 100 people. They can install builds as soon as processing finishes, without a beta review.
  • External testers are anyone you invite by email or through a public link, up to 10,000. The first build for external testing goes through Beta App Review before external testers can install it; later builds of the same version usually move faster.
  • Testers install the free TestFlight app, accept the invite and install your build. Each build expires after 90 days, so plan longer betas around new builds.
  • Testers can send feedback with screenshots directly from the TestFlight app, and crash reports appear in App Store Connect.
  • You can organize external testers into groups, for example a small trusted group first and a larger public-link group later.

How to run an iOS beta test

  1. Archive and upload the build, then add release notes that tell testers what changed and what to focus on.
  2. Prepare a demo account with realistic data, and use sandbox accounts or StoreKit testing for in-app purchases.
  3. Send the build to internal testers and run a full pass over every screen and core flow.
  4. Fix crashes and blockers, upload a new build, and confirm the fixes.
  5. Submit the build for Beta App Review and invite a small external group with a short brief.
  6. Ask every tester to report with iPhone model, iOS version and build number.
  7. Review TestFlight feedback and crash reports at a fixed rhythm, for example twice a week.
  8. Widen to a public link when the small group stops finding serious issues, then prepare the App Store submission.

iOS beta testing checklist

Layout and display

  • Content and buttons stay clear of the notch or Dynamic Island, the home indicator and rounded corners.
  • Small screens (iPhone SE size) and large screens (Pro Max size); iPad if you support it.
  • Dynamic Type at the largest accessibility sizes does not cut off labels or overlap buttons.
  • Dark mode on every screen, including web views and images with transparent backgrounds.

Gestures and navigation

  • Swipe back from the left edge works on every pushed screen, including custom navigation.
  • Pull to refresh and swipe to dismiss sheets behave as expected and do not lose unsaved input.

Permissions and privacy

  • Notification, camera, photos, location and tracking prompts appear in context, with purpose strings that explain why.
  • The app still works after each permission is denied, and explains how to enable it in Settings.

Sign-in and accounts

  • Sign in with Apple, including the "hide my email" relay address.
  • Email and one-time code autofill from the keyboard.
  • Logging out and back in, deleting an account if you offer it (Apple requires in-app deletion for apps with account creation).

Lifecycle and purchases

  • Backgrounding, returning from Safari or a payment sheet, low power mode and an incoming call.
  • In-app purchases and subscriptions only with sandbox accounts or StoreKit testing, never real money.
  • Restoring purchases on a fresh install.

Example iOS bug report

Title: Swipe-back gesture disabled on Settings > Profile
Environment: iPhone 13, iOS 18.0, build 2.1.0 (87) via TestFlight
Severity: Medium (navigation works with the back button, but users get stuck)

Steps to reproduce:
1. Log in with the demo account.
2. Open the Settings tab, then tap "Profile".
3. Swipe right from the left edge of the screen.

Expected: The Profile screen slides away and Settings is shown.
Actual: Nothing happens. Only the "<" button in the top bar goes back.
Swipe-back works on every other pushed screen.

Evidence: screen recording of steps 2-3.
Notes: Profile uses a custom navigation bar; likely the gesture recognizer
is not re-enabled after hiding the system bar.

Preparing for App Store review

Beta testing is also your chance to catch things that commonly cause review problems:

  • Broken links to your privacy policy or support page.
  • Sign-in required with no working demo account for the reviewer.
  • Placeholder text, test data or "coming soon" screens.
  • Crashes on launch on a clean install.
  • Features that do not work as described in the listing.

Give reviewers a working demo login, just as you would give your beta testers one.

Common iOS beta testing mistakes

  • Testing only on the newest iPhone and the latest iOS version.
  • Skipping the clean-install path because the team always upgrades from an older build.
  • Letting builds expire mid-beta, so testers suddenly cannot open the app.
  • Sending a build to external testers before internal testing catches the obvious crashes.
  • Testing purchases with a real Apple ID instead of a sandbox account.

How to prioritize what to fix

  1. Crashes, especially on launch or in core flows.
  2. Anything that would fail App Store review or blocks signup, login or purchase.
  3. Data loss on update or after backgrounding.
  4. Layout bugs on common iPhone sizes, Dynamic Type and dark mode.
  5. Copy, polish and feature requests, collected for later versions.

Manual iOS testing vs an AI beta tester

Human beta testers on different iPhone models remain essential. They notice how the app feels, use it on weak or offline networks, rely on the camera, location, push notifications and sensors, and tell you whether they would keep or pay for it. Those are real-world conditions and opinions an AI tester cannot reproduce.

An AI beta tester like betatest.ing handles the methodical pass. You upload your .ipa, it installs the build on real iPhones, walks through every screen and core flow, and files bug reports with steps to reproduce, severity, annotated screenshots and screen recordings. It can repeat the same pass on every build or on a schedule as a regression test, and it never makes real purchases. Test logins are encrypted and never shown to the AI.

Run the AI pass on each new build before it goes to external testers, so your human testers spend their time on real-world feedback instead of the obvious bugs.

The test task

What you send your AI beta tester. It works out the steps and tests like a real user.

Beta test my iOS app (the uploaded .ipa build) on a real iPhone. It is [WHAT THE APP DOES AND WHO IT IS FOR]. Install the build, go through first launch, onboarding and every permission prompt (deny one and check the app still explains what to do). Sign in with the saved test login, then use each main screen and flow. Check that nothing sits under the notch, Dynamic Island or home indicator, that swipe back works on every pushed screen, that sheets can be dismissed, and that the keyboard never hides the field being typed in. Look for cut-off text, dark mode problems and dead buttons. Check the links to the privacy policy and support pages. Do not make any purchases. Log each bug as a finding with steps to reproduce and an annotated screenshot, record any flow that breaks, and end with a report that scores onboarding, navigation, layout and App Store readiness with the top fixes.

Fill in your details

Here, or later in the chat with your tester.

  • [WHAT THE APP DOES AND WHO IT IS FOR] One sentence about the app

What the AI beta tester checks

  • Install of the uploaded build and first launch
  • Permission prompts and behavior after denial
  • Safe areas: notch, Dynamic Island, home indicator
  • Swipe back, sheet dismissal and navigation
  • Keyboard overlap and input types
  • Dark mode and cut-off text
  • Privacy policy and support links for App Store review
  • Every main flow with the test login

What you get

  • Bug reports with steps to reproduce and the screen
  • Annotated iPhone screenshots
  • Recordings of broken flows
  • A report with scores, App Store readiness notes and top fixes

How to run it with betatest.ing

  1. Add your app as a project and upload an .ipa exported for ad-hoc, development or enterprise distribution.
  2. Add a demo login the tester (and later App Review) can use.
  3. Send the iOS beta test task; the tester runs the app on a phone and logs findings.
  4. Fix the issues, upload a new build and invite external TestFlight testers.

Tips

  • Export an ad-hoc or development .ipa for the AI tester; TestFlight and App Store builds cannot be installed on its devices.
  • Write "What to Test" notes for each build in App Store Connect; testers read them.
  • Keep a demo account ready for both testers and App Store review.
  • Plan around TestFlight build expiry for long betas.

iOS app beta testing: FAQ

What is TestFlight?

TestFlight is Apple's beta testing service. You upload a build to App Store Connect and invite internal or external testers, who install it with the TestFlight app and can send feedback and crash reports.

Do TestFlight builds need review?

Builds for internal testers do not. The first build of a version for external testers goes through a TestFlight beta review by Apple.

Can an AI beta tester test my iOS app?

Yes. Add the app as a project and upload an .ipa exported for ad-hoc, development or enterprise distribution; it installs the build on a real iPhone, tests each flow and files bug reports with screenshots and recordings. It cannot install from TestFlight or the App Store, so keep TestFlight for your human beta testers.

How many TestFlight testers can I have?

Apple allows a small internal team and up to 10,000 external testers; check App Store Connect for current limits.

Will it test in-app purchases?

Only with sandbox or StoreKit test setups. It never makes real purchases.

How long does TestFlight Beta App Review take?

It is usually faster than a full App Store review, but Apple does not guarantee a time, so plan for it to take up to a day or more. Only the first build for external testing of a version needs the review; internal testers can install as soon as a build finishes processing. Upload early so the review does not hold up your beta.

How much does iOS beta testing cost?

TestFlight itself is free with an Apple Developer Program membership. The real costs are the time to triage and fix reports, devices to test on, and any tester incentives or paid testing services. An AI beta tester can cut down the repetitive work of re-testing every build.

Do I need a demo account for iOS beta testing?

If your app requires sign-in, yes. Beta testers, the AI tester and Apple's reviewers all need a working account with realistic data, otherwise they stop at the login screen. Use a dedicated test account, never a real customer's.

Related beta testing guides

  • Mobile app beta testing — Mobile apps reach testers through store testing tracks, run on hardware you do not control, and get interrupted constantly. This guide covers how to distribute a mobile beta, what to test that is specific to phones, and how an AI beta tester fits alongside your human testers.
  • Android app beta testing — Android beta testing means getting a test build onto many different phones and finding what breaks before the public release. Here is how Google Play testing tracks work, what to test that is specific to Android, and a task your AI beta tester can run from your uploaded build or Play link.
  • TestFlight beta testing — TestFlight is Apple's beta distribution service and the standard way to get iOS, iPadOS, macOS, watchOS, tvOS and visionOS builds to testers before the App Store. This guide walks through internal and external testers, groups and public links, Beta App Review, build expiry, how feedback and crash reports arrive, and how to pair TestFlight with an AI beta tester so your human testers meet a stable build.
  • Find iOS beta testers — TestFlight makes distributing an iOS beta easy; finding people who install it and keep reporting is the hard part. This guide covers how TestFlight public links and limits work, where to recruit iPhone testers, what to offer them, how to keep them engaged across 90-day build cycles, and how an AI beta tester fits in before the first invite goes out.
  • App Store rejection reasons — Most App Store rejections are not about taste. They cite a small set of guidelines: the app crashed, a login had no demo account, a purchase bypassed in-app purchase, a social login lacked Sign in with Apple, or there was no way to delete an account. This guide lists the common rejection reasons by guideline number, what reviewers actually check, and a review-readiness task your AI beta tester can run on the build before you press Submit.
  • Free tool: Beta testing checklist generator — An interactive checklist for websites, SaaS, mobile apps, stores and extensions. Progress saved, Markdown export.

More in by product