[Bug]: Chrome console error related to lockdown-run.js and lockdown-more.js

[ghost]

Describe the bug

• lockdown-run.js:17
  Lockdown failed: TypeError: At intrinsics.Object.groupBy expected boolean not function
  at isAllowedPropertyValue (lockdown-install.js:1:53384)
  at isAllowedProperty (lockdown-install.js:1:53807)
  at visitProperties (lockdown-install.js:1:55095)
  at isAllowedPropertyValue (lockdown-install.js:1:53041)
  at isAllowedProperty (lockdown-install.js:1:53807)
  at visitProperties (lockdown-install.js:1:55095)
  at lockdown-install.js:1:55523
  at repairIntrinsics (lockdown-install.js:1:144597)
  at lockdown-install.js:1:145462
  at lockdown-run.js:4:3

• lockdown-more.js:99
  lockdown-more.js:99 Protecting intrinsics failed: ReferenceError: harden is not defined
  at lockdown-more.js:69:13
  at Set.forEach ()
  at protectIntrinsics (lockdown-more.js:44:22)
  at lockdown-more.js:97:5

Steps to reproduce

When I turn on the MetaMask extension and open any web page, an error appears in the console.
These errors disappear when MetaMask is disabled.

Error messages or log output

No response

Version

11.0.0

Build type

None

Browser

Chrome

Operating system

MacOS

Hardware wallet

No response

Additional context

No response

[anaamolnar]

Hello, @unsiu. Thanks for reporting! Do you have other crypto wallets and extensions in the browser? Did this start occurring when updating the extension? Thank you!

[ghost]

Hello, @unsiu. Thanks for reporting! Do you have other crypto wallets and extensions in the browser? Did this start occurring when updating the extension? Thank you!

I only have this one cryptocurrency related extension. These errors were reported with the last version (v10.35.1).

[x1ongzhu]

I'm facing the same error on macos.
Chrome version: 117.0.5938.62
Extension version: 11.0.0

[krasezzza]

The same issue on my machine.

OS: Windows 11 Pro
Chrome version: 117.0.5938.62
Extension version: 11.0.0

[RAMTO]

Same here

[ochikov]

Same here:
OS: Mac OS Monterey 12.6.1 (21G217)
Chrome version: 116.0.5845.110
Extension version: 11.0.0

[fditrapani]

Same here:
MAC OS: 13.5.2
Chrome: 117.0.5938.62
Extension version: 11.0

[huytq03]

same here

[SandiRizqi1503]

I just solved this issue by Uninstall Metamask and VPN Google Chrome plugin

[krasezzza]

I just solved this issue by Uninstall Metamask and VPN Google Chrome plugin

How do you use MetaMask wallet interactions in a dApp then?

[woutersteven]

Same error message, also using Chrome v117.

Chrome 117.0.5938.63
Win 10 Pro
MetaMask v11

I disabled the MetaMask plugin instead of removing it.. that removes the error as well.

[githubarj]

same getting the error too

[rick-liruixin]

same getting the error too

[francesco-gaglione]

I just solved this issue by Uninstall Metamask and VPN Google Chrome plugin

How do you use MetaMask wallet interactions in a dApp then?

How is it so difficult for you to understand that this is an issue with MetaMask? You giving responses thumbs down because the helpful responses don't answer your noob question of "h0w Do U uze metamask..." is worthy of public humiliation. If you're such a poor web3 developer that you don't have other wallet extensions, well, then it's clear Darwin's survival of the fittest has made it to the digital realm.

I agree with you that perhaps there are many other alternatives to at least continue to develop. And I agree that the question posed that way makes no sense at all. But it's not exactly as you say. There are situations in which there are non-technical limitations for which one is forced from the outside to use a certain wallet. And therefore the problem must be solved in all cases. I don't change my car every time it runs out of petrol, I solve the problem by refueling. So if this is a problem with the metamask extension and does not depend on factors external to metamask this issue should be resolved. There are products in production that can only use metamasks and cannot find themselves unable to connect the wallet overnight. And I'm in a similar case

.....so if any maintainers or contributors read this, please let us know if we can provide you with additional information about the bug to analyze and resolve it asap.

[csmartinsfct]

I just upgraded chrome to 117.0.5938.62 and started seeing this error as well, wasn't there before (unsure what version I was on tbf). MetaMask still seems to work though.

