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
Currently, if WalletConnect SignClient hangs on initialization/requesting URI, it will cause Discovery to get stuck in a loading state on mobile. The most common scenario is that the projectId is invalid
Expected Behavior
Should not get stuck. Failure to initialize WalletConnect should not brick FCL Discovery. That being said, we do generally need to wait for WalletConnect, as pre-fetching URI is necessary for deep linking. Minimum solution is to add a timeout.
Steps To Reproduce
Try using FCL Discovery with bad WC project ID on mobile.
Environment
n/a
What are you currently working on that this is blocking?
No response
The text was updated successfully, but these errors were encountered:
Current Behavior
Currently, if WalletConnect SignClient hangs on initialization/requesting URI, it will cause Discovery to get stuck in a loading state on mobile. The most common scenario is that the projectId is invalid
Expected Behavior
Should not get stuck. Failure to initialize WalletConnect should not brick FCL Discovery. That being said, we do generally need to wait for WalletConnect, as pre-fetching URI is necessary for deep linking. Minimum solution is to add a timeout.
Steps To Reproduce
Try using FCL Discovery with bad WC project ID on mobile.
Environment
What are you currently working on that this is blocking?
No response
The text was updated successfully, but these errors were encountered: