[Sentry] Error: Internal JSON-RPC error.

[sentry-io]

Sentry Issue: METAMASK-X62Q

Error: Internal JSON-RPC error.
  at new EthereumRpcError (node_modules/eth-rpc-errors/dist/classes.js:18:1)
  at getEthJsonRpcError (node_modules/eth-rpc-errors/dist/errors.js:118:1)
  at exports.ethErrors.rpc.internal (node_modules/eth-rpc-errors/dist/errors.js:28:1)
  at parseResponse (node_modules/@metamask/eth-json-rpc-middleware/dist/fetch.js:100:1)
  at <anonymous> (node_modules/@metamask/eth-json-rpc-middleware/dist/fetch.js:57:1)
...
(1 additional frame(s) were not displayed)

[gauthierpetetin]

Events in past 14 days: 731

[gauthierpetetin]

The error indicates an internal JSON-RPC error with MetaMask. In this particular case, the error mentions that the transaction reverted without a reason string. This often means that the smart contract's function was called with parameters or in a state that caused it to fail, but no specific error message was provided by the contract.

[danjm]

There are actually multiple different errors being grouped in here. Examples:

  "code": -32603,
  "message": "Internal JSON-RPC error.",
  "data": {
    "code": -32000,
    "message": "header not found"
  },

  "code": -32603,
  "message": "Internal JSON-RPC error.",
  "data": {
    "code": -32602,
    "message": "Block with such an ID doesn't exist yet"
  },

  "code": -32603,
  "message": "Internal JSON-RPC error.",
  "data": {
    "code": -32000,
    "message": "cannot query unfinalized data"
  },

  "message": "Internal JSON-RPC error.",
  "data": {
    "code": -32000,
    "message": "missing trie node 1c3f42345fbf34a12934730eb5ff6cd2e3283aaa3d929cc2485542e0bc702161 (path ) state ******************************************3d929cc2485542e0bc702161 is not available, not found"
  },

It seems that these cases are all a result of errors coming from the network provider.

As a first step with this task, we should probably focus on having the errors properly reported in sentry, with the data.message being what is reported to sentry instead of all these different errors being grouped under Internal JSON-RPC Error. Then we can figure out which can be ignored, which require special handling, and which indicate a bug that needs to be fixed.

[sentry-io]

Sentry issue: METAMASK-X7G7

[gauthierpetetin]

Next step suggested by @danjm would be a good topic to prioritise in a future Sentry sprint.

[sentry-io]

Sentry issue: METAMASK-X7T3

[sentry-io]

Sentry Issue: METAMASK-X7MY

[sentry-io]

Sentry Issue: METAMASK-X8DR

[gauthierpetetin]

Related issue: #5907

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity in the last 90 days. It will be closed in 45 days if there is no further activity. The MetaMask team intends on reviewing this issue before close, and removing the stale label if it is still a bug. We welcome new comments on this issue. We do not intend on closing issues if they report bugs that are still reproducible. Thank you for your contributions.

[gauthierpetetin]

Example steps to reproduce in this issue (switching network multiple times): #25785

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity in the last 90 days. It will be closed in 45 days if there is no further activity. The MetaMask team intends on reviewing this issue before close, and removing the stale label if it is still a bug. We welcome new comments on this issue. We do not intend on closing issues if they report bugs that are still reproducible. Thank you for your contributions.