[krasezzza]

I just upgraded chrome to 117.0.5938.62 and started seeing this error as well, wasn't there before (unsure what version I was on tbf).

It seems to be an issue between Chrome and MetaMask because I notice the same behavior after browser update.

[WebDevTalha]

Hello, In my Dapp everything was working fine so far but when I added the web3js package to my dapp to make my contract read function work, it kept showing the same error in my console, so I want to know if there will be any problem with my dapp due to this error? Should I ignore this error?

[anaamolnar]

Hey @danjm. Could you please take a look? Thanks!

[mattimatt]

Yup just removed meta mask and error goes away. For me it also appeared after updating chrome.

[lucaslee129]

I have the same problem and it came up just before. What is the reason and what is the solution?

[d1v1ng1sC00l]

Me too. Error on Brave and Chrome.

[FranRom]

Same here

[mujtabashamas]

same came after updating chrome.

[tadpole2077]

Details relating to metamask lockdown.js issue and root cause on stackoverflow : https://stackoverflow.com/questions/76393186/what-is-causing-the-warning-removing-intrinsics-arrayprototype-toreversed-in

Its the anti-pershing detect feature on metamask (v10.31.1), that isnt aligned with latest ES2023 prototypes, so all those new native methods throw warnings with MetaMask 10.31.1

Seems to be resolved with MetaMask 11.0.0

Those warning are going to occur with Chrome 110 and higher (latest version is 116) and MetaMask 10.31.1 , 110 is when ES2023 support/compatibility was activated.

[federicosan]

@weizman please look into this as you resolved an issue that is mentioned here I think this two may be related.

[federicosan]

Chrome update 117.0.5938.88 for desktop and the errors persist, (I am editing my question because it was not clear)

[roudra323]

Facing the same issue.
Browser - > Brave (1.58.124) -> Chromium (117.0.5938.62)
MetaMask -> 11.0.0
Windows -> 11

[top-comengineer]

This will be fixed in an upcoming release of MetaMask (v11.1.0).

For now, this error can be safely ignored and should not prevent you from running MetaMask.

I am also facing the same issue.
Thank you for your clarification, @FrederikBolding
Could you let me know when will be probably the upcoming release time of the Metamask?
Thanks again.

[omarabid]

Bumping this. The wallet functions fine but this pollutes the console + any debugging/tracing tool you have out there.

[Fikunmi01]

I just solved this issue by Uninstall Metamask and VPN Google Chrome plugin

Thanks bro you just saved me from stressing much haha

[dankelleher]

About one in ten sites are currently broken for me because of this. Removing metamask fixes them.

[hacenbarb]

I'm facing the same issue

[Hiker-Hope]

Same 🙃

[samyan]

same here. I've Metamask plugin.

[eriksonlizandro]

No need to remove Metamask just do this

[etsraphael]

Same issue here, the only trick right now is to disable it. But that's not even a solution.

[karlwerxz]

uninstalled metamask :)

[FrandeSUG]

Same Hereだよもう

[aiiiden]

Same issue here

[ennioVisco]

For gods sake don't post new comments if you have nothing relevant to add.
Just subscribe to the issue, if you want, react to previous comments, and then wait for updates from the devs, instead of triggering notifications to hundreds of people for just saying "me too".

[elliotWoas]

Thanks for the report. I had the same problem, I reinstalled Metamask with a VPN to fix the bug

[PRChain]

Get the same error, always use a VPN.

[moazzamgodil]

I think the issue is fixed. I recently updated to version 11.1.2, and now there are no more error logs, so everything seems to be working fine.

[Muurtaja]

The issue has been resolved in version 11.1.2. Thank you all for your assistance!

This issue can now be considered closed.

[GimpMaster]

Looks like the Edge (chrome) extension hasn't been up dated in the store yet. That is currently at 11.0.0

[vunh195]

Looks like the Edge (chrome) extension hasn't been up dated in the store yet. That is currently at 11.0.0

same

[rheza]

what is my options now ?, I cant access my wallet.

[nazar-pc]

Still happening with 11.7.3 version of extension in Chromium 123.0.6267.0 (nightly). Metamask is not loading, making it useless.

[yahdielo]

it says it solve, but im having the same problems updated chrome and metamask and still getting this