-
Notifications
You must be signed in to change notification settings - Fork 973
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connected accounts are not listed. #5432
Comments
@mooorex I cannot reproduce the issue with shared 'steps to reproduce'. Do you see it each time and every network? I mean is it a consistent issue? |
@Aniket-Engg Yes, I can reproduce it every time no matter which network I use and I have serval Chrome profiles no matter which profiles I use. It seems that the Chrome DevTools didn't give much useful information. But after you said this, I started a new Chrome profile, the Remix behaves normally with this new profile. The difference between my existing Chrome profiles and the new one is that in addition to metamask, I also installed other extensions (including other wallets). Maybe that's the reason. I will check if this is the cause of the problem when I have time. Thanks very much. |
Sure. Thanks for the info 👍 |
Besides metamask, I installed another extension wallet, then the account list is empty. If I turn off this "another extension wallet" in the page chrome://extensions/, the Remix works very well. Then, the second extension wallet causes the trouble. @Aniket-Engg |
are you you you are allowing connection from wallet side? |
Yes, as you see in the screenshot, Metamask already shows connected. @LianaHus |
Describe the bug
On the tab of Deploy & run transactions, when the environment is switched from others (e.g. Remix VM(Cancun), the default environment) to injected provider-metamask, if the injected provider is already connected, the account will not be listed.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
the account drop-down box is filled with connected accounts.
Screenshots
Desktop (please complete the following information):
Additional context
The problem does not exist on my Arch Linux operating system (kernel 6.12.1-arch1-1) equipped with chromium-131.0.6778.85-1.
The text was updated successfully, but these errors were encountered: