Build Distribution

Upload iOS builds to Sentry for distribution to internal teams and beta testers.

Build Distribution helps you securely distribute iOS builds to your internal teams and beta testers. Streamline your distribution workflow with automated uploads from CI.

Accepted Formats: XCArchive

Upload Mechanisms: Fastlane Plugin (version 1.35.0 or higher) or Sentry CLI

The Fastlane plugin can be used to upload XCArchive or IPA builds to Sentry. On GitHub Actions, Fastlane will automatically detect your build's metadata and include it in the upload. In other Continuous Integration (CI) environments, you may need to manually set metadata values.

  1. Configure the Sentry Fastlane plugin (version 1.36.0):

    Copied
    bundle exec fastlane add_plugin fastlane-plugin-sentry
    
  2. Set up SENTRY_AUTH_TOKEN in your environment (you can generate a token here)

  3. In FastFile, add a call to sentry_upload_build after your build step:

    Fastfile
    Copied
    lane :upload_to_sentry do
       build_ios_app(
         scheme: 'YourScheme',
         configuration: 'Release',
       )
       sentry_upload_build(
         org_slug: 'your-org',
         project_slug: 'your-project',
         build_configuration: 'Release' # Adjust to your configuration
       )
    end
    
  4. After an upload has successfully processed, confirm the metadata is correct in the Sentry UI

The Fastlane plugin automatically detects all build metadata. If needed, the metadata values can be overridden by passing parameters to sentry_upload_build:

Fastfile
Copied
lane :upload_to_sentry do
  build_ios_app(
    scheme: 'YourScheme',
    configuration: 'Release',
  )
  sentry_upload_build(
    org_slug: 'your-org',
    project_slug: 'your-project',
    build_configuration: 'Release',
    # Optional metadata overrides:
    head_sha: 'abc123',
    base_sha: 'def456',
    vcs_provider: 'github',
    head_repo_name: 'organization/repository',
    base_repo_name: 'organization/repository',
    head_ref: 'feature-branch',
    base_ref: 'main',
    pr_number: '42'
  )
end

See the Fastlane repo for more information.

  1. Install the sentry-cli (version 2.58.2)

  2. Authenticate the Sentry CLI by following these steps

  3. Build your app to create an XCArchive (preferred) or IPA

  4. Invoke the following CLI command to trigger the upload:

    Copied
    sentry-cli build upload app.xcarchive \
      --org your-org \
      --project your-project \
      --build-configuration Release
    
  5. After an upload has successfully processed, confirm the metadata is correct in the Sentry UI

Once builds are uploaded to Sentry, your team members and beta testers can download them through the Sentry web interface.

  1. Open the URL printed to the console after uploading the build
  2. Click the Install button on the right side of the page

  1. Either scan the QR code from a mobile device or click the Download button to download the build directly

After downloading, you can install the build directly on your iOS device. For more information on installing enterprise apps, see Apple's documentation on installing custom apps.

We use build metadata to organize builds in the UI and ensure correct comparisons.

FieldDescription
org*Sentry organization slug
project*Sentry project slug
build-configuration*Build configuration describing how the app was built, for example Release or Debug or Release-Bazel
head-shaCurrent commit SHA
base-shaBase commit SHA (for comparisons, recommended to use the branch's merge-base)
head-repo-nameRepository name (org/repo)
pr-numberPull request number
head-refBranch or tag name
base-refBase branch name

* required field

Features such as automatically comparing the head build against the base build will only compare builds of the same build configuration. This is important to consider when setting up Size Analysis in your CI. For example, Release and Debug builds can be drastically different depending on the compiler and linker settings used during the build process. Trying to compare the two would give unexpected results.

Sometimes this is expected though, say you want to test the impact of converting your project to use Bazel (e.g. Release vs Release-Bazel). In this case, it's still possible to perform a manual comparison of builds with different build configurations.

Was this helpful?
Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").