Closed amolmaid closed 6 years ago
I suspect it might be in here "details":[]
if the API endpoint had started nodeosd with --verbose-http-errors
.. I'm not sure what the trade-off is for enabling it and why it is off by default.
There is some example code parsing details in another issue, we can find it if you need it.
Ohh great, Thank you for your response, this suffice my need here, I am able to get the precise error msg now. So thank you :)
I suspect it might be in here
"details":[]
if the API endpoint had started nodeosd with--verbose-http-errors
.. I'm not sure what the trade-off is for enabling it and why it is off by default.There is some example code parsing details in another issue, we can find it if you need it.
wow~ thank you again~
I am using eosjs in my dAPP, where I am executing few transactions like issue and transfer. While doing so lets say I/user does something wrong while doing transfer
{"code":500,"message":"Internal Service Error","error":{"code":3050003,"name":"eosio_assert_message_exception","what":"eosio_assert_message assertion failure","details":[]}}
While at the same time, nodeos returns me the precise error message like,
SO do we have anything which will give me this kind more accurate error message like nodeos, so I can render it on page by which user could correct his mistake ?