Closed DJilanov closed 1 year ago
Hey @DJilanov, the provider.connect
resolves when a session is created.
From the code snippet, I'm seeing you're already listening to display_uri
so when this event is emitted, you should use that URI to pair with a wallet. Once the session is approved, the .connect
will resolve with it.
Describe the bug Once we fire the "connect" method of the '@walletconnect/universal-provider', the promise is never completed and there are no errors into the terminal
SDK Version (if relevant)
To Reproduce Code snipped to reproduce the behavior:
All of the logs I got
Expected behavior The method to finish its promise and return <SessionTypes.Struct | undefined>. If needed i can prepare a demo app that reproduces the problem.
Smartphone (please complete the following information):