-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Page crashes when injected provider is used. #1447
Comments
Tom from Portis here, please let us know if there is any way we can help. |
Hi, As far as I can see uniswap is serving 5.1.0, and this should be fixed on 5.1.3 |
we have this issue with a number of wallets, it was caused by switching to a newer version of ethers. this workaround should fix it for at least coinbase wallet |
crash starts on line 305 here https://unpkg.com/browse/@ethersproject/[email protected]/src.ts/json-rpc-provider.ts |
Thanks @moodysalem I have tried on coinbase wallet & status browser and I get an empty page when accessing app.uniswap.org, but unlike before no error is thrown (though page is completely blank) The last request made is this one:
(I have only looked at the logs on status as I can't access them on the coinbase wallet). Thanks for the prompt response. |
@ricmoo we had to workaround a bug in the latest ethers provider package @5.1.1 with this commit the problem is the web3provider constructor super calls json provider constructor super calls base provider constructor which calls detectNetwork before the result is that json rpc provider does not work if you pass in 'any' network |
should be fixed in interface |
@moodysalem That was fixed in 5.1.3. The current version is 5.1.4. Updating to the latest version should solve this. Let me know if there are still issues after updating. :) |
Bug Description
Attempting to use an Inejected provider (wallet), the page crashes (white screen with error in console).
Steps to Reproduce
Expected Behavior
Page doesn't crash.
Additional Context
I suspect that something in the code is making assumptions about what the injected provider provides beyond what is standard. In particular, it seems to want to get network information from the injected provider but is failing.
There are a few issues here:
The text was updated successfully, but these errors were encountered: