Description

RC and manual iOS builds were only uploaded to TestFlight internally (distributed to Apple internal testers only). This change enables external distribution to the MetaMask BETA & Release Candidates TestFlight group automatically for all RC build paths.

Changes:

• runway-rc-builds.yml (Runway manual RC trigger): passes distribute_external: true to upload-to-testflight.yml so the resulting IPA is distributed to external testers immediately after upload.
• auto-rc-ota-build-core.yml (reusable core for auto RC): adds a distribute_external input (default false to keep the interface safe for other callers) and threads it through to the inner upload-ios-testflight job.
• build-rc-auto.yml (auto RC on release/* push): passes distribute_external: true into auto-rc-ota-build-core.yml for the iOS build job.
• build-and-upload-to-testflight.yml (manual build + upload workflow): flips the distribute_external default to true in both the workflow_call and workflow_dispatch input blocks. The testflight_group was already defaulting to MetaMask BETA & Release Candidates.

Changelog

CHANGELOG entry: null

Related issues

Fixes:

Manual testing steps

N/A

Screenshots/Recordings

Before

N/A

After

N/A

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I've included tests if applicable
• I've documented my code using JSDoc format if applicable
• I've applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Performance checks (if applicable)

• I've tested on Android
  • Ideally on a mid-range device; emulator is acceptable
• I've tested with a power user scenario
  • Use these power-user SRPs to import wallets with many accounts and tokens
• I've instrumented key operations with Sentry traces for production performance metrics
  • See trace() for usage and addToken for an example

For performance guidelines and tooling, see the Performance Guide.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

Made with Cursor