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
Problem: On November 2nd, 2018 MetaMask and other DApp browsers will stop exposing user accounts by default. Instead, dapps must request access using a new provider method: provider.enable(). Detailed info is available here: https://medium.com/metamask/https-medium-com-metamask-breaking-change-injecting-web3-7722797916a8
November 2nd, 2018
provider.enable()
Solution: Fix the code which loads DApp according to instructions from What this means for developers section of the article mentioned above.
What this means for developers
The text was updated successfully, but these errors were encountered:
Merge pull request #142 from poanetwork/support-metamask-change-#139
7f1390e
Support Metamask changes
Merge pull request #162 from poanetwork/backport-#139-into-develop-1.x
449a5cb
Backport #139 into develop 1.x
fernandomg
patitonar
No branches or pull requests
Problem: On
November 2nd, 2018
MetaMask and other DApp browsers will stop exposing user accounts by default. Instead, dapps must request access using a new provider method:provider.enable()
. Detailed info is available here: https://medium.com/metamask/https-medium-com-metamask-breaking-change-injecting-web3-7722797916a8Solution: Fix the code which loads DApp according to instructions from
What this means for developers
section of the article mentioned above.The text was updated successfully, but these errors were encountered: