Skip to content
← All Field Notes

TestFlight

Verify an iOS release build in TestFlight

Confirm the exact build installs, exercise the production-like user flows and record what passed before submitting to App Review.

Oleg Yakushin

Identify the build before testing

Pick the version and build number in App Store Connect and confirm the build is available to the intended tester group. Install it through TestFlight on a real device. Put the version and build number in an About or diagnostics screen so screenshots and bug reports point to the correct binary.

import Foundation

func buildLabel(for bundle: Bundle = .main) -> String {
    let version = bundle.object(
        forInfoDictionaryKey: "CFBundleShortVersionString"
    ) as? String ?? "?"
    let build = bundle.object(
        forInfoDictionaryKey: "CFBundleVersion"
    ) as? String ?? "?"
    return "\(version) (\(build))"
}

A processed upload and a tester installation are separate checkpoints. Record the device and iOS version along with the installed build. Apple’s build statuses

Exercise the paths most likely to break

  • Fresh install. Launch with a new test account, complete onboarding and reach the first useful screen. Try denying any permission the first flow depends on.
  • Upgrade. Install the previous relevant build, create representative data, then update in place. Verify existing data opens and the main action still works.
  • Services. Check that authentication, API calls and universal links reach the intended environment. Toggle connectivity and confirm the app shows a recoverable state.
  • Paid access. Run purchase and restore on the installed build when applicable. TestFlight purchases use Sandbox. Record each outcome separately. StoreKit 2 subscription testing
  • Release-only behaviour. Check the flows that depend on signing, capabilities or build configuration, such as push notifications, associated domains or background work.

Make the release decision from the evidence

Keep one row per check with the build, device, expected behaviour, actual outcome and any issue link. Mark checks that do not apply explicitly. If a fix changes the binary, install the replacement build and rerun the affected flow plus the launch smoke test.

Before submitting, compare the verified build number with the one selected for App Review. After publication, confirm the public listing and run a smoke test from an App Store installation. App Store launch checklist