fix: cp-7.46.0 Temporarily disable send flow via token details on non-evm networks

[gambinish]

Description

It looks like Send flow via the Token Details screen is not supported as of 7.46. There is another PR opened that begins to implement this: #15095

This PR can be used as a cherry-pick in the meantime into 7.46 to disable send flow via tokens details for non-evm networks.

Worth mentioning that users can still enter the send flow via the main tokens screen.

Related issues

Fixes:

Manual testing steps

1. Go to this page...

Screenshots/Recordings

Screen.Recording.2025-05-03.at.4.23.24.AM.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: 53853e9
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/eead4559-5896-4ea6-80d0-4a37695963d2

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: 7eec7b3
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/c20df0a0-4482-40d0-bda0-baa48e65a5ae

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud