Metamask + Trezor pop up window automatically closes without signing

[ChooChooCC]

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".

[prusnak]

Everyone, please make sure you are running Metamask 10.8.0. They are slowly pushing the update to you which should fix the issue.

@camus1612 @danny-molamola @faxotherapy @alexruzenhack @lostintime101 @lawrenzpng @mickmastermike @HeroHann @vying1 @darkwing @ChooChooCC @bradwbradw @onetwoitsthewu

[camus1612]

I upgraded. Worked good at start but now again on Pancakeswap it's still happening.

[GeraldWallace]

I upgraded, worked for about 10 txns before the problem persisted consistently. Tried everything in this thread. No solution in sight.

Also created this account just to comment. It's stopping from making so many essential transactions.

[danny-molamola]

I upgraded to 1.80, and it worked most of the time. Occasionally the issue still happens, but it is much less frequent. However, it created another issue, when I try to use it on Avalanche with MM and Trezor, all transactions failed with the error "String Overflow". It worked before the upgrade. Now I have to use Trezor on another machine, with an older MM version for my Avalanche transactions.

[aloceros]

Just a suggestion for everyone having problems - you can use Rabby instead of Metamask. Since switching my Trezor usage has been trouble free on all EVM chains.

[danny-molamola]

Thanks for the suggestion, tried a few transactions using Rabby on Avalanche and it works great. The only issue on Rabby for me is the lack of Harmony support.

[danny-molamola]

Upgraded to 1.81, and the pop up window automatically close issue came back again, see this issue every 2-3 transactions, I'm using it on Harmony and can't use Rabby as alternative.

[inthernar]

I started having the above described issue:

Chrome Version 96.0.4664.110 (Official Build) (x86_64) MM v10.8.1 Trezor T v2.4.3

I am trying to execute a transaction on Matic. The first one or two times the pop-up opens and I can interact with it to complete the transaction. After two or three tries, the pop-up displays and closes before I can interact with it. On my Trezor it asks me to enter my passphrase in the window. Problem is, the window is gone. When I check my Trezor Suite it tells me that the Trezor is incorrectly waiting and resets the passphrase to normal on the Model T screen. And the transactions fail.

In order to get it to work again, I have to close out entire from Chrome. Once it reloads, I can try again. It works the first two or three times then back to closing pop-up loop.

Note: I was having this issue prior to upgrading my firmware to 2.4.3 (it was the version right before this one, 2.4.1 maybe, I cannot remember) I was hoping upgrading would have resolved this.

No pop-up blocks, nothing fancy. I read all the comments above, tried many of the things. DevMode is too much for me right now as I am overloaded and super busy. Read several other googled pages with similar issues. This issue is far from closed and happens a lot. I do not have my PC here, so I cannot test with that. I am stuck on my Mac. Every day that passes, I lose a lot of money with the projects that I am in. Please do not take this too lightly, and I am patient. Thank you so much.

Please help.

[camus1612]

Guys reopen this, you can see this problem is still valid.

[bradwbradw]

Still happening for me too after the update, intermittently.

It happens more often when I have many browser tabs open and things are lagging. Not sure whether it's due to high CPU or high RAM usage, but the slowdown effect seems to increase the likelihood of this issue appearing.

On Mon, Jan 3, 2022 at 1:44 PM camus1612 @.***> wrote:

Guys reopen this, you can see this problem is still valid.

— Reply to this email directly, view it on GitHub https://github.com/trezor/connect/issues/784#issuecomment-1004379837, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABD7F5CCKB37QEDOC3B6MIDUUIKETANCNFSM4ZR6KTYQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you were mentioned.Message ID: @.***>

[Ankarrr]

I have the problems again and again. Can dev please do something to fix this?

[faxotherapy]

I came to the conclusion that Trezor devices are utterly useless for DeFi plays. They're only great for storing BTC, ETH, etc. As a result, I decided to go with Ledger for DeFi. In the end, one must choose between a company that's utterly bad in terms of customer support (SatoshiLabs) and a company that's utterly bad with customer data (Ledger).

[wendys-cats]

@Ankarrr @bradwbradw @camus1612 @vying1 @danny-molamola thank you for reporting!

Can you please elaborate on your setup? We are trying to reproduce the issue(s) and this might help narrow it down.

OS; browser type and version; trezor device type and firmware; metamask version; what were you trying to do - network, transaction type, if it was metamask integration with another provider and so on.

