-
Notifications
You must be signed in to change notification settings - Fork 16
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
Errors on the ccipRecieve side are ambiguous #15
Comments
Thank you for the nice words, @Andriy-Kulak, we appreciate that! If possible, I would also like to hear later why the initial setup wasn't a smooth experience for you and how we can improve the Chainlink Local docs But now let's solve this issue first :) You are right, this is a generic error returned from the CCIP contracts when they call the Can you please paste me here the piece of code where you send the CCIP message from the Sender contract and the |
Hi @andrejrakic ! I'm facing the same error in |
Issue is resolved for me after following this - https://docs.chain.link/ccip/tutorials/ccipreceive-gaslimit. Increased the gasLimit. |
Yeah I was able to resolve the issue. I was just saying that the error is ambiguous & can have some additional clues to pinpoint potential culprits (i.e., check gas limit, check the receiver code, etc.) |
First off, thanks for the hard work on this repo!
I got the local testing to work, but it took a little bit of effort (& a ton of console.logging 😅 ) to get it to work.
The main reason is that once the receiving contract was able to get the message, there were a few bugs on my code (i.e I wasn't decoding properly, set gas limit too small, etc.) For any error on Receiver contract, no matter, what it was, I got the same exact error below.
Not sure the best way to have the error pinpoint exact culprit, but in the meantime maybe the error can at least be more descriptive. I.e. Something along the lines.
There is likely a code error somewhere on receiver side, also check the gasLimit, etc.
this would save people a little bit of time in future.The text was updated successfully, but these errors were encountered: