CODEWITHSUNDEEP
eventsethereumsolidityweb3jsabi
Ferit
Ferit

Reputation: 9737

Uncaught Error: Returned values aren't valid, did it run Out of Gas?

I'm listening to events of my deployed contract. Whenever a transaction gets completed and event is fired receiving the response causes following error:

Uncaught Error: Returned values aren't valid, did it run Out of Gas? at ABICoder.push../node_modules/web3-eth-abi/src/index.js.ABICoder.decodeParameters (index.js:227) at ABICoder.push../node_modules/web3-eth-abi/src/index.js.ABICoder.decodeLog (index.js:277)

Web3 version: 1.0.0-beta36

Metamask version: 4.16.0

How to fix it?

Upvotes: 10

Views: 14234

Answers (8)

Silvio Guedes
Silvio Guedes

Reputation: 1274

The solution for me was changing of provider. With Infura the error is gone, but with Alchemy is still happening.

Upvotes: 1

Yilmaz
Yilmaz

Reputation: 49759

This happened to me on my react app.

I deployed to contract to Ropsten network, but metamask was using the Rinkeby aaccount. So make sure whichever network you deployed, metamask should be using account from that network.

Upvotes: 2

7FigureSwagger
7FigureSwagger

Reputation: 115

Before even checking your ABI or redeploying, check to make sure Metamask is connected to whichever network your contract is actually deployed too. I stepped away and while i was afk Metamask logged out, I guess I wasn't watching closely and I was connected to Ropsten when I working on localhost. Simple mistake, wasted an hour or so trying to figure it out. Hope this helps someone else out!

Upvotes: 2

Carlos Jafet Neto
Carlos Jafet Neto

Reputation: 891

This can also happen when the MNEMONIC value from Ganache is different from the one you have in your truffle.js or truffle-config.js file.

Upvotes: 0

Naveen S Adhikari
Naveen S Adhikari

Reputation: 1

Please check your Metamask Login, This issue is generally populated when you are either log out of the Metamask or worse case you have 0 ether left at your account.

Upvotes: 0

Ivan Zakharov
Ivan Zakharov

Reputation: 173

Throws the same error when inside a transaction it generates different events with the same name and the same arguments. In my case, this was the Transfer event from ERC721 and ERC20. Renaming one of them solves this problem, but of course this isn't the right way.

Upvotes: 6

Ramesh babu
Ramesh babu

Reputation: 89

Try the command truffle migrate --reset so that all the previous values are reset to their original value

Upvotes: 9

Ferit
Ferit

Reputation: 9737

This is a bug in web3js, discussed here.

And the following change fixes it (source):

patch-package
--- a/node_modules/web3-eth-abi/src/index.js
+++ b/node_modules/web3-eth-abi/src/index.js
@@ -280,7 +280,7 @@ ABICoder.prototype.decodeLog = function (inputs, data, topics) {


     var nonIndexedData = data;
-    var notIndexedParams = (nonIndexedData) ? this.decodeParameters(notIndexedInputs, nonIndexedData) : [];
+    var notIndexedParams = (nonIndexedData && nonIndexedData !== '0x') ? this.decodeParameters(notIndexedInputs, nonIndexedData) : [];

     var returnValue = new Result();
     returnValue.__length__ = 0;

Edit: Also downgrading to web3-1.0.0.beta33 also fixes this issue too.

Upvotes: 4

Related Questions