feat: add detected tokens automatically

[sahar-fehri]

Description

Now that we have most users autodetect tokens, we can make the UX even more streamlined. This PR automatically add in tokens we detect on behalf of users.

Related issues

Fixes:https://consensyssoftware.atlassian.net/browse/MMASSETS-439

Manual testing steps

1. Switch to an account that has tokens
2. Notice you no longer see the link telling you that you have tokens detected
3. Detected tokens are added automatically to your state
4. Disable token detection setting
5. Switch to an account that has tokens
6. Detected tokens are not added to state

Screenshots/Recordings

Before

After

Screen.Recording.2024-12-20.at.19.28.35.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: ddc551b
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/e888e596-0c84-41d0-94ec-a3c4d9eea862

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 failed on Bitrise! ❌❌❌

Commit hash: a6ce16e
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/e7b81b73-7a49-4ff2-8826-af28e18305c2

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 failed on Bitrise! ❌❌❌

Commit hash: 013fdfd
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/d16095d0-bbe9-4512-a38b-c4797efc77f8

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: 20aa789
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/538fa771-7e1c-4d29-8039-a98571bb8ce8

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

See analysis details on SonarQube Cloud