-
Notifications
You must be signed in to change notification settings - Fork 5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failing to load events on a new provider #2761
Comments
Have you tried reloading the page after switching the provider (if it isn't automatically)? |
Yes, hard reloading didn't solve it. Neither did switching users and coming back to the original user. |
Interesting to note: I am not finding this buggy behavior on Brave. |
Hey @alex-miller-0, is this still an issue for you? We did some things that may have fixed this. |
We could really use reproduction steps here, or we should maybe close it in favor of #2978. |
Sorry for the delay. Here are the reproduction steps (only in Chrome):
I haven't worked on that project in a while and can't seem to get my workflow working, so I can't verify if it's still there or not. I think it's okay if you close this for now and I'll let you know if I see it again. Good work squashing all those log bugs! |
Certainly not all yet, some still out there for sure. Thanks for the follow up! |
I am building an application that requires me to interact with a provider, switch providers, and pull events from the new provider (e.g. localhost:7545 -> localhost:8545). After switching providers, I get zero events about 90% of the time (I can see logs of the events in a separate web3 console). The only way to get the events in Metamask seems to be restarting Chrome entirely. What's strange is that once in a while, things work as expected, but that's probably 1 in 10 tries.
Expected Behavior
Upon switching providers, I expect the new provider to collect events from a contract that has emitted them.
Actual Behavior
No events are found from e.g.
allEvents.get()
after switching providers until I reboot Chrome.Browser Used
Chrome 63.0
Operating System Used
macOS Sierra
The text was updated successfully, but these errors were encountered: