greymass / anchor-link-browser-transport Goto Github PK

Users who have a pending signing request, and subsequently perform another action that queues up a second signing request, will receive a 410 error code on the request.

We may want to catch this 410 and display a useful error to the user that they should start/restart/reconnect their wallet to receive the pending requests before performing additional requests.

During the Resource Provider sampling process, we can catch errors involving the transaction before its sent to the users wallet. These aren't resource errors, they are errors with the contract the user is trying to interact with. Currently these errors are returned as part of the API response but not surfaced to the user. The current flow is:

• User starts transaction.
• Transport checks resource requirements.
• If there's an error during sampling, the API returns the error to the transport.
• The transport currently just proceeds without cosigning and without prompting the error.
• The user signs using their wallet, and it often fails from resource issues.
• The user powerup/rents/etc and tries again, and now they see the error.

We should change the transport to surface the errors that occur during sampling. The flow should be:

• User starts transaction.
• Transport checks resource requirements.
• If there's an error during sampling, the API returns the error to the transport.
• The transport prompts the error to the user and the transaction flow is halted.
• The user corrects the error (if possible) and resubmits, the transaction is cosigned and successful.

Hello. I'm having trouble setting up anchor-link on a React + Typescript app.
I'm using the same code in a Vue app, and everything is working fine.

I'm able to login and the the user's session, however when I try to use the transact function, I'm getting this error:

Uncaught (in promise) TypeError: Cannot assign to read only property 'prepareStatusEl' of object '#<BrowserTransport>'
    at BrowserTransport.showLoading (app.js:9870:30)
    at LinkChannelSession.showLoading (app.js:10784:40)
    at Link.transact (app.js:11298:15)
    at LinkChannelSession.transact (app.js:10797:37)
    at app.js:31552:24
    at step (app.js:31363:19)
    at Object.next (app.js:31293:14)
    at app.js:31265:67
    at new Promise (<anonymous>)
    at __webpack_modules__../resources/js/Domains/Wallet/useWallet.ts.__awaiter (app.js:31244:10)

It references the line 366 of anchor-link-browser-transport's index.ts

Any advice on how can I proceed?

Thanks in advance

It's been requested that the app itself can listen for the close event if the user cancels the modal. We could probably expose some sort of API or data that the app could listen to for the status of the modal.