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
Note this can be reproduced only after this other PR is merged: #301
There's a "strange" behavior when making another request like near_signIn right after the connect has been approved as shown in the video below:
walletconnect-issue.webm
What I suspect is that this line ModalStore.close() in SessionProposalModal is executed a bit later then the new session_request for near_signIn has been made. As shown in the video right after clicking "Approve" the request for near_signIn shows for a split second and the modal gets closed without giving a chance to either approve or reject.
If we add some waiting time between the connect and another request in a dApp then the modals open and close correctly, but this is not an ideal solution
// this is some dummy pseudo codeawaitsignClient.connect(params)awaitwait(1000)// wait for 1 sec// make a new requestawaitsignClient.request(params)
The text was updated successfully, but these errors were encountered:
Note this can be reproduced only after this other PR is merged: #301
There's a "strange" behavior when making another request like
near_signIn
right after theconnect
has been approved as shown in the video below:walletconnect-issue.webm
What I suspect is that this line ModalStore.close() in SessionProposalModal is executed a bit later then the new
session_request
fornear_signIn
has been made. As shown in the video right after clicking "Approve" the request fornear_signIn
shows for a split second and the modal gets closed without giving a chance to either approve or reject.If we add some waiting time between the
connect
and another request in a dApp then the modals open and close correctly, but this is not an ideal solutionThe text was updated successfully, but these errors were encountered: