MetaMask / MetaMask/metamask-extension
[Sentry] Error: Skipping migration: `NetworkController.networkConfigurationsByChainId` is not an object.
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-XMGW](https://metamask.sentry.io/issues/6683341553/?referrer=github_integration)
```
Error: Skipping migration: `NetworkController.networkConfigurationsByChainId` is not an object.
at versionedData.data (app/scripts/migrations/160.ts:112:7)
at r.migrate (app/scripts/migrations/160.ts:61:24)
at Migrator.migrateData (app/scripts/lib/migrator/index.js:43:46)
at loadStateFromPersistence (app/scripts/background.js:741:9)
at initialize (app/scripts/background.js:547:9)
...
(1 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 by reading app/scripts/migrations/160.ts at the reported lines, then trace how app/scripts/lib/migrator/index.js and app/scripts/background.js load persisted state. Reproduce the migration error with the relevant persisted data and determine the expected handling for a non-object NetworkController.networkConfigurationsByChainId value. Done means the behavior is defined and covered by an appropriate migration test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100