-
Notifications
You must be signed in to change notification settings - Fork 619
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wallet Connect not exposing error.data when custom error is thrown #1000
Comments
Hi @makoto, Thank you for the detailed report on this issue regarding the new custom error handling introduced in Solidity v0.8.4, as well as the live reproduction which is a huge help. @iljadaderko will be looking into a fix for this today, in the meantime is it possible for you to share the source/repo for |
Hi @bkrem . Thanks for taking a look.
|
Hi @bkrem let me know if there's anything we can help |
Hi @bkrem just checking on the progress. |
Hi @makoto, Was great meeting you today in person! I just had a chance to test #1151 against the The steps are:
Let us know if you're still seeing issues around error forwarding, and sorry again about the wait on this 🙏 |
Describe the bug
Wallet Connect does not seem to return the original error from json rpc endpoint when the smart contract throws custom error which was introduced in Solidiy 0.8.4 https://blog.soliditylang.org/2021/04/21/custom-errors/
This leads to ethersjs unable to decode custom error which ccip-read relies on showing ENS offchain record
SDK Version (if relevant)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
When I put the following console.log at [
checkError
function of ethers js] (https://github.com/ethers-io/ethers.js/blob/master/packages/providers/src.ts/json-rpc-provider.ts#L52), The provider via Infura (which we connect during read only mode) returnederror.data
on the left side of screenshot whereas wallet connect doesn't have any data on the right side of the screenshot below.Screenshots
If applicable, add screenshots to help explain your problem.
The text was updated successfully, but these errors were encountered: