You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Submitting a transaction with an invalid method name or argument name results in two error messages being returned to the 'lamdenWalletTxStatus" event listener. This makes it more difficult for the developer perform error handling and inform the user the status of their request. Both the events contain same information, but it is laid out differently (see attached files).
As a work around I could ignore the second event with the "detail.data.txBlockResult.errors" attribute as it is not common to the tx errored to send tx events, but I wanted to check if this was by design and if there is something I am missing.
Submitting a transaction with an invalid method name or argument name results in two error messages being returned to the 'lamdenWalletTxStatus" event listener. This makes it more difficult for the developer perform error handling and inform the user the status of their request. Both the events contain same information, but it is laid out differently (see attached files).
As a work around I could ignore the second event with the "detail.data.txBlockResult.errors" attribute as it is not common to the tx errored to send tx events, but I wanted to check if this was by design and if there is something I am missing.
argument_error2.txt
argument_error1.txt
method_error2.txt
method_error1.txt
The text was updated successfully, but these errors were encountered: