MetaMask / MetaMask/metamask-extension
[Sentry] Error: No metadata found for 'useNonceField'
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
Sentry Issue: [METAMASK-XGXS](https://metamask.sentry.io/issues/6433767977/?referrer=github_integration)
```
Error: No metadata found for 'useNonceField'
at Array.reduce ()
at handler (app/scripts/lib/ComposableObservableStore.js:70:30)
at _handleAccountsControllerSync (app/scripts/controllers/preferences-controller.ts:998:10)
at .setActiveNetwork (app/scripts/metamask-controller.js:3165:25)
at async s. (app/scripts/lib/createMetaRPCHandler.js:23:7)
...
(15 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 trace in app/scripts/lib/ComposableObservableStore.js:70 and follow the call chain through preferences-controller.ts:_handleAccountsControllerSync, metamask-controller.js:setActiveNetwork, and createMetaRPCHandler.js. Determine why metadata for useNonceField is unavailable during setActiveNetwork, then verify that the Sentry error no longer occurs in that flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100