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
Right now there is now way to know if a transaction has been rejected by the API.
It would be useful if calls such as openContractCall would include an onFailure callback or similar that gets fired whenever there is an issue.
The text was updated successfully, but these errors were encountered:
yeah, this is something i've run into in the past, it's so hard to debug onFailure seems like it might make sense, was thinking about how it'd be nice to have these three:
onSuccess - meaning it's a correct transaction, and it's been broadcast onFailure - failed for some reason onCancel - user ends session before completing any action
i'm not sure this would make sense for message signing though, but it could
I think this makes a lot of sense too, it'd be nice to be able to target each state with a specific strategy on the UI/UX side.
Right now there is now way to know if a transaction has been rejected by the API.
It would be useful if calls such as
openContractCall
would include anonFailure
callback or similar that gets fired whenever there is an issue.The text was updated successfully, but these errors were encountered: