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
{{ message }}
This repository has been archived by the owner on Mar 11, 2024. It is now read-only.
When I switch accounts in Metamask, the information in both, AccountData and drizzleState still reflect the information of the moment the page was rendered for the first time.
The following component shows how to reproduce the problem and see the right values as returned by the web3 API.
Just familiarizing myself with Drizzle box over the last week and it looks like it just makes a direct web socket connection to the local blockchain and doesn't check for another web3 provider that's already existing?
Wow, so the lockdown must have me brain dead or this just wasn't obvious. I had to comment out the customProvider line in drizzleOptions.js to get it to start attempting to connect to Metamask.
Wow, so the lockdown must have me brain dead or this just wasn't obvious. I had to comment out the customProvider line in drizzleOptions.js to get it to start attempting to connect to Metamask.
Thanks @alexfisher this took me an embarrassingly long time to figure out aswell
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When I switch accounts in Metamask, the information in both, AccountData and drizzleState still reflect the information of the moment the page was rendered for the first time.
The following component shows how to reproduce the problem and see the right values as returned by the web3 API.
The text was updated successfully, but these errors were encountered: