You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<!--
Please submit this PR as a draft initially.
Do not mark it as "Ready for review" until the template has been
completely filled out, and PR status checks have passed at least once.
-->
## **Description**
<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->
<img width="1052" alt="Screenshot 2024-10-11 at 20 29 04"
src="https://github.com/user-attachments/assets/a5680804-7bc8-45c4-a27a-d790bd5f9a5d">
<img width="766" alt="Screenshot 2024-10-16 at 00 01 02"
src="https://github.com/user-attachments/assets/aa4689f2-9ce0-4dc7-9b99-f24fd4db1b78">
<img width="699" alt="Screenshot 2024-10-15 at 17 57 12"
src="https://github.com/user-attachments/assets/dc31684a-4dea-4f26-8b18-c5497679a0ce">
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: MetaMask/mobile-planning#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.
<img width="1560" alt="Screenshot 2024-10-22 at 05 02 54"
src="https://github.com/user-attachments/assets/4abc259f-be70-4f74-af2b-7ece47343678">
(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...
2.
3.
## **Screenshots/Recordings**
<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->
### **Before**
<!-- [screenshots/recordings] -->
### **After**
<!-- [screenshots/recordings] -->
## **Pre-merge author checklist**
- [ ] I’ve followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [ ] 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](https://jsdoc.app/) format
if applicable
- [ ] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
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.
---------
Co-authored-by: tommasini <tommasini15@gmail.com>
Co-authored-by: tommasini <46944231+tommasini@users.noreply.github.com>
0 commit comments