MetaMask / MetaMask/metamask-mobile
Error: No matching key. session: 310ce5c68bc06441b14b82aec4ffbf4156f414d590518d1452c1ed9c6f1ea233
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-29F8](https://metamask.sentry.io/issues/5021393497/?referrer=github_integration)
```
Error: No matching key. session: 310ce5c68bc06441b14b82aec4ffbf4156f414d590518d1452c1ed9c6f1ea233
at getData (node_modules/@walletconnect/core/dist/index.cjs.js:1:42999)
at anonymous (node_modules/@walletconnect/core/dist/index.cjs.js:1:41769)
at ?anon_0_ (node_modules/@walletconnect/sign-client/dist/index.cjs.js:1:10068)
at next (native)
at asyncGeneratorStep (node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:24)
...
(37 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 Sentry report and the stack trace entry points in node_modules/@walletconnect/core/dist/index.cjs.js and node_modules/@walletconnect/sign-client/dist/index.cjs.js. Reproduce the session error and determine why the matching key is unavailable. Done means the error is resolved or prevented and the affected WalletConnect flow is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100