We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Even though the user has an account connected in MM, the extension returns an empty array when trying to get the connected accounts.
Luckily, Chromium functions as a workaround.
For context:
web+urbitgraph://group/~halbex-palheb/uf-public/graph/~halbex-palheb/general-4066/170141184505929554797657732808611725312
The text was updated successfully, but these errors were encountered:
With version 9.0.0 of the MetaMask browser extension, we stopped providing the window.web3 API to websites
https://metamask.zendesk.com/hc/en-us/articles/360053147012-MetaMask-Legacy-Web3
Sorry, something went wrong.
metamask: resolve connected accounts
e47013d
This change adds the recommended approach to get a user's connected account address, as well as fallbacks for older versions of Metamask. This resolves #1073 See: https://docs.metamask.io/guide/sending-transactions.html#example https://metamask.zendesk.com/hc/en-us/articles/360053147012-MetaMask-Legacy-Web3
Just ran into this myself today.
tomholford
Successfully merging a pull request may close this issue.
Even though the user has an account connected in MM, the extension returns an empty array when trying to get the connected accounts.
Luckily, Chromium functions as a workaround.
For context:
web+urbitgraph://group/~halbex-palheb/uf-public/graph/~halbex-palheb/general-4066/170141184505929554797657732808611725312
The text was updated successfully, but these errors were encountered: