You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
💡 Are you able to provide enough information to be able to reproduce your issue locally?
I can provide enough details to reproduce my issue on local environment.
Synpress version
3.7.1
Node.js version
18.16.0
Operating system
Win10
Run mode
Cypress + Synpress (as plugin)
CI platform (if applicable)
No response
Are you running your tests inside docker? (if applicable)
This issue could be related to docker.
What happened?
When I use the cy.setupMetamask and cy.changeMetamaskNetwork API, I get an error saying "Provided chain was not found" if the provided chain is Holesky. Additionally, the check link provided in the error message cannot be opened. What should I do?
ps: chainId = 17000
What is your expected behavior?
I expect to successfully add or switch to the Holesky network.
How to reproduce the bug.
it("Setup Metamask and import the required wallets", () => {
cy.setupMetamask(SECRET_WORDS, NETWORK_HOLESKY, PASSWORD)
cy.changeMetamaskNetwork(NETWORK_HOLESKY)
cy.visit("/ethereum/reward")
cy.switchChain(NETWORK_HOLESKY)
cy.wait(2000)
})
🔎 Have you searched existing issues to avoid duplicates?
🧪 Have you tested your code using latest version of Synpress?
💡 Are you able to provide enough information to be able to reproduce your issue locally?
Synpress version
3.7.1
Node.js version
18.16.0
Operating system
Win10
Run mode
Cypress + Synpress (as plugin)
CI platform (if applicable)
No response
Are you running your tests inside docker? (if applicable)
What happened?
When I use the
cy.setupMetamask
andcy.changeMetamaskNetwork
API, I get an error saying "Provided chain was not found" if the provided chain is Holesky. Additionally, the check link provided in the error message cannot be opened. What should I do?ps: chainId = 17000
What is your expected behavior?
I expect to successfully add or switch to the Holesky network.
How to reproduce the bug.
Relevant log output
The text was updated successfully, but these errors were encountered: