-
Notifications
You must be signed in to change notification settings - Fork 31
tBTC dApp reads MEW as MetaMask #251
Comments
Hey @JaviAnibarro, we only support MetaMask right now, though we have Ledger and a few others in the works. I'm moving this from "bug" to "enhancement". If you have examples of dApps that handle MEW or any other favorite wallets of yours well, screens and links would be handy! |
@mhluongo Ok |
That really depends on how your I think supporting web3 generically before explicit multi-wallet support makes sense- otherwise we're excluding non-MetaMask users unnecessarily. What do you think? |
are not one of the points of this dApp is mainly about the usage of MetaMask itself? what is the advantage of allowing non-MetaMask to use it if they can not connect the wallet? another thing that is worrying is, what will happen if it reads another extension(it is possible?)? |
I'm struggling to understand that alternative behavior you'd like to see, before we roll out multi-wallet support. |
@mhluongo well nvm, about dApp supports MEW. |
The issue here as I read it is that you have BOTH Metamask AND MyEtherWallet installed, but when you try to connect to Metamask you get MEW instead, and then it doesn't work. Is that a correct understanding of what you ran into? |
Yes @Shadowfiend , it stuck after MEW came out. |
Description:
When I was trying to connect my wallet on tBTC dApp, it asked me to connect my MetaMask wallet but after I clicked it MEW wallet popup came out. And after clicking the address I have on MEW wallet, it appeared there was nothing happened, it's stuck on that popup.
Steps to reproduce the behavior:
Expected behavior:
tBTC dApp should not show a wrong app when I am trying to connect my wallet
Environment details:
OS: Windows 10 , 64 bit OS
Web Browser: Google Chrome (64-bit)
Wallet: Metamask (Chrome extension), and MEW wallet
The text was updated successfully, but these errors were encountered: