ganache and metamask not working fine

[monica-gahlawat]

inpage.js:1 MetaMask - RPC Error: [object Object] {code: -32603, message: "[object Object]", data: {…}, stack: "Error: [object Object]↵ at a (chrome-extension:…eogaeaoehlefnkodbefgpgknn/background.js:1:1206771"}

[kumavis]

not sure what the underlying layer is, but obviously there is a problem with the error serialization

possibly related MetaMask/eth-json-rpc-middleware#20

[shahafn]

Might be related to the bug I encoutnred in #8385 ?

[monica-gahlawat]

Error is RPC -32603

…

On Thu 23 Apr, 2020, 5:26 AM shahafn, ***@***.***> wrote: Might be related to the bug I encoutnred in #8385 <#8385> ? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#8374 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANI26JC6OYFHY2HN5EXX353RN572RANCNFSM4MNDPGCQ> .

[wbt]

I am seeing something similar where the issue I came here to report was not the cause of the underlying error (I knew before triggering the transaction that it would fail a require statement), but the way MetaMask fails to show any error details such as the reason thrown in require():

[adrianmcli]

If I had to guess, it looks like MetaMask calls .toString() on the error object containing the revert string, causing it to return [object Object] instead of the underlying error object with revert string.

[Gudahtt]

Thanks for the report! Unfortunately the original issue here doesn't have enough information for us to investigate further. Please re-submit the bug including relevant details such as the MetaMask version, OS and OS version, browser version, as well as more information about the situation you were in when this occurred.

The error serialization issues talked about here are quite concerning on their own though. The ticket #8975 already tracks that problem though, and has a lot more information in it, so I'm going to close this for now and use #8975 for tracking the serialization issues.