-
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
Tests running in Firefox still fails (on MAcOS) when a browser is already opened #6380
Comments
@flotwig I wonder if the message should state something like “no other instances of Firefox launched, prior to opening cypress” As it is not just related to two Firefox instances launched by cypress, but an ff instance being launched first by any means. Which would be nice to resolve in a future release if possible |
@YOU54F Weird. I wrote it like that because all open-mode sessions use the same profile and on Linux, I am able to run my personal Firefox profile alongside the profile Cypress launches. Is this reproducible 100% of the time on macOS? |
Sounds like passing -no-remote during Firefox launch might be the solution: https://www.brycevandyk.com/dissecting-firefoxs-no-remote-option/ |
The code for this is done in cypress-io/cypress#6400, but has yet to be released. |
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Current behavior:
Have a Firefox running
Open cypress ui
Select Firefox 72 (beta) and run tests (tested with this repo )
This page is opened in a new Firefox window (with 2 tabs, one empty):
file:///Users/stephane/Library/Application%20Support/Cypress/cy/production/browsers/firefox/interactive/
Then we saw that cypress cannot connect to the server
It's OK if no Firefox running at the moment we launch the tests in Cypress.
Desired behavior:
Be able to run the tests with FF without closing any other existing Firefox instances
Versions
Cypress 4.0.1
Firefox 72.0.2 (64 bit)
MacOS Catalina 10.15.3
Additional informations
This ticket follows 6356 which is closed (I don't have the error in console anymore)
The text was updated successfully, but these errors were encountered: