chore(sentry): don't report AxiosError: Network Error

[Daniel-Cross]

Description

Added a try catch around the infura calls so Sentry does not pick up an error from axois when the request fails due to poor connection.

Related issues

Fixes: This issue

Manual testing steps

• Open the app, log in, disconnect from the internet.
• • App should now handle that failure instead of the api throwing an error which is caught by Sentry.

Screenshots/Recordings

Before

After

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: 5adfb0e
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/353becf9-2242-4800-bed6-9e17cc0b06b8

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

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: cb6d002
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/560f833c-fd07-4183-9656-e70978e3ee2b

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: 5384c97
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/4552faa6-8a86-4fb9-b244-60d1eada6420

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]

Hey @Daniel-Cross could you plz provide the best way for me to recreate the buggy behavior vs fix? Also may want to run Bitrise once more as it may have flaked.

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 4604866
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/75ebe899-afc7-4512-a89a-155ec8c1119c

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

[github-actions]

Bitrise

🔄🔄🔄 pr_smoke_e2e_pipeline started on Bitrise...🔄🔄🔄

Commit hash: 856771f
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/7c322584-ca9e-4b8c-96b7-dda477fbc4a0

Note

• This comment will auto-update when build completes
• 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

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 9427fc2
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/8575267d-a021-4b55-9b1b-22067cf7dabe

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
3 New issues
0 Accepted issues

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

See analysis details on SonarCloud