fix: add new translations

[sahar-fehri]

Description

PR that adds new translation for Portfolio View feature when the asset network is different than the selected network

Related issues

Fixes:

Manual testing steps

1. Click on "All Networks"
2. Click on a token that is on a network different than the network you are currently on
3. Scroll down and you should see "Please switch network to view transactions"

Screenshots/Recordings

Before

After

Screen.Recording.2024-12-12.at.11.49.46.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 passed on Bitrise! ✅✅✅

Commit hash: c2d8c6a
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/c6bcfd30-d9e7-405f-9303-ee12d5726d1b

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

[tommasini]

It seems we have conflicts! Can we also have screenshot of the component and scenario where the translation is used?

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 7602183
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/2917c855-1dd2-41d0-af5f-33e346aac699

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
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud