Skip to content
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

Web3 API doesn't process custom error correctly #4389

Closed
ququzone opened this issue Sep 11, 2024 · 0 comments · Fixed by #4454 · May be fixed by #4459
Closed

Web3 API doesn't process custom error correctly #4389

ququzone opened this issue Sep 11, 2024 · 0 comments · Fixed by #4454 · May be fixed by #4459
Assignees
Labels
bug Something isn't working

Comments

@ququzone
Copy link
Contributor

What version of iotex-core image (or code branch) are you using?

latest

What operating system and processor architecture are you using?

What did you do? If possible, provide a recipe for reproducing the error.

If contract emit revert error with custom error, the web3 rpc return 0x, doesn't return error message. Use below cmd can reproduce error on testnet.

cast call 0x2d93899a441a12a694D3b6D1a505931c99fbDDc4 'validPrice(uint256,uint256,bytes)(bool)' 3387000 1726021000 0xd6c42fdc96b0cc44f3d2e3abfb9dbc889d574ab93057e6d04e4d10073106b886261dc7964f8a9f7b59f584fddab8528e758a151a8a09fe4fe0c332f00ba70da31c

What did you expect to see?

(code: 3, message: execution reverted: custom error c9cf1f8b:, data: Some(String("0xc9cf1f8b")))

What did you see instead?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
2 participants