-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Conflict between Injected Web3 Providers #468
Comments
This may be a repeat of a similar issue: web3-react issue: Uniswap/web3-react#300 |
Closing this issue since it's a duplicate and be fixed with @4skinSkywalker approach to custom connectors. |
We're can I find the code snippet |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you have both Coinbase Wallet and Metamask Chrome extension, clicking on the Metamask option causes both extensions to prompt for account access.
I believe this is a result of the Coinbase browser extension functioning as an injected Web3 provider, much like Metamask. There needs to be some kind of check in the code that prevents this from happening. Please advise.
Happy to propose a pull request if we can get to the bottom of this.
The text was updated successfully, but these errors were encountered: