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
The SignDataItem page is only used for token transfers, while the Sign page is used for both sign() and signDataItem(), but the SignDataItem page doesn't show amounts while the Sign one does.
The BulkSignDataItem page doesn't show amounts like the Sign or SignDataItem do, not even when opening each individual DataItem.
dispatch() will re-request permissions if the upload to Turbo fails. While that's ok, it would be better if either the first AuthRequest item reflects that it failed (despite being accepted by the user) or, even better, the same item is re-used, showing/explaining that it failed and re-requesting permissions to try to post the tx directly.
UI issues:
sign()
andsignDataItem()
, but the SignDataItem page doesn't show amounts while the Sign one does.dispatch()
will re-request permissions if the upload to Turbo fails. While that's ok, it would be better if either the first AuthRequest item reflects that it failed (despite being accepted by the user) or, even better, the same item is re-used, showing/explaining that it failed and re-requesting permissions to try to post the tx directly.Logic (permission/authorization) issues:
decrypt()
andsignMessage()
do not use the Auth popup at all, they do not request permissions.Fixed in Feature:
decrypt()
&signMessage()
permissions + fixdispatch()
requesting permissions twice (when rejected) #582Other issues:
wallet_names.background.ts
throws a "No wallets added" error but doesn't open the Welcome page.The text was updated successfully, but these errors were encountered: