Metamask-extension: MetaMask does not work with Tor browser

Created on 11 Jul 2018 · 23Comments · Source: MetaMask/metamask-extension

Bounty: currently MetaMask is throwing errors in the Tor browser that prevent the extension from loading. To fill the bounty, get MetaMask's most recent version (4.8 at time of writing) to work in Tor.

MM is successfully installed, but when I click on the MM icon, the small window shown is completely empty.

Tor 7.5.6, Metamask 4.8.0.

Screenshots are bellow:
clipboard01
clipboard02

N01-needsResearch has bounty

Source

vbresan

All 23 comments

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

__This issue now has a funding of 0.06 ETH (29.93 USD @ $498.83/ETH) attached to it.__

If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
Questions? Checkout Gitcoin Help or the Gitcoin Slack
$29,599.51 more funded OSS Work available on the Gitcoin Issue Explorer

gitcoinbot on 17 Jul 2018

This is probably duplicate for #4502.

jreginsson on 18 Jul 2018

Interestingly enough, errors only appear on first opening after installation. Then, nothing.

tor_mm_blank

uivlis on 18 Jul 2018

@vbresan do you see this error consistently, or just after installation?

bdresser on 18 Jul 2018

Consistently.
clipboard01

vbresan on 19 Jul 2018

I will match the bounty here to double it to 0.06 + 0.06 ETH = 0.12 ETH.

owocki on 19 Jul 2018

❤1

I could be wrong but I believe this issue is coming from Firefox 52(Tor browser's version) as it does not have the listener onConnectExternal available. I'm still researching alternatives.

anonrose on 20 Jul 2018

@anonrose we've had some other recent issues with a blank screen Firefox - check #3963 or #4502

bdresser on 20 Jul 2018

Issue Status: 1. Open 2. Cancelled

__Work has been started__.

These users each claimed they can complete the work by 4 months, 1 week from now.
Please review their action plans below:

1) ajnauleau has started work.

Seems like a similar issue too:

Version 4.x no longer compiling to es5 #3505

Will apply my patch to the issue and if the bug still appears, will look into changing the `present-react' settings

Learn more on the Gitcoin Issue Details page.

2) otaviocapila has started work.

Analyze the errors in Dev tools
Search for then in code
Fix them
Create tests to prevent errors from happening
Submit

Learn more on the Gitcoin Issue Details page.

gitcoinbot on 20 Jul 2018

@ajnauleau Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

[x] warning (3 days)
[ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

gitcoinbot on 24 Jul 2018

Just going off the error in the image this doesn't look related to #3505 but it wouldn't hurt to test this out with the latest changes on develop now that #4812 is merged.

whymarrh on 24 Jul 2018

The build in the PR I just requested built to support Firefox 52 which is what Tor uses #4873. Although this resolved the issue for Chrome, I think something else is going on with Tor.

ajnauleau on 25 Jul 2018

[x] warning (3 days)
[ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

gitcoinbot on 30 Jul 2018

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

@ajnauleau due to inactivity, we have escalated this issue to Gitcoin's moderation team. Let us know if you believe this has been done in error!

[x] warning (3 days)
[x] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

gitcoinbot on 2 Aug 2018

Still looking over this, would like to have the weekend to work through it. @gitcoinbot

ajnauleau on 2 Aug 2018

😕1 👍1

This might be a decent workaround until the issue is addressed:

I was able to get v.3.13.8 to work in Tor. All newer versions have the blank screen issue.
Link to 3.13.8:
https://addons.mozilla.org/en-US/firefox/addon/ether-metamask/versions/?page=1#version-3.13.8

I was able to send/receive and interact with a dapp.

dpazdan on 12 Aug 2018

@ajnauleau & @dpazdan, I've snoozed Gitcoin bot for you guys :). Was there any follow up on the exploration work?

frankchen07 on 23 Aug 2018

👍1

To workaround this, you can detect the user's MetaMask version.

To get the current user's MetaMask version, you can use the method web3.version.getNode(console.log), or directly from the provider object like this:

web3.currentProvider.sendAsync({"jsonrpc":"2.0","method":"web3_clientVersion","params":[],"id":67}, console.log)

danfinlay on 4 Sep 2018

👍1

I have just upgraded to Tor 8.0 and MetaMask 4.9.2. So far everything seems to be working fine.

vbresan on 6 Sep 2018

Tested on Tor 8.0 and confirmed working 👍

dpazdan on 6 Sep 2018

🎉1

Yahoo! Closing this for now - please ping if the issue returns.

Heads up @ajnauleau @OtavioCapila the bounty will be cancelled as well.

bdresser on 6 Sep 2018

🎉1

Issue Status: 1. Open 2. Cancelled

__The funding of 0.06 ETH (plus a crowdfund of 1.0 EOS worth $5.76) (13.33 USD @ $222.15/ETH) attached to this issue has been cancelled by the bounty submitter__

Questions? Checkout Gitcoin Help or the Gitcoin Slack
$19,157.68 more funded OSS Work available on the Gitcoin Issue Explorer

gitcoinbot on 6 Sep 2018

The most recent version of Tor & MM 6.3.2 seem to work. You get a blank popup for MetaMask, but then you can click the MM toolbar icon to approve what would have been on the popup and it works.

mm_tor