[brbubba]

@Ankarrr @bradwbradw @camus1612 @vying1 @danny-molamola thank you for reporting!

Can you please elaborate on your setup? We are trying to reproduce the issue(s) and this might help narrow it down.

OS; browser type and version; trezor device type and firmware; metamask version; what were you trying to do - network, transaction type, if it was metamask integration with another provider and so on.

Metamask 10.8.1 LinuxMint Brave Browser (Chrome won't even connect to the Trezor)

Swapping 1 FTM to USDC on Spookyswap. Trezor validation window pops up and closes within 2 seconds. Disabling security outlined above has no effect. If you repeat the transaction no window pops up, you have to close out of Brave and relaunch to get the 2 second window to pop up again.

FYI works just fine on windows in Brave. Would prefer to use on dedicated Linux system for crypto that doesn't see daily use.

[danny-molamola]

Metamask 10.8.1 I've a MacBook Pro and old Air, both have the same issue Tried Brave and Chrome, both the same I have a Trezor One and T, both the same, I use the One more and see this issue more often

Transactions: The issue appears randomly, I saw it on Aave, Curve on Polygon, and DFK on Harmony, and some other sites that I've forgotten.

[bradwbradw]

MacOS Big Sur 11.6 Firefox 95.0.2 Trezor One f/w 1.10.4 Metamask 10.8.1 Various networks: eth, fantom, polygon. Any kind of transaction is susceptible

On Thu, Jan 6, 2022 at 2:03 PM danny-molamola @.***> wrote:

Metamask 10.8.1 I've a MacBook Pro and old Air, both have the same issue Tried Brave and Chrome, both the same I have a Trezor One and T, both the same, I use the One more and see this issue more often

Transactions: The issue appears randomly, I saw it on Aave, Curve on Polygon, and DFK on Harmony, and some other sites that I've forgotten.

— Reply to this email directly, view it on GitHub https://github.com/trezor/connect/issues/784#issuecomment-1006966996, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABD7F5ADI3UQ6WXL6AEVP6TUUYGSVANCNFSM4ZR6KTYQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you were mentioned.Message ID: @.***>

[camus1612]

@Ankarrr @bradwbradw @camus1612 @vying1 @danny-molamola thank you for reporting!

Can you please elaborate on your setup? We are trying to reproduce the issue(s) and this might help narrow it down.

OS; browser type and version; trezor device type and firmware; metamask version; what were you trying to do - network, transaction type, if it was metamask integration with another provider and so on.

Windows 10 Chrome 97.0.4692.71 Trezor One Firmware: 1.10.4 Metamask 10.8.1

It happens a lot on Pancake Swap on BSC while trying to swap and adding liquidity. Also happened on Harmony at DefiKingdoms while trying to add liquidity. On AAVE when trying to repay loan, when trying to deposit collateral.

[camus1612]

I came to the conclusion that Trezor devices are utterly useless for DeFi plays. They're only great for storing BTC, ETH, etc. As a result, I decided to go with Ledger for DeFi. In the end, one must choose between a company that's utterly bad in terms of customer support (SatoshiLabs) and a company that's utterly bad with customer data (Ledger).

I'll take the bad customer support instead. Because if it'll continue, there will be a vacuum that other company will fill. While me staying secure all along. I hope they will fix the customer support in first priority of course.

[darkwing]

For those experiencing this issue, could you do the following:

• Click the "Extensions" icon and choose "Manage extensions":

  

• Click the "background.html" link, which will open a developer console:

  

Please let us know if you see any errors in the console! Thank you!

[danny-molamola]

For every action (click on the buttons on the Trezor pop-up window, or physically press the button on the Trezor One, an error "Refused to set unsafe header 'origin'" is shown on the console.

When the pop-up was closed unexpectedly, there is no new error messages on the console.

As the transaction was stuck at this state, I unplugged the device and it showed the below errors:

[inthernar]

For those experiencing this issue, could you do the following:

• Click the "Extensions" icon and choose "Manage extensions":

• Click the "background.html" link, which will open a developer console:

Please let us know if you see any errors in the console! Thank you!

My screen doesn't have the URLs available, see my attached image, please.

It has started happening a lot more today, like non-stop. I've done the RESET ACCOUNT option. It used to work when I close the browser window and re-open, now six times in a row, the pop-up open and then closes right away. For me, this happens on the MATIC (polygon) network only (so far). I haven't had to use another chain as much as this one.

[o3o3o]

Same error here. It had happened many times :(.....

[petravis]

same for me too

edit: Works on my model T - model one is having the issue

[warc0s]

Same error here, and I bought my trezor one a few days ago.. Im regretting so much

[wendys-cats]

Thank you very much for providing more info! I have FINALLY managed to replicate the pop up issue, so hopefully this comment will be helpful for you all. @mrkaqz @vying1 @markg31 @mickmastermike @lawrenzpng @lostintime101 @alexruzenhack @faxotherapy @danny-molamola @camus1612 @GeraldWallace @danny-molamola @ramseynasr @bradwbradw @Ankarrr @brbubba

So, to summarize:

1. The pop-up problem - have not reproduced it recently and it might be OS+browser+settings dependent. We (QA) have experienced the issue in the past, but (not yet) since the new version came out. Forever loading trezor connect for signing transactions AND pop up closing itself - I have managed to replicate this issue. @szymonlesisz Reproduced on Win10 + Chrome 97.0.4692.71 (Official Build) (64-bit) + webUSB for both adblock present and not present.

How to avoid this issue: do not check the opt-in boxes mentioned below, disable adblock for trezor connect site (just to be sure), and install the latest bridge (2.0.31). Then, connect your HW account again. If you encounter the same problem even after taking these measures, please report here immediately, so we can look into it. Thank you again for taking the time to write us the additional data!

The issue started for me once I checked these two:

opt in one

opt in two - this one is available only when connecting via webUSB.

I was also able to temporarily solve it by disabling adblock for trezor connect site, but it worked only for a short while. It is possible that adblock might play a role for some users.

2. wrong path derivations - should be solved with new Metamask version.

3. Refused to set unsafe header 'origin' - when using T1 or TT on Brave. Apparently, Brave wallet uses funny HD paths, and this happens when you try to connect Trezor, Metamask and Brave when the paths are not compatible.

@petravis @o3o3o can you confirm this? Or is your setup different? I was only able to reproduce this with Brave, but Metamask itself might also do this for certain tokens. @prusnak ?

Just so we're on the same page - these are HD paths offered by Metamask (for ETH testnet). The yellow one is compatible with Brave wallet, the red one is not and will result in being unable to connect properly all three (Metamask, Brave, Trezor) and, of course, being unable to sign transactions.

4. contract interaction failing - experienced this myself. Created dum dum token contracts on tROP testnet via remix, injected web3 with metamask. Metamask shows a LOT of 429 errors (too many requests), it might be related, and also explain the randomness.

AFAIK, MEW also offers contract interaction, and I have never experienced any issues with it in the past. It's not as pretty, but it should get the job done.

5. further party providers - this might be out of scope, and out of our hands, since it is accessing HW accounts on said party provider via Metamask.

Other testing info 1. Windows 10 and Windows 11 Adblock present Browser Chrome Version 97.0.4692.71 (Official Build) (64-bit) Browser Firefox 96.0 (64 bit) Metamask version 10.8.1 (polygon mumbai testnet, binance smart chain testnet, ropsten testnet) Remix Pancakeswap Devices T1 1.10.4 and TT 2.4.3 Trezord 2.0.27 and 2.0.31, also tried with webUSB for Chrome

Outcome: Chrome with Metamask shows a LOT of 429 errors. Did not encounter Refused to set unsafe header 'origin'. Did not encounter pop up issue. Remix with Metamask - Successfully created, compiled, deployed contract, contract interaction works mostly fine, sometimes the response time took too long. Could not reliably reproduce the issue. Might be tied to 429 errors. Integration with pancakeswap - only rudimentary. Was able to access trezor via metamask in pancakeswap production, but they do not offer trezor integration/it does not work on testnet.

I also managed to totally break Metamask extension in Chrome TWICE, had to restart everything to get it to work again. Most likely crashed first time when I tried stuff with pancakeswap - it refuses to stay on testnet and switches back to mainnet. Metamask crashed second time when I was testing trezor connect.

2 mac Big Sur Adblock present Chrome Version 96.0.4664.93 (Official Build) (x86_64) Brave Version 1.34.80 Chromium: 97.0.4692.71 (Official Build) (x86_64) - tested, but Brave is NOT supported! Metamask extension 10.8.1 (polygon mumbai testnet, binance smart chain testnet, ropsten testnet) Remix Devices T1 1.10.4 and TT 2.4.3 Trezord 2.0.27, also tried with webUSB for Chrome

Outcome: Observation: Brave, like Metamask, uses different testnet coins. Encountered Refused to set unsafe header 'origin' when using T1 or TT on Brave. Did not encounter pop up issue on either browser. Chrome with Metamask shows a LOT of 429 errors.

[rsimonton]

This issue (pop-up window appearing momentarily before closing when attempting to complete/sign a tx) has been long standing and has been very annoying but I've lived with it. Recently it's happening more often (or at least it feels that way). This morning I was able to reproduce it 100% simply trying to sign a transaction on a proposal on https://commonwealth.im/. Given that it's been happening for ages I can say with certainty that it's not tied to any one version of the specs below as they've all been upgraded over time and the issue has persisted.

T1, firmware: 1.10.4 Mac: High Sierra 10.13.6 (17G6030) Brave: Version 1.34.80 Chromium: 97.0.4692.71 (Official Build) (x86_64) MetaMask (NOT Brave Wallet, which is disabled): 10.8.1 Trezor Suite: 21.12.2

I have Brave Shields (ad block) down for the Trezor Suite site.

@wendys-cats "How to avoid this issue: do not check the opt-in boxes mentioned below" -- I've never once checked the box and always click "allow once for this session".

@darkwing (holy shit, it's David Walsh!) "Click the "background.html" link, which will open a developer console -- I did this and went through the process of connecting and then attempting to sign the transaction, saw the pop-up window appear/disappear and... nothing in the dev console. Nothing of interest in network tab. I cleared cookies and local storage in the dev console and tried again, same experience. Nothing useful.

Because I actually needed to use my wallet I took the semi nuclear option and force-quit Brave. This always works to temporarily resolve the issue.

FWIW I'm a dev and am fairly familiar with all of this stuff, happy to help on my end however I can. Thank you all for looking into this.

Update: This disappearing pop-up issue returned on the very next tx I tried, on a different site. lol/sob

[danny-molamola]

The issue is still happening. I have switched from Brave to Chrome, and the pop up closed unexpectedly randomly and the frequency is high when I have many tabs open. The usual fix is either force quit all chrome browsers or unplug the trezor and plug it back again a few times. There is no error in the developer console when the pop up closed. It can be easily reproduced as it basically happens every day.

[inthernar]

The issue is still happening. I have switched from Brave to Chrome, and the pop up closed unexpectedly randomly and the frequency is high when I have many tabs open. The usual fix is either force quit all chrome browsers or unplug the trezor and plug it back again a few times. There is no error in the developer console when the pop up closed. It can be easily reproduced as it basically happens every day.

He's correct. It has been happening consistently. I went over the proposed "solution" provided by @wendys-cats and it still happens. He is also correct, in saying that the only way to resolve this is to quit Chrome outright, then re-open and try again. Sometimes the issue persists even after quitting outright. But most of the time the quitting and restarting of Chrome solves the problem for a TX or two, then it returns.

There is also nothing magical about having to recreate this problem. Just try a few transactions in a row and it will start happening. It is weird that the window call to open the Trezor page immediately force closes. And I can confirm that there are no easily visible errors in the console window.

[ryny24]

This issue is driving me nuts tonight. When will this get resolved?!?!?!?

[Sheesh-bit]

This issue still happens, mostly in the Matic/Polygon Mainnet. The trezor will pops up for a sec and will suddenly close making the transaction unable to process. Tried every solution that is stated here in this thread but nothing works.

[richyboycaldo]

I've been having this problems for months now. I can't believe it hasn't been fixed.

[sime]

This thread has diverged, but if you have hard examples of reproducible cases, please the steps in a manner similar to below. It's important to share exactly which site/application you're experiencing the bug with. Unfortunately, so far I expect it to be a race condition, which is difficult to track down.

Device: Trezor Model T Prerequisites:

1. Setup MetaMask with Polygon network RPC.
2. Add connect hardware wallet (Trezor) to MetaMask
3. Login on this NFT Polygon marketplace. Requires signing a message on the device.

Chrome (MetaMask 10.11.3)

• First attempt: popup appeared and closed immediately
• Second attempt: works as expected

Firefox (MetaMask 10.11.3)

• First attempt: spinner of death
• Second attempt: works as expected

[ANDYVDL]

Just started having the same issue. It tuned a year old a week ago! Happy birthday!

[sime]

@ANDYVDL I'm looking for more detail about this. Could you share which site you are using, currency, exactly which actioned you performed?

[terrymason]

@ANDYVDL I'm looking for more detail about this. Could you share which site you are using, currency, exactly which actioned you performed?

I'm able to produce this any time - roughly 20% of my actions on the trezor are successful. If I reboot my computer, fire up my browser, I'm able to make a transaction. After that my transactions will all fail. I then do a dance of unplugging my trezor and closing / reopening my browser. It can get one, maybe two transactions before it fails.

The symptoms are that:

1. I take an action that requires approval
2. Metamask comes up asking me to approve the transaction (I do)
3. A trezor window will open asking me to approve the transaction, and will close within 2 seconds.
4. The transaction will stay as unconfirmed in metamask until I unplug the trezor, when it will fail with "device disconnected"

Windows 11 21H2 Firefox 98.0.2 trezor model T trezor firmware 2.4.3

Example action: Questing on Defi Kingdoms (harmony)

[terrymason]

I turned off safety checks in my trezor suite and tried again. First transaction was successful Second transaction launched the approval window, which then auto closed. No request for input on the trezor device. Transaction failed.

[ian444]

I'm mostly on Polygon and Harmony and have had 2 PC's running so I can use one while the other restarts to try to get a tx through. One is Linux, the other Win10, one running Chrome, the other Firefox or Chrome. One thing I found to help was to first send a transfer of funds to another wallet, but cancel it at the Trezor. This gets the Trezor and Metamask connected and warmed up. Then might get 2 or 3 tx's through.

I did find the ultimate solution though, I moved my accounts over to a Ledger for defi. It's a breath of fresh air to have stress-free transactions again. Should have done it ages ago. Will keep my Trezors on standby hoping for a fix of these popup windows that Ledger does not need or use. This is such a shame as the Trezors are a nice bit of gear.

[sicalpath]

Fuck Fuck Fuck this fucking issue drives me crazy!!!!!!!!!!!!!!!!

[faxotherapy]

I really sympathize. This bug is truly a nightmare. In my case, I 've been forced to switch from Trezor to buying yet another wallet, i.e. Ledger. Trezor can only be used for long-term storage. Since using Ledger, not a single problem arose with MetaMask (at least on Brave). It's a shame Trezor is in fact not compatible with DeFi. Personal opinion here, but my feelings tell me SatoshiLabs people are Bitcoin maximalists, and hence, despise those who are not. How could it be otherwise since this issue has not truly been addressed yet. After more than a year. Bolstering this is the fact SatoshiLabs is utterly crap in terms of tech support. In one last desperate attempt, I have contacted some crypto media to let them know about this issue (the one raised on this thread), but have not received any reply so far…

[sime]

We recently released an update to Trezor Connect which attempted to squash race condition we thought might be related.

I am aware the bug still exists, it's difficult to track down because it is not reproducible 100% of the time.

Which is why I ask contributors of this thread to continue to provide as much information as possible. e.g. What currency you are using, what action you are performing on what platform. Then maybe we can detect a pattern.

What would be more advantageous is a platform that supports test coins where the bug exists. E.g. Can I reproduce this bug with Testnet Polygon and Harmony coins? That what we can hammer at it without the fear of loosing coins.

[mroz22]

If you could guys please just enter this url into your browser

http://127.0.0.1:21325/status/

And tell me what is your bridge version. My guess is your bridge version is 2.0.27, right?

[artystern]

I literally have the same routine and issues... I get a : sentry-install.js:1 MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 "latest" listeners added. Use emitter.setMaxListeners() to increase limit. Error in my console

@ANDYVDL I'm looking for more detail about this. Could you share which site you are using, currency, exactly which actioned you performed?

I'm able to produce this any time - roughly 20% of my actions on the trezor are successful. If I reboot my computer, fire up my browser, I'm able to make a transaction. After that my transactions will all fail. I then do a dance of unplugging my trezor and closing / reopening my browser. It can get one, maybe two transactions before it fails.

The symptoms are that:

1. I take an action that requires approval
2. Metamask comes up asking me to approve the transaction (I do)
3. A trezor window will open asking me to approve the transaction, and will close within 2 seconds.
4. The transaction will stay as unconfirmed in metamask until I unplug the trezor, when it will fail with "device disconnected"

Windows 11 21H2 Firefox 98.0.2 trezor model T trezor firmware 2.4.3

Example action: Questing on Defi Kingdoms (harmony)

[sime]

@artystern What currency you are using, what action you are performing on what platform.

[artystern]

Every transaction, whether on avax, ethereum or matic is doing this. Usually first one works then second one pop up doesn't appear. Seems like a systematic problem with trezor that most people are experiencing...

For my examples I'm interacting with Aave on Avalanch or Tokemak on Ethereum. Happns every transaction (pop up doesn't appear and nothing happens)

On Wed, May 4, 2022 at 9:20 AM Simon Males @.***> wrote:

@artystern https://github.com/artystern What currency you are using, what action you are performing on what platform.

— Reply to this email directly, view it on GitHub https://github.com/trezor/connect/issues/784#issuecomment-1117372705, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEIIFLGQCU2UXQW56GON5KDVIKBRRANCNFSM4ZR6KTYQ . You are receiving this because you were mentioned.Message ID: @.***>

[KyleF0X]

@artystern What currency you are using, what action you are performing on what platform.

Hi Im also having this issue using Metamask on Firefox with Trezor T. Here's how to reproduce on the pulsechain bridge test net.

• First you will need to get some RINKEBY test net eth from faucet https://rinkebyfaucet.com/
• Then you will need to add the pulsechain test net https://pulsechain.com/
• then get some test pulse from faucet https://faucet.v2b.testnet.pulsechain.com/
• Then use pulseChain Bridge to swap tPLS for pPLS https://pulseramp.com/#/bridge

the first half the the swap goes fine, but then when you go to claim you get an error " "Error Error: Forbidden key path"

here are some errors from inspecting element

If i turn safety checks to "prompt" i get the following

I didnt approve incase it messed things up

[sime]

@KyleF0X Thanks for the detailed report. You need to disable safety checks here because you are signing a testnet transaction with a mainnet derivation path. Which is what your Trezor shows when disabling safety checks. Thus it is a 'forbidden key path'.

You can fix that by selecting 'Trezor testnets' in the hardware wallet connection UI of MetaMask.

Just note, in my experience you cannot have two accounts from the same device, e.g. a standard BIP44 wallet and a 'Trezor testnets'. The latest one overwrites the other. You can always overwrite it back once you are done testing.

[KyleF0X]

@sime Thanks for the reply

You can always overwrite it back once you are done testing.

How would that be done? Would i need to re-enter my private recovery keys?

[sime]

(for people watching this thread, this comment is off-topic)

You can always overwrite it back once you are done testing.

How would that be done? Would i need to re-enter my private recovery keys?

No need to re-enter anything. You are changing the derivation path of the connected Trezor. The UI of MetaMask is confusing, to do this, you need to add a 'new' hardware device, but since you are using the same hardware wallet, it will actually update the derivation path of the previously connected one.

[sirloinfurr]

I'm having this issue with a specific dapp - lyra.finance on optimism network. I was able to sign a transaction on synthetic with my trezor and MM thru optimism. But when I jump into Lyra, the dapps loads very slowly, and the trezor connect pop up window crashes in 2 seconds. I grabbed the url in the popup, and entered it into a new tab, but that didn't get me anywhere

[danny-molamola]

From what I observed, it occurred much more frequently on less powerful machines. When I tried to sign a transaction, from the activity monitor it shows 100% CPU utilization when the Metamask is popping up. If I wait for around 10 sec to let the CPU go back down to a lower % before signing on Metamask, often times the Trezor pop-up can show up after that with no issue.

This issue has been around for so long, and so many people have the same issue. Although it appears randomly, I don't think it is super difficult to reproduce as I had that issue at least a few times basically every day, and the same for the other folks on this thread, and many more who didn't know the existence of this thread. It is amazing that the Trezor team has no intention to help the community and can't reproduce this obvious issue on their end. We can only self-help in this case.

On Sat, May 28, 2022 at 4:55 AM sirloinfurr @.***> wrote:

I'm having this issue with a specific dapp - lyra.finance on optimism network. I was able to sign a transaction on synthetic with my trezor and MM thru optimism. But when I jump into Lyra, the dapps loads very slowly, and the trezor connect pop up window crashes in 2 seconds. I grabbed the url in the popup, and entered it into a new tab, but that didn't get me anywhere

— Reply to this email directly, view it on GitHub https://github.com/trezor/connect/issues/784#issuecomment-1139943792, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMMFDFAPDTQEZBZKUM47B2TVMELARANCNFSM4ZR6KTYQ . You are receiving this because you were mentioned.Message ID: @.***>