Bitcoin Forum

I need help please. I'm trying to download metamask extension on Chrome but it keeps giving me an error.

'Variable $1$ used but not defined.'

What is this and how could I solve it? Thank you.

What are you trying to do before you shown that error? Does it show when opening up the extension? I tried to search around, especially on Metamask's GitHub and its community support site, but there is no such kind of error that others had, maybe you should also ask it there.

One thing to consider is to make sure you install it from legitimate sources, and if it still got an error, try to reset the extension, and reimport back your wallet seed phrase. If that is no luck, I think completely resetting the browser might be the option. I tried Metamask on Chrome, but couldn't reproduce the error on the latest version.

haven't experience such this error before, pls try reinstall the wallet from original source and import your seeds, if same after that best option is using another browser, recently chrome indicate some errors that should be reported to devps, However contact MM support if you have continuously rising same issue bro.

Are you sure you are downloading a legit metamask extension? This is quite surprising cause ita rarely to see such error and I dont understand the
 Statement regarding variable $1 but not defined. Is it some sort of payment? Cause its a free download. Which one you used pc or mobile device? Can you share us some images to check it properly. Oh edited.

Your rank still newbie. But can you explain much in details.

I searched about your problem and this was also asked in Turkish language in google chrome community.

The package is invalid. Details: 'Variable $1$ used but not defined.' (https://support.google.com/chrome/thread/209626177/paket-ge%C3%A7ersiz-ayr%C4%B1nt%C4%B1lar-variable-1-used-but-not-defined?hl=tr)

I just used the google translate for the thread and one recommended answer there in green said that it is the apps problem and will need to wait for its developer/publisher to fix it. The source of the answer was also on that link and I just also translated it. You can check it for reference since the thread was just also posted 19 hours ago as of typing.

Thanks for your help. It was the exact same error and they said it's a problem on metamask's end. Now it's fixed I could install it without a problem.

Don't mention it. It's great that it has been fixed by the publisher just as that guy have answered on that thread. Well, it seems that this thread has already served the purpose and you're able to download what you're trying to download. Maybe for future reference, someone might find this thread and will refer if ever the same error exists as they download some extension. You can go ahead and lock the topic as it's solved your concern.

Actually it wasn't fixed right after. I downloaded it to another browser. But now I can also install it on Chrome.
They fixed this issue later.

I thought that it was fixed already. But that's good to know that it's fixed just as you said. It's easier and more compatible with using the browser extension to Google Chome.
Although it eats a lot of ram and space in your PC. If you can use any other browser like Brave or Firefox or even Edge, well that's on you for what's more convenient to you in using.

Basing up on this link
https://community.metamask.io/t/i-cant-install-metamask-from-chrome-extensions/24991

Once you do get that error on what you have stated.
Its been said "try change Chrome’s language to English (USA)"

Dont know if it works but it seems it does because there are people who do have on the same problem just like yours.

It's not due to the browser or anything from user end but from the metamask site and I reckon now its been fixed so just use it as before but as said earlier it's kind of weird error while installing so the developers team need to be more active about finding the bugs and errors because it's one of the most preferred wallet for eth and tokens so they need to keep their standards to that level.

It was already English. The problem was different and devs fixed it.

Locking this thread now.