MetaMask / MetaMask/metamask-extension
[Bug]: Basic Functionality - My wallet got broken `Cannot read properties of undefined reading ('type')` `Account not found` `at new JA eval` and `Account may not have been removed from snap`
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
### Describe the bug
My wallet got broken after re-enabling basic sync and reloading it with multiple errors
`Cannot read properties of undefined reading ('type')`
`Account not found`
`at new JA eval`
`Account may not have been removed from snap`
I'm unsure which error(s) are relevant for the broken UI
### Expected behavior
_No response_
### Screenshots/Recordings
https://github.com/user-attachments/assets/63f52dd1-a90f-41f6-a59a-44bb05cd7c90
### Steps to reproduce
I'm unsure on the repro steps. Roughly
1. Perform a tx
2. Turn off basic func
3. Perform a couple of tx from a dapp
4. Enable basic func
5. Click Reload extension
6. Login
7. Click netwokr menu (unsure)
8. Wallet broken
### Error messages or log output
```shell
```
### Detection stage
During release testing
### Version
13.11.0
### Build type
None
### Browser
Chrome
### Operating system
MacOS
### Hardware wallet
_No response_
### Additional context
_No response_
### Severity
_No response_
Contributor guide
Research direction
Start by testing the reported sequence in MetaMask extension version 13.11.0 on Chrome and macOS: transactions, disabling and re-enabling basic functionality, reloading, logging in, and opening the network menu. Compare the resulting UI and errors, then identify which failure breaks the wallet and verify that the wallet remains usable after the sequence.
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
- 20/100