feat: 1940 add custom sentry span

[MarioAslau]

Description

This task is for adding custom spans to track activities that happen between app start and wallet UI load. The screenshot below is an example of a trace for Wallet UI load that takes about a minute to load. During that time, we can see a large gap between app start spans and the initial http requests.

The goal here is to isolate these areas and track them with custom spans. Once implemented, we can expect to see the custom spans appearing within the gap, which would inform us of the areas to optimize

Issue: https://github.com/MetaMask/mobile-planning/issues/1940

Technical Details

• Added custom span for when the Login screen is mounted to when the login button is tapped
• Added span for when the login button is tapped to when the wallet view is mounted
• Added custom span for Engine initialization process
• Added custom span for Store creation
• Added custom span Storage rehydration
• Added custom span fro Create New Wallet to Choose Password
• Added custom span for Biometrics authentication

##Engine Initialisation Bug##

While initally the engine init trace was preceded by an await, which would allow the grouping of all the calls that happen inside Engine to be under the Engine Initialisation process, that would cause a crash of the application in Production on Android.

As a temporary fix until the issue that happens within Engine is found and fixed, the only noticeable difference will take place as bellow. API calls from within the Engine Initialization, will not all be grouped within the same span.

(left without await, right with await)

Bitrise Build: https://app.bitrise.io/build/6ee0b625-d8b9-4d95-9fcc-a1d624202736?tab=artifacts

Related issues

Fixes:

Manual testing steps

1. Go to this page...

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: f6adb4c
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/53fd2edf-205b-4ee3-8cf1-b087c25df4ea

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 passed on Bitrise! ✅✅✅

Commit hash: b69ed01
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/214d60e9-6c94-46a7-8e2a-068989ee0755

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: a7c2540
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/9284d684-99cd-448d-924f-b9fbcb86d077

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: 1a93300
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/4a264b9c-c7bd-4c1e-a966-19f9d0adf482

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 passed on Bitrise! ✅✅✅

Commit hash: 9f00e41
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/94e08554-dc69-4db0-8303-9d0081d50169

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

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

See analysis details on SonarCloud