Metamask + Trezor pop up window automatically closes without signing #784
Comments
|
Which OS are you using? |
|
Mac and brave. The workaround I found is to downgrade to firmware 2.3.0, and reset the metamask and clear my browser cache, now it works with the older version. |
|
Brave is not supported. Please, try if this works in Chrome. |
|
I also use the brave browser and had problems confirming a certain transaction for weeks for the same reason. Then it worked. I used the Trezor suite (beta version) for this. And now it does not work AGAIN. The problem: the metaMask wallet I use is connected to the BraveBrowser. I can NOT open this particular wallet anywhere else because of Trezor, as I do not have the private key! :( so I urgently need your help for this problem |
|
@prusnak it's also broken in Chrome. I'm also a Brave user, but I just tried connecting the Trezor to Metamask in Chrome so that I can test, but the popup closes immediately before signing, and then the metamask page is stuck on the "Looking for your Trezor" screen
Im using: issue at Metamask: |
|
@bradwbradw do you have any popup blocker installed like Adblock, privacy Badger etc? |
|
hey @szymonlesisz , I just disabled adblock, and turned off "pops up and redirects allowed" in chrome, restarted Chrome and tried again, but the problem still persists. This time, i did see the error "Device call in progress" in the metamask UI |
|
@bradwbradw Please, try the same thing in the Incognito mode of Chrome. |
|
could you pls describe what you are doing step by step, bc. im not able to reproduce the issue. |
|
I am unable to connect the hardware wallet again after I had removed it
while trying to work around the issue.
@prusnak When I click on "connect hardware wallet" in incognito mode, it just opens up a new window with the
`chrome-extension://.../home.html#new-account/connect` url in regular Chrome, and the same problem happens.
@szymonlesisz for steps, go to: MetaMask/metamask-extension#10896 (comment)
|
|
i guess this will require additional debugging so i need to ask you to do the following:
|
|
alright, I DM'd you the logs.
… |
|
Does anyone know a workaround to this issue? Because, in the mean time, Trezor no longer works with MetaMask. Pop-up window always unexpectedly closes before allowing me to do anything on Trezor. That's the huge impediment as it prevents me from interacting with any DeFi app. Again, on Polygon, issue still persits. I'm not keen at all at moving my funds on MM. Thank you. |
|
@faxotherapy the workaround I found is that I downgraded the firmware 2.3.0 (for model T) and it works. I have been using this firmware version for a few month and it works fine. |
|
Using a Trezor One firmware v1.10.0, I'm able to use it with Metamask on
Windows 10 Firefox, but not at all on Mac Catalina (Chrome or Firefox)
I also tend to change networks frequently too, between Matic, Binance Smart
Chain, Fantom and Eth. I don't know if this has anything to do with the
problem.
…On Fri, Jun 4, 2021 at 1:39 PM ChooChooCC ***@***.***> wrote:
@faxotherapy <https://github.com/faxotherapy> the workaround I found is
that I downgraded the firmware 2.3.0 and it works. I have been using this
firmware version since.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#784 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABD7F5F35DBV5SCSKICLJVLTRE2ZTANCNFSM4ZR6KTYQ>
.
|
|
I am also having major issues with my Model T (firmware 2.3.6) with Metamask. If/when the popup does appear after making transaction request, it tells me that my Trezor device is inactive and that it is being used by another application. When I click on activate, either the pop-up will close and give me the "device was disconnected" error or it will forever spin the "loading" message and then time out saying "unable to claim interface." other times, the transaction just gets stuck in MM, but not appear as pending on etherscan so i have to manually "reset account" in MM to get rid of the stuck txns. is this a firmware issue, as this just started happening recently? any ideas on how to remedy? all of my crypto is effectively stuck at the moment which is no bueno. |
|
I was seeing my Trezor popup window closing upon an attempt to send today, with the following error: "Forbidden key path" A quick Google search shows it appears it could be a firmware issue, but I haven't followed the provided steps to ensure they work. Edit Removed link that I've not verified works to fix the issue. |
It's not a firmware issue. It's an issue of a caller (Metamask) using the wrong path for selected coin (i.e. not using m/44'/60' for Ethereum or m/44'/1' for any of the Ethereum testnet networks). |
|
I'm really trying to reproduce this but with no luck. my setup: macOS Catalina 10.15.15 Trezor 1.10.0 and 2.3.6 i even tried it with older setups: older browsers, older MM extensions, older firmwares, custom firmwares, webusb - before chrome 91... @trezor/qa pls help me out here |
|
@szymonlesisz Did you try reproduce that in alternative network other than ethereum mainnet like BSC, xDai, or Matic? I remember that's when it was failing for me. |
Then you are just confirming my words from above:
Each coin has assigned path - https://github.com/satoshilabs/slips/blob/master/slip-0044.md - and no other path should be set. I am almost confident it is this issue, because downgrade to 2.3.0 (where we did not check the paths) seems to fix the issue. Metamask should catch error from Connect and show it in their UI, so it seems there are two issues with Metamask:
|
|
MetaMask has gone too far on this issue. I will never ever again use MetaMask with Trezor. It simply is dangerous. It's totally unreliable. I'm currently in a leveraged position on Instadapp and I cannot unwind it, because I'm not offered to confirm on my Trezor after clicking on the Confirm button on MM pop-up window. |
|
Instead of downgrading the firmware you can try to temporary disable safety checks mentioned by @prusnak to see if that helps. Trezor will warn you about using invalid slip44 path.
|
I'm going to reply to myself. The issue seems to happen erratically. When it happens, one should try any combination of the following: close dApp tab/window (or quit/restart Firefox), Lock MM (then re-open it), switch network back and forth (e.g. Ethereum ⇌ Polygon), unplug/replug Trezor (if necessary, connect Trezor directly to USB port), clear cookies/cache for the dApp tab/window, sometimes opening MM in a tab first, and interacting with the MM tab instead of the MM pop-up window help. The thing I understand is why any two or three of the combination above help solve the issue, at least temporarily. |
Don't really know whether the suggestion is addressed to me or not. If so, I'm a bit scared to break everything in my Trezor with these steps. Is it some kind of a debugging process for Trezor? |
|
I was able to reproduce and solve issue via Suite 21.6.1 As soon you change device setting via #784 (comment) you can send transactions. Info:
|
|
I can confirm what @bosomt wrote. With disabled safety checks, I was able to send a transaction. With enabled safety checks, i got the same error message. Info:
|
|
@faxotherapy it was addressed to anyone having this issue don't worry you will not break anything.
like @prusnak said: |
|
of course it would be better to have "safety checks" enabled (you can enable them back after you send your coins) but since your assets are locked in metamask, this is the way how to work with them |
|
Previously I mentioned Enkrypt. It uses the latest version of Trezor Connect v9. We are only tracking issues with Trezor Connect v9. The version that MetaMask uses (v8) is deprecated. |
|
@sime good to know. |
|
I believe that @sirloinfurr is correct, and this is a CPU related issue. I had this issue on an older laptop - tried different browsers, even reinstalled the OS. It wasn't until I tried a more powerful desktop that I had no more problems. |
|
Then it turns out that the matter is in very poor code optimization or some kind of leaks. Because in terms of resource consumption - there is no problem to sign a transaction even on an old mobile phone. When the Trezor popup opens, something happens, because of which the computer starts to warm up and the page crashes. I wrote to the Metamask team, waiting for an answer. |
I find MetaMask and Enkrypt can conflict with each other. I suggest disabling the MetaMask extension temporarily and see if Enkrypt then starts to wake up. |
And
This is the definition of a race condition. Which is innately hard to track down. |
|
I removed MM extension from brave browser before I tried using Enkrypt. Unfortunately there is no Enkrypt listed in the 'Connect your wallet' list on opensea and it does not connect automatically. Even tried to use the connect with MM but it just brought me to the MetaMask homepage. So, since Enkrypt, does not work with opensea and MetaMask-OS-Trezor seem to be a problem, to me it seems that I (we) don't have many options left. Buying a new laptop just to use MM with Trezor is not an option from a financial perspective. I'll write Enkrypt and ask them if they have an idea and maybe opensea as well. |
|
@Phileicht Brave is weird, Just tried to use it for the first time. I guess it conflicting with its built-in wallet.
Enkrypt works as expected (for me at least) on Firefox and Chrome. No new laptop required. Edit: Brave started working after re-starting it. |
|
@sime it seems like in my case it has been an issue with Pocket Universe and the pop up to connect Enkrypt to OS. |
|
I had a little chat with Enkrypt, they will have a look at the conflict with Pocket Universe. |
@sime Metamask version v10.25.0 is running. Is Trezor Connect v9 implemented? |
|
Unfortunately, my prediction was wrong. Recently the internal dependency that uses Trezor Connect v9 was released, now it needs to be upgraded into the main repository of the extension: https://github.com/MetaMask/eth-trezor-keyring/releases/tag/v1.0.0 |
Ok. We are looking forward to this implementation to resolve this issue. |
|
@jvnovo Only MetaMask team. |
|
New Update of MetaMask extension (10.26.1) still uses eth-trezor-keyring: ^0.10.0 and not v1.0.0 which would use Trezor Connect v9. For now, my solution, thanks to @sime is to use Enkrypt in Firefox, which seems to work very well so far. I've already asked the Pocket Universe devs if they could fix the problem with Enkrypt, but they can't because Enkrypt seems to take control of the entire window.ethereum object, which causes errors on the Pocket Universe side. |
|
@Phileicht Could you please describe step by step how do get to that issue? I am trying to reproduce the issue with MetaMask and I am not able to. It's possible that once MetaMask updates to |
|
@karliatto
Here is what I did this morning:
Tested with versions: Also tested with disabled and removed other browser extensions. |
|
QA OK tested on macARM + Chrome + MetaMask and Windows 10 + Chrome + MetaMask /latest versions/ Device firmware: latest 2.5.3 firmware with Safety checks disabled. I was able to login via signing on device with two separate accounts with some ETH present on account. |
|
I did not used to have this problem in general but since sometime in the last week or so, I'm now experiencing it 100% of the time on 3 different machines. In contrast MetaMask on Firefox works flawlessly with the |
|
I also have never had this problem for almost two years only started happening several weeks ago in chrome and Firefox, switched to edge which fixed the issue for a week but now is doing the same. Needs to be fixed or will be a mass exodus to ledger |
|
I'm facing this nearly all the time with Trezor Model One on Chrome and Firefox. Sometimes resetting metamask, cleaning browser cache and reconnecting trezor helps, I'd say 30% of the time, and 70% popup just disappears and I can't sign anything. Very frustrating. I'm on Manjaro Linux, but I see people in this thread have faced the same on Win and macos. I'd happily provide any troubleshooting info you may need. |
|
We are currently working on fix. No need any more info for now. |
|
Hi team. Can you give us feedback on how the fix for this issue is going? |
|
Jvnovo's comment is accurate. I also can't get my Trezor to approve any MM smart contract interactions. The pop-ups disappearing was always frustrating issue for years, but now it's completely broken. Computer restarts or changing browsers no longer help. The account is bricked. And to answer your question Jvnovo, yes, this problem has been going on for years and hasn't been fixed. |
|
After a huge amount of time MetaMask has finally merged the necessary changes! MetaMask/metamask-extension#18302 We are now eagerly awaiting the next MetaMask release. |
|
This repo is obsolete. Therefore we will archive it. We track all the issues connected to Connect in Trezor Suite repo. Regarding this issue, we track all issues regarding Connect popup here. |
and others
When the pop up window shows up for me to sign transactions (the part where there is a green circle waiting to load), the window automatically closes before I can sign anything, and in my metamask activity it says "Failed, send X coin".
The text was updated successfully, but these errors were encountered: