Set chain id based on the env variable #831
Draft
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
Define the chain id based on the env variable and use it in the `connect` function from wagmi. We have separate builds for each network and we do not change chain dynamically so we can use hardcoded value in `connect` function. If we use the `useChainId` hook from wagmi it will return the cached chain id. So when for example we were locally testing a dapp on the testnet and then changed the env variables to integrate with the mainnet, the wagmi used the cached chain id for the testnet and we couldn't connect to the wallet.
✅ Deploy Preview for acre-dapp-testnet ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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.
Define the chain id based on the env variable and use it in the
connectfunction from wagmi. We have separate builds for each network and we do not change chain dynamically so we can use hardcoded value inconnectfunction. If we use theuseChainIdhook from wagmi it will return the cached chain id. So when for example we were locally testing a dapp on the testnet and then changed the env variables to integrate with the mainnet, the wagmi used the cached chain id for the testnet and we couldn't connect to the wallet.