[Bug]: Keep unable to unlock wallet on Firefox, MacOS

[bsheart24]

Describe the bug

I am unable to unlock my Metamask wallet (browser extension) on Firefox. I have a Mac machine

Expected behavior

standard unlock

Screenshots/Recordings

No response

Steps to reproduce

1. Run Firefox
2. Click on Metamask extension
3. Enter password
4. Wait forever

Error messages or log output

The wheel spins endlessly, but extension continues to be lock

Detection stage

In production (default)

Version

12.6.2 update from Mozilla store 17 Dec 24

Build type

None

Browser

Firefox

Operating system

MacOS

Hardware wallet

No response

Additional context

Solution

4. If you switch to incognito mode.
5. Disable the extension.
6. Close tab
7. Enable extension
8. Change network to some exotic (like Mantle)
9. Enter password
10. Аfter that extension unlock incorrectly without displaying the main asset, but you can change to another network
11. Change to main network
12. Fix it!

Severity

Highest level of criticality!!! Extension cannot be used!! You need to urgently remove the version 12.6.2 from the update Mozilla store

[AbnerZheng]

I am suffering from this issue too. Please fix it ASAP.

[danjm]

@bsheart24 @AbnerZheng Would you be able to share the error logs you are seeing?

1. Go to about:addons
2. Click the gear icon
3. Select "Debug add-ons"
4. Click "Inspect" next to MetaMask
5. In the new window, make sure the "Console" tab is selected
6. Right click and then select "Save all messages to file"

And then send us that file

Here is a video of how to do that https://github.com/user-attachments/assets/459af6f5-dcfb-4864-bd23-d8d3088ec25e

[danjm]

Also, you may find that fully closing all browser windows, and then re-opening will resolve the issue (at least temporarily). Please let us know if that is true for you or not.

[AbnerZheng]

sorry, I'm away from keyboard now and can't provide the error message to you, but neither fully closeting Firefox nor restarting computer resolve the issue. I solve the issue by disabling the plugin and then enabling it as told above.