fix: update token balances on pull tokenlist pull down

[sahar-fehri]

Description

PR to add updating balances as part of pulling down on the tokenList

Related issues

Fixes:

Manual testing steps

1. Make a swap between any 2 tokens
2. Go back to home page and notice your balance is not updated for the two tokens.
3. Pull down on the tokenList
4. Your balances should now be refreshed

Screenshots/Recordings

Before

After

Screen.Recording.2025-01-27.at.21.16.09.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: 6481a7a
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/6c3470f5-d93d-4ed4-b7b9-75bf7bea0aa4

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

[gambinish]

This works as expected. I left a comment on your thread about something that I think we should keep in mind.

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: ef7f392
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/dccb33fb-a8ac-4a06-a230-78bd61390130

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

See analysis details on SonarQube Cloud