Closed jmlon closed 4 years ago
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?
This led me to discover the LoadingContainer, but it looks like it's still not available outside of the legacy version of Drizzle? :-(
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.
No worries @alexfisher . I was doing that before the lockdown :) I'm going to go ahead and close this issue.
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
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.