Replies: 2 comments 6 replies
-
Is that a custom error? Are you including the custom error in the ABI? |
Beta Was this translation helpful? Give feedback.
5 replies
-
@ricmoo, any update on that? is that a bug? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
It seems that errors in the underlying contract do not always propagate with the sepcific error code.
For example, when using
swapExactTokensForTokens
and usingtx.wait
, the contract can return the error codeINSUFFICIENT_OUTPUT_AMOUNT
, but throughethers
library, I get the genericCALL_EXCEPTION
which indicates nothing about the actual error.I would expect the original error from the underlying contract to be exposed in the exception details.
Alternatively, the important information that helps diagnose the problem should be present in the exception details
Beta Was this translation helpful? Give feedback.
All reactions