Build Mobile Apps using Codex/Ship It
Lesson 2 / 4 · 10 min
Walkthrough

TestFlight and Internal Testing

Getting builds in front of real testers in under a day.

TestFlight on iOS, Internal Testing on Play Console. Both let you ship a build to up to 100 testers without store review. Both want a few metadata fields filled in before they'll accept a build. Get this configured once and subsequent uploads are minutes.

Steps · 0 / 4 done

  1. App Store Connect: register the app

    Bundle ID, name, default language. The bundle ID must match your app.json identifier exactly.

    // app.json
{
  "expo": {
    "ios": { "bundleIdentifier": "com.tipjar.app" },
    "android": { "package": "com.tipjar.app" }
  }
}
    VerifyApp listed in ASC; same identifier on both platforms is a sanity-saver.

  2. Submit to TestFlight

    EAS Submit handles the upload. After upload, Apple does an automated review (usually <30 min) before the build is testable.

    eas submit --platform ios --latest
    VerifyBuild appears in TestFlight under Builds; status flips from Processing to Ready to Test.

  3. Add testers

    External testers need the app's review approved once; internal testers (same Apple Developer team) can install immediately.

    # Add testers in App Store Connect → TestFlight → Internal Testing
    VerifyTesters receive an email with the install link.

  4. Same flow for Android Internal Testing

    Play Console → Testing → Internal testing. Upload an .aab via EAS Submit; add testers' Google accounts.

    eas submit --platform android --latest
    VerifyTesters install via the Play Store opt-in link.
Check your understanding
Q1. Why does TestFlight let you skip the full App Store review for testing?
· Tick off the 4 step(s) above.
· Score 100% on the quiz.