Bitrise Immerse

Pipeline Stages

Testing Stage

Uploading your build to TestFlight for beta testing.

The Testing stage is the second step in the version pipeline. Here, you upload your selected build artifact to TestFlight for beta testing before moving on to approvals.

What This Stage Does

This stage uploads your release candidate to Apple’s TestFlight platform, where beta testers can install and test the build before it’s submitted for App Store review.

Prerequisites

  • A build artifact must be selected in the Release Candidate stage
  • Your App Store Connect configuration must be set up (see Settings)

Upload to TestFlight

The Testing stage moves through two states:

  1. Review the upload state

    When you first reach this stage, you’ll see:

    • An info banner: “Upload the release candidate first to start beta testing”
    • The selected artifact details (filename, version, build number)
    • An “Upload Version” button

    testing-ready-upload

    The Testing stage in Ready to Upload state

  2. Upload the build

    Click “Upload Version” to upload the build to TestFlight.

  3. Confirm upload success

    After a successful upload, the stage shows:

    • A success banner: “Ready for Testing”
    • The uploaded artifact details
    • A note: “Manage in TestFlight or continue to Approvals”

    testing-ready-for-testing

    The Testing stage showing Ready for Testing status

Currently, auto-upload is on by default and this stage will be completed automatically.

At this point, the stage is complete and the Approvals stage becomes available.

Managing Beta Testing

Once the build is uploaded to TestFlight:

  • Beta testers can install the build through the TestFlight app on their devices
  • Test feedback is managed directly in App Store Connect / TestFlight — the Rollouts module doesn’t track individual test results
  • You can continue to the Approvals stage while testing is ongoing
You don’t need to wait for all beta testing to finish before moving to the Approvals stage. The approval process can run in parallel with ongoing beta testing.

Troubleshooting

Upload fails:

  • Verify your App Store Connect configuration in Settings (Bundle ID, Team ID, etc.)
  • Ensure the build artifact is a valid, signed .ipa file
  • Check that your App Store Connect account has the necessary permissions

Build doesn’t appear in TestFlight after upload:

  • TestFlight processing can take several minutes after upload
  • Check App Store Connect for any processing errors (e.g., missing compliance information, invalid provisioning profile)

What’s Next