fix: poll only popular network

[salimtb]

Description

To reduce the impact of showing assets across all networks, which can be unbounded, this PR scopes the portfolio view to the 9 popular networks built into metamask.

Related issues

Fixes: MetaMask/metamask-extension#29055

Manual testing steps

1. On popular networks:

• The token filter should allow switching between popular networks and current network
• The filter should work as described
• RPC requests in the background should only hit the popular networks

2. On other networks

• The token filter should become disabled and scoped to the current network
• RPC requests in the background should only hit the current network

Screenshots/Recordings

Before

After

account-trcker.mov

currencyRate.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: f22b797
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/c3ee9b07-8f0f-45a1-8152-3e0875e14a1d

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]

Can we have a recording of what changed?

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: a4c25ef
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/198b70b8-d46f-495a-b703-cf67f620aec5

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

[salimtb]

One bug I notice.

• Start on a popular network
• With the filter set to 'current network'
• Switch to a non-popular network
• Switch back to the popular network

It keeps showing tokens from the non-popular network.

Screen.Recording.2024-12-13.at.9.54.43.AM.mov

@bergeron fixed 3adb9de

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: bcad469
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/497f2346-4e3b-42f9-8b6a-7a51036bd038

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

[salimtb]

Now when switching networks while the filter is on 'current network', the tokens do not update to the new network.

Screen.Recording.2024-12-13.at.12.11.36.PM.mov

@bergeron bug fixed + flaky e2e test addressed , i should have a green build now

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud