MetaMask / MetaMask/metamask-extension
[Bug]: Infinite load after update with no console errors
@dbrans is already working on this.
Since Apr 3, 2025.
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
### Describe the bug
We are receiving reports of an infinite loading screen after updating to v12.15.0. In one report, the error was encountered after updating from v12.13, and there were no console errors that seemed relevant (we checked the UI, service worker, and offscreen document consoles).
The problem was resolved by disabling and re-enabling the extension.
### Expected behavior
_No response_
### Screenshots/Recordings
_No response_
### Steps to reproduce
We don't yet have reliably reproduction steps. In the one confirmed case, it was encountered after force-updating from v12.13.0 to v12.15.0.
I was able to reproduce this once locally by doing an update test from v12.12.0 to v12.15.1. The steps I followed were as follows:
* Create an empty directory for the test
* Copy the files from a v12.12.0 build into the directory
* Load this directory as an unpacked extension in Chrome
* Proceed through onboarding (import or new wallet, doesn't matter) and wait a few seconds on the home screen (to ensure there is enough time for the vault to persist).
* Disable the extension
* Delete all files in the directory
* Copy the files from a v12.15.1 build into the directory
* Enable the extension and quickly reload it (immediately after enabling)
* Open the browser-action popup
At that point I saw the infinite load. But then after reloading the extension again, the problem disappeared.
### Error messages or log output
```shell
```
### Detection stage
In production (default)
### Version
12.15.0
### Build type
None
### Browser
Chrome
### Operating system
MacOS
### Hardware wallet
_No response_
### Additional context
_No response_
### Severity
_No response_
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.
Assessment
This issue has not been assessed yet.