Timeline for How to decode error that occurred while calling a write method on ink contract, on the client side?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 9, 2023 at 5:45 | vote | accept | Non-named | ||
| Jan 8, 2023 at 8:11 | answer | added | vivek sharmapoudel | timeline score: 1 | |
| Jan 7, 2023 at 15:01 | comment | added | kriko.eth | good point, if you do not return Err, do you get such error too? | |
| Jan 6, 2023 at 9:01 | comment | added | P.Ossun | BTW I am assuming you are calling a read-only function as query (but the question title said otherwise). If you process as a tx you can do like this: Best practise | |
| Jan 6, 2023 at 8:57 | comment | added | P.Ossun | I guess your error doesn't come from your contract but rather from the runtime (mostly pallet-contract). What you can do is get the tx hash of your transaction and in polkadot js UI developer > RPC calls > contracts - call dry-run it to get the proper Error enum variant | |
| Jan 5, 2023 at 15:59 | answer | added | Maario | timeline score: 1 | |
| Jan 5, 2023 at 10:59 | comment | added | Non-named | Yep. It still says the same error for every error that I throw on the contract | |
| Jan 5, 2023 at 10:12 | comment | added | kriko.eth |
if the contract return Err(Error::VestingAmountTooLow), does it still say CalleTrapped?
|
|
| Jan 5, 2023 at 9:49 | history | asked | Non-named | CC BY-SA 4.0 |