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
{{ message }}
This repository has been archived by the owner on Sep 14, 2023. It is now read-only.
So this code breaks if I cancel the transaction, even though it's in a try catch block
The initial fix was to add await await sent.transactionStatuses
but then it will be stuck forever, unless I add return true
if (status === 'ready') {
setStatus(...);
return true;
}
unfortunately this creates a new issue, now the first transaction will be called twice in a row
I receive a popup two times, after confirming the second one, only then it proceeds further
The text was updated successfully, but these errors were encountered:
the only way to mitigate this for now is to use the initial code without await or return true and add .rehandle(is(SignerError), (error) => error.access('inner')) after .transactionStatuses
At least this way my catch captures the error and the whole page doesn't turn red
though I thought error.access('inner') would return specifically that portion of the error object
instead I get this
'sent' is an ExtrinsicStatusRune here
So this code breaks if I cancel the transaction, even though it's in a try catch block
The initial fix was to add await
await sent.transactionStatuses
but then it will be stuck forever, unless I add
return true
unfortunately this creates a new issue, now the first transaction will be called twice in a row
I receive a popup two times, after confirming the second one, only then it proceeds further
The text was updated successfully, but these errors were encountered: