fix: (cp-7.46.0) network switcher - use additional checks for non-evm networks#15283
Conversation
|
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. |
e89a10d to
6297691
Compare
|
…nsure-toHex-uses-evm-networks
|
I think I'm in favour of closing this fix for this already merged fix: |
NicolasMassart
left a comment
There was a problem hiding this comment.
Can we have a unit test for CustomNetwork please?
I know there's no test file already, but adding one could be a good way to make sure we deal with all the cases.
…nsure-toHex-uses-evm-networks
…nsure-toHex-uses-evm-networks
|
@NicolasMassart tests added. This technically is already fixed in |
|
|
|
make the arrange props more customisable for future test cases
NicolasMassart
left a comment
There was a problem hiding this comment.
Looks good to me!
|
|
I added the |



Description
I have not been able to replicate this bug, but this is some additional checks to ensure we are correctly checking against EVM networks and ignore non-EVM networks.
We already added checks into main from #15184
^ However this targets
@metamask/multichain-network-controller@^0.4.0, whereas the RC uses0.3.0Related issues
Fixes: #15272
Manual testing steps
N/A, I still haven't figured out how to repro this.
Screenshots/Recordings
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist