MetaMask / MetaMask/metamask-mobile
Error: Missing or invalid. respond() response: {"id":null,"jsonrpc":"2.0","error":{"code":1,"message":"I...
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3k
- Forks
- 1.7k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 669
Description
Sentry Issue: [METAMASK-MOBILE-2G86](https://metamask.sentry.io/issues/5529963854/?referrer=github_integration)
```
Error: Missing or invalid. respond() response: {"id":null,"jsonrpc":"2.0","error":{"code":1,"message":"Invalid chainId"}}
at (node_modules/@walletconnect/sign-client/dist/index.cjs.js:1:40246)
at asyncGeneratorStep (node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:20)
at _next (node_modules/@babel/runtime/helpers/asyncToGenerator.js:22:9)
at tryCallOne (node_modules/promise/setimmediate/core.js:37:12)
at setImmediate$argument_0 (node_modules/promise/setimmediate/core.js:123:15)
...
(8 additional frame(s) were not displayed)
```
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 with the reported stack trace in node_modules/@walletconnect/sign-client/dist/index.cjs.js and trace it back to the app’s WalletConnect integration. Reproduce the Invalid chainId response and identify the affected request; done means the Sentry error is resolved or correctly handled and verified with a reproducible check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- blockchain, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100