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
As you can see, isConnected becomes true on route change above
Also, when connected to a wallet, switching between pages loses the activeConnector field and becomes undefined for some reason. That bug can also be repro'd on the link above.
Expected Behavior
isConnected remains false even after route change
activeConnector to be defined on route change after wallet connection established
Steps To Reproduce
No response
Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)
This issue has been locked since it has been closed for more than 14 days.
If you found a concrete bug or regression related to it, please open a new bug report with a reproduction against the latest wagmi version. If you have any other comments you can create a new discussion.
Is there an existing issue for this?
Package Version
0.3.0
Current Behavior
isConnecting
returns true on client-side route transition, even when you don't have a wallet connected.Repro here:
https://codesandbox.io/s/vigilant-firefly-guj5zt
As you can see, isConnected becomes true on route change above
Also, when connected to a wallet, switching between pages loses the
activeConnector
field and becomes undefined for some reason. That bug can also be repro'd on the link above.Expected Behavior
isConnected
remains false even after route changeactiveConnector
to be defined on route change after wallet connection establishedSteps To Reproduce
No response
Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)
https://codesandbox.io/s/pedantic-agnesi-r8dn22
Anything else?
isConnected bug:
https://user-images.githubusercontent.com/15570714/166090160-86c4ee0e-a3c6-4fe5-bc1f-34da25f1412c.mp4
activeConnector bug:
https://user-images.githubusercontent.com/15570714/166090161-e553db9c-0e47-4fdf-85dd-47cd22d0f917.mp4
The text was updated successfully, but these errors were encountered: