[Bug]: Firefox import keystore JSON

[pociej]

Describe the bug

Importing password protected keystore JSON doesnt work in firefox. Once file selection window popus up metamask plugin widget disappears and there is no option to provide password.

Steps to reproduce

1. Open plugin widget in FF go to accounts -> imports -> JSON

Error messages or log output

No response

Version

11.0.0

Build type

None

Browser

Firefox

Operating system

MacOS

Hardware wallet

No response

Additional context

No response

[anaamolnar]

Hello, @pociej. Thank you for taking the time to report this issue! Do you experience the same problem when trying to import in Metamask in Brave or Chrome, or does it work as expected? Thank you!

[pociej]

hi @anaamolnar yes Chrome and Brave works. I checked FF on different machines and operating systems. And i can confirm problem was the same everywhere.

[plasmacorral]

Thank you for sharing your experience here, @pociej, I am sorry for the frustration. This behavior and performance is not ideal. If the issue is specific to having MM open in the pop-up view, I can recommend a potential work around to help you get this account imported into the Firefox extension.

1. Open MM
2. Select the kebab menu (3 dots on the right corner)
3. Select Expand View From this point forward you should have MM open in the full browser window
4. Hit the Accounts drop down menu
5. Select Import account
6. Hit the dropdown to select JSON file
7. enter optional password as needed
8. Select import
9. Be extraordinarily patient, and do not stop the page.
10. Account is imported and active

There is a previously reported issue that impacts the ability to import from the pop-up (smaller) window. I will add to that existing impact that we have impact on Firefox 117, as we can observe today.

From within that report there is another issue cited about poor performance when importing JSON. In my experience reproducing this today as far back as 10.34, Firefox would present the message A web page is slowing down Firefox. To speed up your browser, stop that page. If you allow it to keep running the account will be successfully imported. In an observation I noted within one of these earlier tickets, if the browser crashed, the new account would appear on relaunch.

There is also a message that appears, but I notice that it is partially obscured by the Import account box. It says: Expect this JSON import to take a few minutes and freeze MetaMask. We apologize, and we will make it faster in the future.

[pociej]

@plasmacorral. Thx for quick reply. Yeah I noticed expanded view is kind of workarround. But its not an good solution IMO.
While I or you or other dev can use workarround end user of the app is customer not me. And posting inside the app such instructions is unacceptable UX. Do you plan to solve it?

[plasmacorral]

@pociej This is something that I too would like to see fixed and will work with the team to try and get it prioritized.

[pociej]

@plasmacorral is there any update in this issue? Do you need help in fixing the problem? Im open to PR.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity in the last 90 days. It will be closed in 45 days if there is no further activity. The MetaMask team intends on reviewing this issue before close, and removing the stale label if it is still a bug. We welcome new comments on this issue. We do not intend on closing issues if they report bugs that are still reproducible. Thank you for your contributions.

[github-actions]

This issue was closed because there has been no follow up activity in the last 45 days. If you feel this was closed in error, please reopen and provide evidence on the latest release of the extension. Thank you for your contributions.