Skip to content
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

MetaMask Pop-up Window Always Unexpectedly Closes Right Before Entering PIN on Hardware Wallet #10896

Closed
faxotherapy opened this issue Apr 17, 2021 · 26 comments · Fixed by #23164
Labels
area-hardware hardware-trezor needs-research release-11.14.0 Issue or pull request that will be included in release 11.14.0 Sev2-normal Normal severity; minor loss of service or inconvenience. team-accounts team-hardware-wallets type-bug

Comments

@faxotherapy
Copy link

faxotherapy commented Apr 17, 2021

Describe the bug
After clicking the Confirm button from MM extension, a pop-up window usually opens to allow me entering my Trezor PIN. Unfortunately, the pop-up window, for unknown reasons to me, unexpectedly and immediately closes before allowing me to enter my PIN. This is new, I never encountered such issue. In an attempt to isolate issue, I disabled pop-up blocking feature of Firefox, but problem persists. In fact, even though with enabled pop-up blocking feature of Firefox, MetaMask always opened a pop-up window.

Steps to reproduce (REQUIRED)
Steps to reproduce the behavior, libraries used with version number, and/or any setup information to easily reproduce:

  1. Approve/Swap on, e.g., Uniswap
  2. Click on Confirm button in MM extension

A new browser window should open (instead of a tab even tough tab function has been activated in Firefox), but closes immediately preventing me from entering PIN on hardware wallet.

Expected behavior
In the old days, before ver. 1.9.3, everything worked fine. Pop-up window remains open.

Screenshots

MM-Trezor-Issue

Browser details (please complete the following information):

  • OS: MacOS 10.14.6
  • Hardware Wallet: Trezor 1.9.4
  • Browser: Firefox 87
  • MetaMask Version: 9.4.0

Additional context (Error Messages, etc.)

The issue seems to appear when Trezor has not yet been “logged in” with PIN before interacting with MM.

@faxotherapy faxotherapy changed the title Pop-up MetaMask Window Unexpectedly Closes MetaMask Pop-up Window Always Unexpectedly Closes Right Before Entering PIN on Hardware Wallet Apr 17, 2021
@bradwbradw
Copy link

bradwbradw commented May 25, 2021

This is happening to me all the time now too, I basically can't interact with any Dapps at all through my Trezor :(

Even with my Trezor already unlocked, the popup (with url "connect.trezor.io/8/popup.html") appears for about one second, then just closes automatically.

I'm getting the problem even if it's already unlocked.

Browser details (please complete the following information):

OS: MacOS 10.15.7
Hardware Wallet: Trezor 1.10.0
Browser: Brave Version 1.24.86
MetaMask Version 9.5.4

@bradwbradw
Copy link

I just noticed there's an issue at trezor-connect too: trezor/connect#784

@onetwoitsthewu
Copy link

having the similar issues as well as other errors including "unable to claim interface" and "device was disconnected." other times the pop up window just shows "loading" forever. any updates on this? all of my crypto are effectively stuck on my trezor right now as i can't do anything with my funds.

@HeroHann
Copy link

The issue is still not resolved.
I opened an issue with Trezor: trezor/trezor-firmware#1762
Answer: Metamask uses the wrong derivation path for testnet. Seems Metamask needs to fix this.

This issue is open for some time. Any ETA on it? With this state no Trezor user can test the Rinkeby Swap Feature on Metamask with the Trezor.

In relation to this see also: trezor/connect#784

@MrSavvyCoins
Copy link

After also suffering with the phantom disappearing Approval window for months, I've come to terms with needing to import the wallet back into my old Chrome browser. I've failed to escape our Google overlords.

@GaylordTuring
Copy link

I can report that I have the very same problem using my Ledger. It works to send ETH or tokens, but when interacting with a smart contract in some more advanced way, the pop-up window just closes itself.

@0xJatto
Copy link

0xJatto commented Sep 26, 2021

Any update from the MM team?

@staringispolite
Copy link

Can confirm I'm still getting this on a new Trezor. Trezor Suite 21.10.2, Mac OS 11.4, Chrome 94.0.4606.81
Ad Block Plus is disabled. Same happens on Brave

@lostintime101
Copy link

Also experiencing the same issue. Super frustrating and expensive!

@MorrisonWill
Copy link

I'm getting "Popup error: Unable to establish connection with iframe" using a trezor model T and metamask on arch linux firefox.

