feat: Add the expo flask pipeline

[ixf]

Description

This creates a Bitrise pipeline for creating flask builds.

Changes made:

• build:ios:flask:local and build:android:flask:local is used by Bitrise for generating Flask Expo prebuild in CI
• Added Flask development provisioning profile
• generateIosBinary selects the correct plist

Related issues

Fixes: #15563

Manual testing steps

1. Go to bitrise, make a new build from this branch using expo_flask_pipeline
2. Verify that there are 4 artifacts - main .apk, test .apk, .ipa and .app
3. Install .apk on Android emulator, verify that the Flask target is installed
4. Install .ipa and .app on iOS simulator and device, verify that the Flask target is installed
5. yarn watch and run the app

For reference here's the latest bitrise build of this pipeline:
https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/be69d047-60ea-400d-8a39-4153f0d85f84

Screenshots/Recordings

After

Installing .ipa and .apk

flask-installs.mov

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.

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.

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[ixf]

I have read the CLA Document and I hereby sign the CLA

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.97%. Comparing base (f6f4594) to head (c6505c4).
Report is 51 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #15792      +/-   ##
==========================================
+ Coverage   69.58%   69.97%   +0.38%     
==========================================
  Files        2473     2530      +57     
  Lines       53007    54023    +1016     
  Branches     8063     8309     +246     
==========================================
+ Hits        36886    37800     +914     
- Misses      13752    13784      +32     
- Partials     2369     2439      +70     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Cal-L]

left a comment

[github-actions]

Bitrise

🔄🔄🔄 pr_smoke_e2e_pipeline started on Bitrise...🔄🔄🔄

Commit hash: 58d1a04
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/03f07dc8-8917-432b-a8d9-4000ed607ceb

Note

• This comment will auto-update when build completes
• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

[Cal-L]

Added comments for context

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 1f482bb
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/4b2ada34-0635-4f5c-8ecb-c204644b71c9

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

[Cal-L]

E2E passed already, just resolved conflict from main

[cursor]

Bug: Android Build Script Issues

The scripts/build.sh script introduces two issues in Android builds:

1. The buildAndroidDevBuild function no longer sources environment variables from .android.env when PRE_RELEASE is true, as the sourcing logic in prebuild_android is now conditional on PRE_RELEASE being false. This can lead to build failures.
2. Both buildAndroidDevBuild and the newly added buildAndroidFlaskLocal functions are missing the -DtestBuildType=debug parameter when building their respective AndroidTest APKs (assembleProdDebugAndroidTest and assembleFlaskDebugAndroidTest). This omission breaks consistency with other test builds and may cause build or test failures.

scripts/build.sh#L286-L299

metamask-mobile/scripts/build.sh

Lines 286 to 299 in 5ba996b

	buildAndroidDevBuild(){
	prebuild_android
	# Generate both APK (for development) and test APK (for E2E testing)
	cd android && ./gradlew assembleProdDebug assembleProdDebugAndroidTest --build-cache --parallel && cd ..
	}
	# Builds the Flask APK for local development
	buildAndroidFlaskLocal(){
	prebuild_android
	# Generate both APK (for development) and test APK (for E2E testing)
	cd android && ./gradlew assembleFlaskDebug assembleFlaskDebugAndroidTest --build-cache --parallel && cd ..

Fix in Cursor • Fix in Web

---

Bug: Build Function Directory Inconsistency

The buildIosFlaskLocal function changes to the ios directory but does not return, which is inconsistent with other build functions and can cause subsequent operations to run from the wrong directory. Additionally, the remapFlaskEnvVariables call was removed from buildIosFlaskRelease to rely on a new global call for Flask modes. This creates an inconsistency where Android Flask release builds may still have a redundant remapFlaskEnvVariables call, leading to it being executed twice for Android but only once for iOS, potentially causing unexpected environment variable behavior.

scripts/build.sh#L460-L471

metamask-mobile/scripts/build.sh

Lines 460 to 471 in 5ba996b

	buildIosFlaskLocal() {
	prebuild_ios
	# Go to ios directory
	cd ios
	# Generate a Flask debug .ipa for local
	generateIosBinary "MetaMask-Flask" "Debug"
	}
	buildIosFlaskRelease(){
	prebuild_ios

Fix in Cursor • Fix in Web

---

Was this report helpful? Give feedback by reacting with 👍 or 👎

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Cal-L]

All cursor comments are expected. The Expo prebuild configuration is most up-to-date. Other configurations will be updated in follow up PRs