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
For example, developers don't want to use a native modal for the connection wallets.
For example needs to connect only with WalletConnect after clicking on the Connect button, without any modals.
You will use the following code after the Connect button is clicked:
When the user clicks on the Connect button the first time the WalletConnect modal with QR code opens, so it works as expected.
If the user clicks on the close button and clicks on the Connect button again, nothing happens.
When the user clicks on the Connect button the second time if the previous time connection was canceled, the WalletConnect modal with QR code should be opened.
Steps To Reproduce
No response
Onboard Version
2.2.9
Node Version
16.15.0
What browsers are you seeing the problem on?
No response
Relevant log output
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Current Behavior
For example, developers don't want to use a native modal for the connection wallets.
For example needs to connect only with WalletConnect after clicking on the Connect button, without any modals.
You will use the following code after the Connect button is clicked:
When the user clicks on the Connect button the first time the WalletConnect modal with QR code opens, so it works as expected.
If the user clicks on the close button and clicks on the Connect button again, nothing happens.
Look at the video:
https://user-images.githubusercontent.com/101503007/171252895-405d42fb-c529-4f81-8066-43bcb2b66830.mov
Expected Behavior
When the user clicks on the Connect button the second time if the previous time connection was canceled, the WalletConnect modal with QR code should be opened.
Steps To Reproduce
No response
Onboard Version
2.2.9
Node Version
16.15.0
What browsers are you seeing the problem on?
No response
Relevant log output
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: