Open tsadovska opened 8 months ago
Issue is also reproducible on https://wormhole-connect.netlify.app/ [Testnet]. Steps:
Actual result:
{code: 5000, message: '{"code":-32602,"message":"May not specify default MetaMask chain."}'}
Reproducible on https://testnet.portalbridge.com/ed4e22522f/ [Testnet] (Portal Bridge: 0.2.12, Wormhole Connect: 0.3.4-beta.4-development) with following scenario:
Actual result:
Uncaught (in promise) {code: 5000, message: '{"code":-32602,"message":"May not specify default MetaMask chain."}'}
Issue is also reproducible on https://portalbridge.com/ [Mainnet] when sending 0.00001 wstETH from BSC (MetaMask through WalletConnect) to Ethereum (MetaMask through WalletConnect). Notification to change network from BSC to Ethereum does not appear in MetaMask mobile app.
Errors appear in Console after user clicks on "Add wstETH to your wallet":
{context: 'client'} '{"code":-32603,"message":"This token is not supported on this network","data":{"originalError":{}}}'
'{"code":-32602,"message":"May not specify default MetaMask chain."}'
Uncaught (in promise) {code: 5000, message: '{"code":-32602,"message":"May not specify default MetaMask chain."}'}
Describe the current behavior in detail
Builds - Tested NOK:
Checked on macOS 12.7.1 and Google Chrome Version 120.0.6099.109 (Official Build) (x86_64).
Preconditions: Polygon Mumbai network is selected on Metamask app
Steps:
Actual result: Notification to change network from Polygon Mumbai to Ethereum is not shown.
Error is displayed in Console:
{code: 5000, message: '{"code":-32602,"message":"May not specify default MetaMask chain."}'}
What is the expected/desired behavior
Notification to change network from Polygon Mumbai to Ethereum is shown.