feat: unified swaps

[infiniteflower]

Description

This PR handles Unified Swaps routing, network, and token selection. It's hidden behind an env var and a feature flag, so there is no risk of accidentally exposing this feature before it's ready.

Related issues

Resolves: https://consensyssoftware.atlassian.net/browse/MMS-2341

Manual testing steps

Setup

1. Add export MM_UNIFIED_SWAPS_ENABLED="true" to .js.env
2. Terminal: source .js.env
3. Start the app up

Swaps

5. Go to Swaps (notice there's no Bridge button anymore)
6. Request a quote for a source and dest token with the same chain

Bridge

5. Go to Swaps (notice there's no Bridge button anymore)
6. Request a quote for a source and dest token with a different chain

Feature flags

1. Add export MM_UNIFIED_SWAPS_ENABLED="false" to .js.env
2. Terminal: source .js.env
3. Start the app up
4. You should see 2 buttons for Swap and Bridge
5. Swap btn should take you to Legacy Swaps
6. Bridge btn should take you to Bridge

Screenshots/Recordings

Before

After

Bridge

Screen.Recording.2025-06-19.at.5.54.00.PM.mov

Swap

Screen.Recording.2025-06-19.at.5.46.23.PM.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.

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 2c51102
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/1eeca6ff-6b13-4dea-bc57-7837a1c861db

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

Tip

• Check the documentation if you have any doubts on how to understand the failure on bitrise

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: b01cd90
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/fe628443-c6f5-40f8-8c2f-0b1d129c80c3

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

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: dfd143b
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/2f897550-3f66-4efc-8556-e78125657899

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

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 6103316
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/356ca19c-9476-4b2c-a9b3-5b6428240236

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

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 4ab5eac
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/df1d5ad4-33fd-4c4d-afb1-5fbef5443453

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

[cursor]

Bug: Swap Logic Fails Initial State Check

The isSwap determination logic was changed from bridgeViewMode to sourceToken?.chainId === destToken?.chainId. This new logic incorrectly classifies the initial state (when both tokens are undefined) as a swap, causing the button to display "Confirm swap". Furthermore, it broadly assumes all same-chain operations are swaps, which may not be accurate for all bridge scenarios, leading to incorrect button labels and potential user confusion.

app/components/UI/Bridge/Views/BridgeView/index.tsx#L338-L339

metamask-mobile/app/components/UI/Bridge/Views/BridgeView/index.tsx

Lines 338 to 339 in 4ab5eac

	const isSwap = sourceToken?.chainId === destToken?.chainId;

Fix in Cursor • Fix in Web

---

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

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

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

See analysis details on SonarQube Cloud

[tommasini]

Left a comment, but if I'm missing something and we do not need to address it, feel free to resolve it