MetaMask / MetaMask/metamask-mobile
addEthereumChain not working on chain with chain_id of 10
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3k
- Forks
- 1.7k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 669
Description
[A QBS customer says](https://consensys.slack.com/archives/G8RSKCNCD/p1633405160332500):
> Currently, we are developing a blockchain application to be used on the Metamask Mobile dApp browser. We require the use of the methods 'wallet_switchEthereumChain' and 'wallet_addEthereumChain'.
However, the popups to add a new chain and to switch chains do not work, and give the error, 'May not specify default Metamask chain'. This error does not appear on the desktop version of the metamask extension.
The deployed QBS network is on chain ID: 10. Is there a way to change the chain ID? Or are there any fixes for the Metamask Mobile bug?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the mobile dApp-browser calls to wallet_addEthereumChain and wallet_switchEthereumChain with chain ID 10, then compare the behavior with the desktop extension mentioned in the report. Trace the mobile handling of the “May not specify default Metamask chain” error; done means the add and switch popups work for this chain without that error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- blockchain, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100