Matic Network Error: The method does not exist / is not available._Last 30 Days: 70K

[sentry-io]

We seem to be getting a lot of “method does not exist” from matic network RPC endpoints. Would be great if this error included what method exactly was attempted that was not available in this case.

Sentry Issue: METAMASK-K790

Error: The method does not exist / is not available.
  at "stack": "Error: The method does not exist / is not available.\n    at new i ( (metamask/common-0.js:18:148782)\n    at s ()
...
(2 additional frame(s) were not displayed)

Last 30 Days: 70K

[danfinlay]

We can increase severity if people report interrupted service on matic network. For now this might be a silent background error, but would be good to add an improved error message so we could diagnose errors like this.

[Gudahtt]

I'm not sure how we should handle cases like this, where a custom network doesn't match Infura's set of supported methods exactly. Is it even a bug? Maybe we should collect reports on these via Segment/Mixpanel so that we understand what methods these networks support, and keep these errors out of Sentry altogether.

[danfinlay]

Seems like if we could collect one instance per method per RPC we would have enough data to act or recommend action.

[seaona]

It seems that due to the new re-grouping algorithm, this issue is pointing to another error now: "stack": "Error: Internal JSON-RPC error.\n at new i ((metamask/common-0.js:18:148782). Header not found

We have already an open issue for addressing the header not found problem.

For the error indicated in this description The method does not exist / is not available. I only see a couple of entries and they are on Mobile side, so I believe this issue could be updated to low prio now. @hilvmason @danjm what do you think?

[Swader]

Confirming my inability to bridge assets (wETH) on any of the available bridges, with this error being thrown on attempt. Using desktop.

[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.

[github-actions]

This issue was closed because there has been no follow up activity in the last 45 days. If you feel this was closed in error, please reopen and provide evidence on the latest release of the extension. Thank you for your contributions.