Metamask-extension: DOMException Failed to execute 'postMessage' on 'Window'

[bicep]

I'm aware of #1280 (I'm running local server on port 3000) and #5333 (I'm not so sure what this is but it was fixed?). Apologies in advance if this was covered already, I cant seem to find it.

Describe the bug
A clear and concise description of what the bug is.

I've set up web3 so that I'm using the latest version of web3 (1.0.0 beta 43) that sets the provider from the metamask's web3.

const provider = window.web3.currentProvider; provider.enable(); const web3 = new Web3(provider);

I've currently deployed a contract on Rinkeby and am trying to get a simple public variable called manager using contract.methods.manager.call(), but I'm getting this DOMException in Chrome:

[YukiOta]

I have a same issue... Any solutions for this?
I posted stack exchange here

[phamhieu]

I fixed this issue by running npm install. I'm using web3:1.0.0-beta.37

[chentschel]

Same issue with [email protected] .Solved installing web3:1.0.0-beta.37

[YukiOta]

Solved by installing web3:1.0.0-beta.37

Thank you so much!
@phamhieu @chentschel

[serapath]

Not sure, but i have the same issue https://play.ethereum.org/play-editor/
It seems to work when running on localhost during development with a dev server.

The error happens when you DEPLOY the contract

Any clue what this is about?

[ninabreznik]

Any news about how to resolve this issue?

[ninabreznik]

[szerintedmi]

Getting the same with beta47 :(

[ninabreznik]

I also get this now with another Dapp. First Dapp uses ethers.js and the second one web3.js :(

[willfsays]

Also hitting this issue with 1.0.0-beta.48 when attempting to perform a web3.currentProvider.send({ method: 'personal_sign', params: params, from: _account});

[Philipid3s]

Same issue with 1.0.0-beta.48 - solved by installing the beta.37

[nicholaspai]

also resolved this by switching from beta.48 to beta.37

[arnigudj]

same here, resolved this by switching from beta.48 to beta.37... hoping that this will be resolved in beta.49

[kumavis]

Opened an issue on web3.js with live reproduction demo https://github.com/ethereum/web3.js/issues/2528

[kumavis]

@wfoster232 this does not look correct, from should be encoded in the params

web3.currentProvider.send({ method: 'personal_sign', params: params, from: _account});

[kumavis]

conclusion from https://github.com/MetaMask/metamask-extension/issues/6262#event-2202563870:

for [email protected] the web3.eth.personal.sign requires a 3rd parameter, a password string (unused in metamask)

if you were using a callback before, it accidently includes the callback in the params in place of the password string. the callback is not json serializeable, thus throwing the error.

[kumavis]

based on comments above, sounds like there are some additional issues (error on deploy, etc)

[jamesmorgan]

Ye I get this using Nuxtjs and metamask - any ideas? Will try to downgrade to 1.0.0-beta.37

[nickgeoca]

Have tried 1.0.0-beta.37 and other versions, even re-cloning and rebuilding the server, but keep getting the same errors.

  try { c = await MyContract.deployed(); } catch (e) {console.log(e);}

Firefox error

TypeError: "this.provider.sendAsync is undefined"
                   sendAsync contract.js:24
                   sendAsync requestmanager.js:80
                   get property.js:116
                   detectNetwork contract.js:512
                   Promise es6.promise.js:177
                   detectNetwork contract.js:503
                   deployed contract.js:451
                   _callee5$ TokenPollInterface.js:119

Chromium error

Uncaught (in promise) DOMException: Failed to execute 'postMessage' on 'Window': function (err, result) {
if(result && result.id && payload.id !== result.id) return callback(new Error(...<omitted>... } could not be cloned.

[ldub]

Also getting this error when using web3.eth.net.getId() or web3.eth.getBlockNumber() on 1.0.0-beta.48. Downgrading to 1.0.0-beta.37 does fix it but using an old version isnt a viable solution. It would be great to see an explanation of this issue.

In my setup, this error only occurs after I run a --mode production webpack build. when running with webpack-dev-server --mode development, this error doesnt happen.

[tomsoft1]

Same issue here, any news....?

[W3stside]

beta.37 is consistently the most stable Web3 beta. Though it still has the memory leak from #1648

[einaralex]

I was using web3beta.48 when I ran into this problem, it worked to downgrade to beta.37. Now I upgraded to beta.55 and that works.

[Kapn]

I ran into this problem running beta.55. I downgraded to beta.37 as suggested above and everything is good to go now.