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(runway): cherry-pick fix(11895): remove duplicate networks in incoming transactions settings #12096

Merged
merged 2 commits into from
Oct 30, 2024

Conversation

runway-github[bot]
Copy link
Contributor

@runway-github runway-github bot commented Oct 30, 2024

Description

We now list mainnet networks in the rpcEndpoints so the previous
logic rendering mainnet in separate functions are no longer need. Here
is the relevant
PR that
has those changes. The rpcEndpoints do not render in the right order
so filtering by Linea Mainnet and Ethereum Mainnet is needed.

Related issues

Related Issue:
#11895

Manual testing steps

  1. Go to this settings page
  2. Click on "Security & Privacy"
  3. Scroll down and toggle "Show incoming transactions" and confirm that
    it works
  4. Confirm that the duplicate mainnet networks are gone

Screenshots/Recordings

test

Before After
![Simulator Screenshot - iPhone 16 Pro Max - 2024-10-24 at 13 37
34](https://github.com/user-attachments/assets/bdf394ca-fbda-449e-baa2-c9beed0cf5fb) incoming_transactions

Before

NA

After

NA

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. 60bdb96

…ncoming transactions settings (#12016)

## **Description**

We now list `mainnet` networks in the `rpcEndpoints` so the previous
logic rendering `mainnet` in separate functions are no longer need. Here
is the relevant
[PR](https://github.com/MetaMask/metamask-mobile/pull/11705/files) that
has those changes. The `rpcEndpoints` do not render in the right order
so filtering by Linea Mainnet and Ethereum Mainnet is needed.

## **Related issues**

Related Issue:
[#11895](#11895)

## **Manual testing steps**

1. Go to this settings page
2. Click on "Security & Privacy" 
3. Scroll down and toggle "Show incoming transactions" and confirm that
it works
4. Confirm that the duplicate `mainnet` networks are gone

## **Screenshots/Recordings**

![test](https://github.com/user-attachments/assets/b0bb2424-1b38-43fc-9953-69f5fec35242)

| Before | After
|:---:|:---:|
|![Simulator Screenshot - iPhone 16 Pro Max - 2024-10-24 at 13 37
34](https://github.com/user-attachments/assets/bdf394ca-fbda-449e-baa2-c9beed0cf5fb)|![incoming_transactions](https://github.com/user-attachments/assets/eaa4c27b-91e8-43d7-bb55-7860f6447e1e)|

### **Before**

NA

### **After**

NA

## **Pre-merge author checklist**

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

## **Pre-merge reviewer checklist**

- [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.
@runway-github runway-github bot requested a review from a team as a code owner October 30, 2024 00:23
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.

@NicolasMassart NicolasMassart added the Run Smoke E2E Triggers smoke e2e on Bitrise label Oct 30, 2024
Copy link
Contributor

github-actions bot commented Oct 30, 2024

https://bitrise.io/ Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 2312a48
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/d95bf73b-2650-4fe8-8ee8-ac5eccc22bf2

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

@NicolasMassart NicolasMassart merged commit ffea898 into release/7.34.0 Oct 30, 2024
35 of 36 checks passed
@NicolasMassart NicolasMassart deleted the runway-cherry-pick-7.34.0-1730247824 branch October 30, 2024 13:52
@github-actions github-actions bot locked and limited conversation to collaborators Oct 30, 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-runway-bot
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants