fix: Updated useComponentSize to re-render on change

[brianacnguyen]

Description

This PR updated the useComponentSize hook to re-render on change.

Related issues

Fixes: #15187

Manual testing steps

1. Go to browser
2. Connect to dapp
3. Check network badge

Screenshots/Recordings

Before

Simulator.Screen.Recording.-.iPhone.15.Pro.Max.-.2025-05-06.at.09.29.13.mp4

After

Simulator.Screen.Recording.-.iPhone.15.Pro.Max.-.2025-05-06.at.09.29.55.mp4

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: a451e4a
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/3d1e4a31-e688-4a23-a46d-55820c011a0b

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

[EtherWizard33]

LGTM!

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 1944f99
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/d2241f73-ded2-4158-acc3-8e7838f18215

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: f1cbb6b
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/b8220c2a-3043-42a2-a383-b1b015d55229

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: 7fd8aa2
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/aa892069-9a74-484e-8abc-76a1027b8068

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