Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: multi cherry pick 7.35.0 #12269

Merged
merged 5 commits into from
Nov 13, 2024

Conversation

kylanhurt
Copy link
Contributor

@kylanhurt kylanhurt commented Nov 13, 2024

Description

Related issues

Fixes:

Manual testing steps

  1. Go to this page...

Screenshots/Recordings

Before

After

Pre-merge author checklist

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.

tommasini and others added 2 commits November 12, 2024 15:22
This PR removes navigation instrumentation of Sentry configuration.

The reason why we are removing navigation instrumentation is that
transaction.durations were not showing accurate values, since if a user
backgrounded the app and opened, that time would be added to the
transaction.duration, creating issues on our measurements.

Fixes: #12165

1. Go to this page...
2.
3.

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

<!-- [screenshots/recordings] -->

<!-- [screenshots/recordings] -->

- [x] 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).
- [x] I've completed the PR template to the best of my ability
- [x] I’ve included tests if applicable
- [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] 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.

- [x] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [x] 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: Aslau Mario-Daniel <[email protected]>
Current Issue: The `AccountSelectorList` subscribed to the `privacyMode`
selector at a component level. It had the unintended consequence of
hiding the balance when choosing an account during the send flow.

Solution: Passing it as a param to allow fine tuned control over hidden
balances in the `AccountSelector` component

Follow Fix:
[#3240](MetaMask/MetaMask-planning#3420)

1. Click on the privacy mode button on the home screen
2. Click on the account selector to verify your balance is hidden
3. Click on the send flow and attempt to switch accounts - confirm that
your balance isn't hidden here while pivacy mode is enabled

| Before  | After  |
|:---:|:---:|

|![before](https://github.com/user-attachments/assets/ee0c13bb-c636-4a1a-9b87-64f1da16eca4)|![after](https://github.com/user-attachments/assets/3606b2e9-d853-4a84-8177-b7437487ae21)|

<!-- [screenshots/recordings] -->

<!-- [screenshots/recordings] -->

- [ ] 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.

- [ ] 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.
Copy link
Contributor

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.

@sethkfman sethkfman added the Run Smoke E2E Triggers smoke e2e on Bitrise label Nov 13, 2024
Copy link
Contributor

github-actions bot commented Nov 13, 2024

https://bitrise.io/ Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: d905d8a
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/5b340046-2b00-407f-aa4a-bf4d5fa121cc

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

@sethkfman sethkfman marked this pull request as ready for review November 13, 2024 00:11
@sethkfman sethkfman requested review from a team as code owners November 13, 2024 00:11
Copy link
Contributor

@sethkfman sethkfman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@kylanhurt kylanhurt added Run Smoke E2E Triggers smoke e2e on Bitrise and removed Run Smoke E2E Triggers smoke e2e on Bitrise labels Nov 13, 2024
Copy link
Contributor

https://bitrise.io/ Bitrise

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

Commit hash: 03359e8
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/6b69071f-8921-4794-b3d3-0b88f4a3bd06

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

@kylanhurt kylanhurt added Run Smoke E2E Triggers smoke e2e on Bitrise and removed Run Smoke E2E Triggers smoke e2e on Bitrise labels Nov 13, 2024
Copy link
Contributor

github-actions bot commented Nov 13, 2024

https://bitrise.io/ Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: a0b1472
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/747e1a18-e850-44b7-b847-1d1e274a54da

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

Copy link

sonarcloud bot commented Nov 13, 2024

@sethkfman sethkfman merged commit 478107e into release/7.35.0 Nov 13, 2024
35 of 38 checks passed
@sethkfman sethkfman deleted the kylan/multi-cherry-pick-7.35.0 branch November 13, 2024 00:55
@github-actions github-actions bot locked and limited conversation to collaborators Nov 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Run Smoke E2E Triggers smoke e2e on Bitrise team-mobile-platform
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants