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

fix: patch for token rates controller with coin gecko endpoint #7991

Closed

Commits on Nov 18, 2023

  1. 7.12.0

    metamaskbot committed Nov 18, 2023
    Configuration menu
    Copy the full SHA
    2a3df54 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    922b8dd View commit details
    Browse the repository at this point in the history

Commits on Nov 21, 2023

  1. chore: cherry-pick #7864 (#7884)

    This PR cherry-picks #7864
    
    ---------
    
    Co-authored-by: Pedro Pablo Aste Kompen <wachunei@gmail.com>
    sethkfman and wachunei authored Nov 21, 2023
    Configuration menu
    Copy the full SHA
    922cd64 View commit details
    Browse the repository at this point in the history
  2. chore: cherry pick 7881 (#7883)

    ## **Description**
    
    
    This PR was created to fix the issue [#7862], following code change has
    been done:
    1. Change the `getKeyringByAddress()` method to return undefined when
    address is not valid hex address (e.g. ENS domain name)
    2. Fix the existing unit tests to reflect above changes in
    `address/index.test.ts` file
    3. add extra unit tests to make sure function will return undefined when
    address is not valid hex address (e.g. ENS domain)
    
    
    ## **Related issues**
    
    Fixes: [#7862]
    
    ## **Manual testing steps**
    
    Please refer to following videos for detail how to test.
    
    ## **Screenshots/Recordings**
    
    <!-- If applicable, add screenshots and/or recordings to visualize the
    before and after of your change. -->
    
    ### **Before**
    
    
    
    https://github.com/MetaMask/metamask-mobile/assets/7315988/2c61515b-df26-460f-b2da-93fe6902e004
    
    
    ### **After**
    
    
    
    
    https://github.com/MetaMask/metamask-mobile/assets/7315988/f8cf64bb-e323-452f-99be-0c3ffc99592f
    
    
    
    - [x] I’ve followed [MetaMask Coding
    Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
    - [x] I've clearly explained what problem this PR is solving and how it
    is solved.
    - [x] I've linked related issues
    - [x] I've included manual testing steps
    - [x] I've included screenshots/recordings if applicable
    - [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 properly set the pull request status:
      - [x] In case it's not yet "ready for review", I've set it to "draft".
    - [x] In case it's "ready for review", I've changed it from "draft" to
    "non-draft".
    
    ## **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.
    
    ---------
    
    ## **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?
    -->
    
    ## **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 Coding
    Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
    - [ ] I've clearly explained what problem this PR is solving and how it
    is solved.
    - [ ] I've linked related issues
    - [ ] I've included manual testing steps
    - [ ] I've included screenshots/recordings if applicable
    - [ ] 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 properly set the pull request status:
      - [ ] In case it's not yet "ready for review", I've set it to "draft".
    - [ ] In case it's "ready for review", I've changed it from "draft" to
    "non-draft".
    
    ## **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: Xiaoming Wang <dawnseeker8@gmail.com>
    Co-authored-by: Gustavo Antunes <17601467+gantunesr@users.noreply.github.com>
    Co-authored-by: Chris Wilcox <chris.wilcox@consensys.net>
    4 people authored Nov 21, 2023
    Configuration menu
    Copy the full SHA
    d82bc55 View commit details
    Browse the repository at this point in the history

Commits on Nov 22, 2023

  1. fix: Cherry pick revert javascript disable on webview (#7898)

    ## **Description**
    This is a cherry pick of this
    [PR](#7893)
    
    ## **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 Coding
    Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
    - [ ] I've clearly explained what problem this PR is solving and how it
    is solved.
    - [ ] I've linked related issues
    - [ ] I've included manual testing steps
    - [ ] I've included screenshots/recordings if applicable
    - [ ] 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 properly set the pull request status:
      - [ ] In case it's not yet "ready for review", I've set it to "draft".
    - [ ] In case it's "ready for review", I've changed it from "draft" to
    "non-draft".
    
    ## **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 authored Nov 22, 2023
    Configuration menu
    Copy the full SHA
    60ab0be View commit details
    Browse the repository at this point in the history

Commits on Nov 29, 2023

  1. chore: cherry pick 7935 (#7944)

    ## **Description**
    
    The Bitrise failure was due to a lacking version of ruby on the Mac
    machines that was deprecated on 11/24. This PR bumps the ruby version to
    3.0.0.
    
    ## **Related issues**
    
    Fixes: #
    -
    
    https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/0e28768b-1ea4-4b9b-8acf-e867d1b6b993
    - Previous fix did not seem to fix the issue permanently ## **Manual
    testing steps**
    
    ## **Screenshots/Recordings**
    
    <!-- If applicable, add screenshots and/or recordings to visualize the
    before and after of your change. -->
    
    ### **Before**
    
    <!-- [screenshots/recordings] -->
    
    ### **After**
    
    [Bitrise
    
    E2E](https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/d924bf72-66c9-4f60-a49d-7fa2216b311e)
    
    ## **Pre-merge author checklist**
    
    - [x] I’ve followed [MetaMask Coding
    Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
    - [x] I've clearly explained what problem this PR is solving and how it
    is solved.
    - [x] I've linked related issues
    - [x] I've included manual testing steps
    - [x] I've included screenshots/recordings if applicable
    - [x] 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 properly set the pull request status:
      - [ ] In case it's not yet "ready for review", I've set it to "draft".
    - [ ] In case it's "ready for review", I've changed it from "draft" to
    "non-draft".
    
    ## **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.
    
    ---------
    
    ## **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?
    -->
    
    ## **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 Coding
    Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
    - [ ] I've clearly explained what problem this PR is solving and how it
    is solved.
    - [ ] I've linked related issues
    - [ ] I've included manual testing steps
    - [ ] I've included screenshots/recordings if applicable
    - [ ] 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 properly set the pull request status:
      - [ ] In case it's not yet "ready for review", I've set it to "draft".
    - [ ] In case it's "ready for review", I've changed it from "draft" to
    "non-draft".
    
    ## **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: yande <110056475+Andepande@users.noreply.github.com>
    Co-authored-by: metamaskbot <metamaskbot@users.noreply.github.com>
    3 people authored Nov 29, 2023
    Configuration menu
    Copy the full SHA
    5f016c2 View commit details
    Browse the repository at this point in the history
  2. chore: cherry pick #7607 (#7945)

    ## **Description**
    
    Cherry-pick for the release 7.12.0 
    
    ## **Related issues**
    
    Fixes: #7607 
    
    ## **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 Coding
    Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
    - [ ] I've clearly explained what problem this PR is solving and how it
    is solved.
    - [ ] I've linked related issues
    - [ ] I've included manual testing steps
    - [ ] I've included screenshots/recordings if applicable
    - [ ] 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 properly set the pull request status:
      - [ ] In case it's not yet "ready for review", I've set it to "draft".
    - [ ] In case it's "ready for review", I've changed it from "draft" to
    "non-draft".
    
    ## **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: metamaskbot <metamaskbot@users.noreply.github.com>
    Co-authored-by: Yande <andepandy@outlook.com>
    Co-authored-by: Cal Leung <cleun007@gmail.com>
    Co-authored-by: LeoTM <1881059+leotm@users.noreply.github.com>
    Co-authored-by: Chris Wilcox <chris.wilcox@consensys.net>
    Co-authored-by: Frank von Hoven <141057783+frankvonhoven@users.noreply.github.com>
    Co-authored-by: MetaMask Bot <37885440+metamaskbot@users.noreply.github.com>
    8 people authored Nov 29, 2023
    Configuration menu
    Copy the full SHA
    fce9c56 View commit details
    Browse the repository at this point in the history
  3. chore: build bump 1214 RC4 (#7939)

    ## **Description**
    Bump build number to 1214
    
    ## **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 Coding
    Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
    - [ ] I've clearly explained what problem this PR is solving and how it
    is solved.
    - [ ] I've linked related issues
    - [ ] I've included manual testing steps
    - [ ] I've included screenshots/recordings if applicable
    - [ ] 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 properly set the pull request status:
      - [ ] In case it's not yet "ready for review", I've set it to "draft".
    - [ ] In case it's "ready for review", I've changed it from "draft" to
    "non-draft".
    
    ## **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.
    chrisleewilcox authored Nov 29, 2023
    Configuration menu
    Copy the full SHA
    04d2d8d View commit details
    Browse the repository at this point in the history

Commits on Nov 30, 2023

  1. Configuration menu
    Copy the full SHA
    893999a View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    f5cac0a View commit details
    Browse the repository at this point in the history
  3. Update to the token rates controller version the fixes the ordered th…

    …at token rates controller its called between events
    tommasini committed Nov 30, 2023
    Configuration menu
    Copy the full SHA
    2158267 View commit details
    Browse the repository at this point in the history
  4. initialize token rates controlller on engine and fix the ticker being…

    … undefined because of the networl controller version being outdated
    tommasini committed Nov 30, 2023
    Configuration menu
    Copy the full SHA
    90fe180 View commit details
    Browse the repository at this point in the history

Commits on Dec 1, 2023

  1. Optimization of token rates controller and check price api supported …

    …currencies and chain id
    tommasini committed Dec 1, 2023
    Configuration menu
    Copy the full SHA
    56b8b83 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    edabd33 View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    0c6cde2 View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    37d5858 View commit details
    Browse the repository at this point in the history
  5. adapt to coin gecko endpoint, add chuncks for limit of 20 tokens per …

    …request, add new header for coin gecko price endpoint
    tommasini committed Dec 1, 2023
    Configuration menu
    Copy the full SHA
    011a2f7 View commit details
    Browse the repository at this point in the history

Commits on Dec 4, 2023

  1. 7.12.1

    metamaskbot committed Dec 4, 2023
    Configuration menu
    Copy the full SHA
    941f05f View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    8facbe2 View commit details
    Browse the repository at this point in the history
  3. chore: cherry-pick: test: fix wallet test (#7966) (#7970)

    ## **Description**
    
    The purpose of this PR is to address the failing wallet-tests.spec. The
    test was failing because of a token that no longer appears in the auto
    complete search. Feel free to read up more on this via:
    https://consensys.slack.com/archives/C02U025CVU4/p1701360559491539
    
    
    ## **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 Coding
    Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
    - [ ] I've clearly explained what problem this PR is solving and how it
    is solved.
    - [ ] I've linked related issues
    - [ ] I've included manual testing steps
    - [ ] I've included screenshots/recordings if applicable
    - [ ] 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 properly set the pull request status:
      - [ ] In case it's not yet "ready for review", I've set it to "draft".
    - [ ] In case it's "ready for review", I've changed it from "draft" to
    "non-draft".
    
    ## **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.
    
    ## **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?
    -->
    
    ## **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 Coding
    Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
    - [ ] I've clearly explained what problem this PR is solving and how it
    is solved.
    - [ ] I've linked related issues
    - [ ] I've included manual testing steps
    - [ ] I've included screenshots/recordings if applicable
    - [ ] 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 properly set the pull request status:
      - [ ] In case it's not yet "ready for review", I've set it to "draft".
    - [ ] In case it's "ready for review", I've changed it from "draft" to
    "non-draft".
    
    ## **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: Curtis David <Curtis.David7@gmail.com>
    2 people authored and metamaskbot committed Dec 4, 2023
    Configuration menu
    Copy the full SHA
    e595c06 View commit details
    Browse the repository at this point in the history
  4. chore: cherry-pick: test: Increase E2E test setup time (#7929) (#7977)

    ## **Description**
    
    The android E2E tests have encountered failures because the installation
    of the application on the emulator now takes longer than the current
    test timeout allows. In order to restore the ability to pass the E2E
    tests, the purpose of this pull request (PR) is to increase the test
    setup time, allowing sufficient time for the installation process.
    
    
    ### **Before**
    
    Failing Bitrise builds: 
    
    
    https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/fa0431b0-3114-4a0f-a511-23d065d4d244
    
    
    https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/10be074e-af5f-4750-8d72-7e61c6102b9d
    
    
    https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/fa0431b0-3114-4a0f-a511-23d065d4d244
    
    
    ### **After**
    
    
    Passing bitrise smoke Build:
    
    https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/354f2ad1-121b-4f48-9d7d-479bcb00160d
    Passing bitrise regression test build:
    
    https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/354f2ad1-121b-4f48-9d7d-479bcb00160d
    
    ## **Pre-merge author checklist**
    
    - [ ] I’ve followed [MetaMask Coding
    Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
    - [ ] I've clearly explained what problem this PR is solving and how it
    is solved.
    - [ ] I've linked related issues
    - [ ] I've included manual testing steps
    - [ ] I've included screenshots/recordings if applicable
    - [ ] 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 properly set the pull request status:
      - [ ] In case it's not yet "ready for review", I've set it to "draft".
    - [ ] In case it's "ready for review", I've changed it from "draft" to
    "non-draft".
    
    ## **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.
    
    ## **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?
    -->
    
    ## **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 Coding
    Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
    - [ ] I've clearly explained what problem this PR is solving and how it
    is solved.
    - [ ] I've linked related issues
    - [ ] I've included manual testing steps
    - [ ] I've included screenshots/recordings if applicable
    - [ ] 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 properly set the pull request status:
      - [ ] In case it's not yet "ready for review", I've set it to "draft".
    - [ ] In case it's "ready for review", I've changed it from "draft" to
    "non-draft".
    
    ## **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: Curtis David <Curtis.David7@gmail.com>
    2 people authored and metamaskbot committed Dec 4, 2023
    Configuration menu
    Copy the full SHA
    4e38a07 View commit details
    Browse the repository at this point in the history
  5. Configuration menu
    Copy the full SHA
    de2facf View commit details
    Browse the repository at this point in the history

Commits on Dec 5, 2023

  1. updated the header key

    metamaskbot authored and tommasini committed Dec 5, 2023
    Configuration menu
    Copy the full SHA
    f4d402a View commit details
    Browse the repository at this point in the history

Commits on Dec 6, 2023

  1. Configuration menu
    Copy the full SHA
    00653af View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    c92dc61 View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    bc95b65 View commit details
    Browse the repository at this point in the history
  4. added removed empty lines

    tommasini committed Dec 6, 2023
    Configuration menu
    Copy the full SHA
    477b92a View commit details
    Browse the repository at this point in the history
  5. Configuration menu
    Copy the full SHA
    8b62b02 View commit details
    Browse the repository at this point in the history
  6. Configuration menu
    Copy the full SHA
    7110873 View commit details
    Browse the repository at this point in the history
  7. Configuration menu
    Copy the full SHA
    d7aaffc View commit details
    Browse the repository at this point in the history
  8. Configuration menu
    Copy the full SHA
    8bedd1e View commit details
    Browse the repository at this point in the history