-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
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
CypressError: cy.visit() failed because you are attempting to visit a second unique domain. #600
CypressError: cy.visit() failed because you are attempting to visit a second unique domain. #600
Comments
Likely same issue as this: #380 Cypress fails to parse subdomains in some situations because the rules are quite complex and ever changing. We'd need to update the code in multiple places to be async because the TLD list is quite extensive and couldn't be sent into the browser. |
@brian-mann Do you have a priority on fixing this issue? having multiple level sub domains is quite common, especially in qa/stage environments |
It's likely 2-3 dev days of work, and its not as high as several other things. I can't really comment on when it'd get into the pipeline, but I'll note this issue when it gets started. |
Appreciate it |
…sing tld, handle multiple different subdomains on cy.visit
Released in |
Any update on this issue ? |
@vineetkumar1511 This issue should be resolved in Cypress versions > 1.4.2, if you're experiencing an issue that you think is related, please give us a reproducible example in this issue or open a new issue if unrelated. |
The two domains are formatted as
https://sso.something.mydomain.com and
http://qa.someotherthing.mydomain.com.
This to me seems like they are unique subdomains, not unique domains, and it's preventing me from testing my login page.
The error in Cypress sends me to: https://on.cypress.io/cannot-visit-second-unique-domain which references which sends me to https://docs.cypress.io/api/commands/visit.html which has no information about this error.
The text was updated successfully, but these errors were encountered: