Same experience here. MetaMask shows a message about the window.web3 API being removed form the add-on but that's not the issue. I found more discussion on the issue here: https://community.brave.com/t/metamask-stop-working-with-brave-browser/269031/11

I hope this gets some priority because MetaMask can't connect to any web3 site right now as far as I can tell.

A lot of complaints regarding MetaMask in Community.

In one of the threads, a user (Luckys) shared a workaround that worked for a few users.

Hi managed to sort mine by going into Brave settings and turning off (Load crypto wallets on startup) then restarting browser hope this may help some of you.

it worked for some of us try it!

Community thread:
https://community.brave.com/t/metamask-stop-working-with-brave-browser/269031

Can confirm that this worked for me - thank you Tonev for the fix. Hopefully this solve will work for all others with this issue as well

A lot of complaints regarding MetaMask in Community.

In one of the threads, a user (Luckys) shared a workaround that worked for a few users.

Hi managed to sort mine by going into Brave settings and turning off (Load crypto wallets on startup) then restarting browser hope this may help some of you.
it worked for some of us try it!

Community thread:
https://community.brave.com/t/metamask-stop-working-with-brave-browser/269031

Verification passed on

• Verified there is no option for Load crypto wallet on startup
• Verified when MM is installed, default provider is set to MM with or without flag being enabled

Verification passed on

• Verified there is no option for Load crypto wallet on startup
• Verified when MM is installed, default provider is set to MM with or without flag being enabled

Verification passed on

• Verified there is no option for Load crypto wallet on startup
• Verified when MM is installed, default provider is set to MM with or without flag being enabled

Greetings,
My MetaMask extension was working just fine in Brave Browser with web3 sites until I got hit with the new V1.31.87 (Oct 19, 2021) today. Now web3 sites are not working, I can't connect with MetaMask and log into my account on these sites, like Rarible.com using my MetaMask. MetaMask wallet is no longer an option, even though if I just log into MetaMask and it shows my wallet is connected to that site. Also if I'm not logged into MetaMask and I select "Connect Wallet" on the web3 site, the "Crypto Wallet" login pops up instead of the MetaMask login pop up.

@Billyv1 what is the default provider set to?

No what is Default cryptocurrency wallet provider set to?

Hi,

Everything has been working fine since early August but since a few days ago I can't connect Metamask to my Ledger Nano S through Brave. It does not trigger any action and that previously annoying "Making sure it's you" windows security pop-up does not pop either.
Please get back to me how this can be fixed?

MetaMask requires you to use Ledger Live for Ledger support. But I believe they're improving that now. We support Ledger without Ledger Live fwiw.

Bumping as you guys need to resolve this. Plenty of MetaMask users on Brave.
MetaMask 10.16.1 is not working for all the defi sites I was previously just a month or so ago. This is Brave [Version 1.40.113 Chromium: 103.0.5060.114 (Official Build) (64-bit)]

@rjaym mind adding an example where it's failing or adding more detailed steps? I ran through MM on current nightly and it worked fine with a bunch of sites.

@rjaym mind adding an example where it's failing or adding more detailed steps? I ran through MM on current nightly and it worked fine with a bunch of sites.

I am unable to use your nightly builds.

@rjaym mind adding an example where it's failing or adding more detailed steps? I ran through MM on current nightly and it worked fine with a bunch of sites.

Also, sorry there really are no detailed steps or special setup as far as I know, it's just Brave on Windows 10 and MM with the versions stated above, although I am using the Avalanche network and not Ethereum.

Ok thanks for the update. I'll give it a try on Avalanche network. Any specific Defi sites that you are facing problems with?

Ok thanks for the update. I'll give it a try on Avalanche network. Any specific Defi sites that you are facing problems with?

All defi sites, they show connected in MM with a green status icon, but the site itself shows as disconnected to MM. Also yes I have tried changing the "Default cryptocurrency wallet" option many times (all options) but nothing has allowed the sites to understand that MM is installed and connected. All the defi sites prompt me to connect to a wallet as if MM is not installed.

If you're changing between wallets you might want to clear cookies on the site in question

Not working for me either - updated Brave too, but still doesn't connect. Works on Chrome but not Brave

MetaMask - Version - 10.16.2
Brave - Version 1.41.96 Chromium: 103.0.5060.114 (Official Build) (64-bit)]

If you're changing between wallets you might want to clear cookies on the site in question

I cleared cookies to no avail. The only other hint I can come up with at this time is that it appeared that MM may have updated (automatically as usual?) after which the defi sites would no longer connect. I think I recall getting the MM notification/hint (because I think MM autoupdated as stated) that I could turn on dark mode, which I did, after which the issue began.

Not working for me either - updated Brave too, but still doesn't connect. Works on Chrome but not Brave

MetaMask - Version - 10.16.2 Brave - Version 1.41.96 Chromium: 103.0.5060.114 (Official Build) (64-bit)]

What is your "default wallet" set to in brave://settings/wallet ?
What happens when you try to connect? Does Brave Wallet come up or MetaMask?

fwiw I've deeply investigated dozens of these types of reports and every time it ends up being that there are multiple wallet extensions installed that are competing for window.ethereum and causing problems with each other. The claims that it works in Chrome is because the same set of extensions aren't installed on Chrome.

I'm still willing to investigate further, but for the past couple years I believe every investigation has led to no real issue.

Setting your wallet to None in brave://settings/wallet will make it so Brave does not try to insert window.ethereum at all.
Setting it to Brave Wallet (Prefer extensions) makes it so Brave does insert window.ethereum but allows it to be overwritten.

@bbondy thanks for the reply!

Checking my "default wallet" was the first thing I did - it is set as 'NONE' - but still having the issue.

Cleared all cache, cookies, site data, hosted app data in Brave ( Clear Browsing Data - All Time )

When going to Pancake Swap ( https://pancakeswap.finance/ ) for example the site loads - as soon as I click "connect wallet", the screen goes black and inspecting I can see a number of errors in the console.

The one that sticks out the most based on your other 2nd comment was:
MetaMask: 'ethereum.send(...)' is deprecated and may be removed in the future. Please use 'ethereum.sendAsync(...)' or 'ethereum.request(...)' instead.
For more information, see: https://eips.ethereum.org/EIPS/eip-1193

Pancake Swap - Screenshot:
https://i.imgur.com/ny8yNvX.png

On a separate DAPP similar thing happens - click on 'Connect Wallet' - screen turns black, this time if I inspect no ethereum error
https://i.imgur.com/LQhrnku.png

Thanks for reading! 🙏🏼

An update, I ended up uninstalling the MM extension and reinstalling and now it is working again after I importing my old wallet using the 12 word recovery phrase.
This implies some LocalStorage or cached data from the extension itself was causing an issue. Unfortunately, the workaround can be quite cumbersome.
I am still not sure where the blame should lie though to be honest, MM or Brave, it's unclear.

Honestly the MM is extension is sometimes just buggy. What makes it worse is that other extensions often conflict with it as they compete fro window.ethereum. There is absolutely no logic specific to MetaMask in Brave so Brave works the same as Chromium and Chrome. Now if you go and try on Chrome, you have a new profile so you might not reproduce. Just like if you use Brave and create a new profile you probably won't reproduce as well.