@anomtttt
Copy link

anomtttt commented Nov 1, 2021

I'm getting "Popup error: Unable to establish connection with iframe" using a trezor model T and metamask on arch linux firefox.

I can't take credit for this, I found the answer on another forum. The solution ..... use MS Edge and install the Metamask extension . Solved my problem. Meta really need to sort their sh8t out.

@MrSavvyCoins
Copy link

MrSavvyCoins commented Nov 13, 2021 via email

@theorbital
Copy link

I have tried chrome as well as microsoft edge and the pop up window is still automatically closing on me and I am unable to complete my transaction.

@AlexJupiter AlexJupiter added hardware-ledger Sev1-high High severity; partial loss of service with severe impact upon users, with no workaround. Sev2-normal Normal severity; minor loss of service or inconvenience. and removed Sev1-high High severity; partial loss of service with severe impact upon users, with no workaround. labels Feb 17, 2022
@darkwing
Copy link
Contributor

darkwing commented Apr 8, 2022

I was able to reproduce this with no special steps on Mac:

  1. I added a new account on my Trezor Model T
  2. Tried sample send to myself
  3. Window pops up very briefly, then closes before I can take any action.

The background console shows the following error:
FKP

Some more debugging info about the transaction:
TrezorTo

Sign and Personal Sign both work, yet sending a transaction does not.

@sime
Copy link
Contributor

sime commented May 19, 2022

Shot in the dark idea: Does the problem persist when Passphrases are disabled in Trezor Suite?

@AlexJupiter
Copy link
Contributor

Are people still experiencing this issue?

@sime
Copy link
Contributor

sime commented Apr 13, 2023

@AlexJupiter related thread on Trezor: trezor/connect#784

@aspiers
Copy link

aspiers commented May 17, 2023

In my case I finally traced it to MetaMask's restricted site access preventing the Trezor popup from opening:

#17607 (comment)

@plasmacorral
Copy link
Contributor

Freshly reported in issue #19476 impacting both Chrome and Brave

@lostintime101
Copy link

The browser window closing unexpectedly issue still happens almost every time I use my Trezor with MM.
The only way I can get it to work is to restart the computer, then it will work for the first transaction, possibly a second transaction also if I'm lucky, after that, the same popup disappearing continues. The only thing I've found that helps is a full restart.
I'm using the latest version of MM and Trezor app/firmware, MM extension is set to "all sites", Brave chromium is up to date, ad blockers turned off.
It's really frustrating.

@jonatascm
Copy link

Is there any update on this issue? It still happens when you use trezor and chrome.

@Hannsek
Copy link

Hannsek commented Sep 8, 2023

Trezor Connect was updated and the issue is fixed. Metamask, however, has to manually update npm package otherwise it won't work. :/

@mkingp
Copy link

mkingp commented Sep 22, 2023

I just started having this issue today on Chrome and Edge.

Even though I have already updated the Metamask Chrome Extension, Trezor Suite.

I have also tried setting the Metamask Extension's setting to Connect to All Sites. It didn't work.

Basically can't do any transaction with my Trezor now, as it is surprisingly hard to find a Metamask alternative that supports Trezor.

Copy link
Contributor

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.

Copy link
Contributor

github-actions bot commented Feb 4, 2024

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.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 4, 2024
@legobeat legobeat reopened this Feb 26, 2024
@github-actions github-actions bot removed the stale issues and PRs marked as stale label Feb 26, 2024
@github-project-automation github-project-automation bot moved this to To be fixed in Bugs by severity Feb 26, 2024
@github-project-automation github-project-automation bot moved this from To be fixed to Fixed in Bugs by severity Mar 18, 2024
@metamaskbot metamaskbot added the release-11.14.0 Issue or pull request that will be included in release 11.14.0 label Mar 26, 2024
@metamaskbot
Copy link
Collaborator

Missing release label release-11.14.0 on issue. Adding release label release-11.14.0 on issue, as issue is linked to PR #23164 which has this release label.

@angelcheung22 angelcheung22 added this to the Q1 2024 milestone Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-hardware hardware-trezor needs-research release-11.14.0 Issue or pull request that will be included in release 11.14.0 Sev2-normal Normal severity; minor loss of service or inconvenience. team-accounts team-hardware-wallets type-bug
Projects
Archived in project