Handling of absence eth_chainId on Web3 provider side #207
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ghost
assigned 
|
Deploy preview for kind-kilby-95344f processing. Building with commit 47c232a https://app.netlify.com/sites/kind-kilby-95344f/deploys/5c9e01c79e88e3000864f322 |
Pull Request Test Coverage Report for Build 438
💛 - Coveralls |
patitonar
reviewed
Mar 29, 2019
patitonar
approved these changes
Mar 29, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If a web3 provider used by the wallet does not support
eth_chainIdcall the messageWallet account rejected by user. You need to unlock your wallet. Please refresh the page and click 'Connect' button in your wallet popupappears. It does not clarify the issue.That's why it is suggested to handle errors appeared when
getChainIdcalled and provide more precise explanation what it is necessary to do to address the issue.