Skip to content
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

Firefox won't start with version 13.15.2 #30636

Closed
brunohgo opened this issue Nov 18, 2024 · 12 comments
Closed

Firefox won't start with version 13.15.2 #30636

brunohgo opened this issue Nov 18, 2024 · 12 comments

Comments

@brunohgo
Copy link

brunohgo commented Nov 18, 2024

Current behavior

Currently the firefox does not start when we click, in version 13.15.1 it worked was normally, I updeted the firefox, but nothing happened.
not start

Desired behavior

When we click in firefox it should open the browser.

Test code to reproduce

  1. npx cypress open
  2. Select firefox
  3. Click and wait
  4. Not open the browser
  5. To open other browser is necessary close all cypress and open again.

Cypress Version

13.15.2

Node version

16.20.2

Operating System

Windows

Debug Logs

In console no show nothing

Other

No response

@brunohgo brunohgo changed the title Firefox not start with version 13.15.2 Firefox won't start with version 13.15.2 Nov 18, 2024
@mschile
Copy link
Contributor

mschile commented Nov 18, 2024

Hi @brunohgo, could you run Cypress in debug mode mode and print the entire set of logs here?

@brunohgo
Copy link
Author

cypress-debug-log.txt

Ok, Does it help ?

@AtofStryker
Copy link
Contributor

cypress-debug-log.txt

Ok, Does it help ?

@brunohgo could you try DEBUG=cypress:server:browsers*,cypress-verbose:server:browsers* and send us those logs? It looks like firefox is trying to start but is getting stuck somehow.

@brunohgo
Copy link
Author

cypress-debug-log.txt
Ok, Does it help ?

@brunohgo could you try DEBUG=cypress:server:browsers*,cypress-verbose:server:browsers* and send us those logs? It looks like firefox is trying to start but is getting stuck somehow.

cypress-noverbose_log.txt
cypress-verbose_log.txt

@AtofStryker
Copy link
Contributor

cypress-debug-log.txt
Ok, Does it help ?

@brunohgo could you try DEBUG=cypress:server:browsers*,cypress-verbose:server:browsers* and send us those logs? It looks like firefox is trying to start but is getting stuck somehow.

cypress-noverbose_log.txt cypress-verbose_log.txt

It looks like the logs are cut off? The verbose logs should have quite a lot of content as it is printing all the commands from geckodriver/webdriver

@brunohgo
Copy link
Author

cypress-debug-log.txt

Ok, Does it help ?

@brunohgo could you try DEBUG=cypress:server:browsers*,cypress-verbose:server:browsers* and send us those logs? It looks like firefox is trying to start but is getting stuck somehow.

cypress-noverbose_log.txt cypress-verbose_log.txt

It looks like the logs are cut off? The verbose logs should have quite a lot of content as it is printing all the commands from geckodriver/webdriver

I didn't look for completely, but, Yes, it's cutting. Sorry

@AtofStryker
Copy link
Contributor

cypress-debug-log.txt

Ok, Does it help ?

@brunohgo could you try DEBUG=cypress:server:browsers*,cypress-verbose:server:browsers* and send us those logs? It looks like firefox is trying to start but is getting stuck somehow.

cypress-noverbose_log.txt cypress-verbose_log.txt

It looks like the logs are cut off? The verbose logs should have quite a lot of content as it is printing all the commands from geckodriver/webdriver

I didn't look for completely, but, Yes, it's cutting. Sorry

Are you able to send the full log? It's going to be difficult for me to tell what is happening without it

@brunohgo
Copy link
Author

I think it's complete.
cypress_log_full.txt

@AtofStryker
Copy link
Contributor

I think it's complete. cypress_log_full.txt

Thank you for sending that over! There isn't anything that is standing out to me, except that your node version in use is very old. A lot of these packages require at least node 18 to work and Cypress only works with node 18. Would you be able to try node 20 and see if it launches?

@brunohgo
Copy link
Author

I think it's complete. cypress_log_full.txt

Thank you for sending that over! There isn't anything that is standing out to me, except that your node version in use is very old. A lot of these packages require at least node 18 to work and Cypress only works with node 18. Would you be able to try node 20 and see if it launches?

I can't, my company works with angular 14 so the node must be on version 16.

I found it strange, in version 13.15.1 it worked normally

@alexsch01
Copy link
Contributor

alexsch01 commented Nov 19, 2024

I thought that Cypress 14 would be the first to actually drop NodeJS 16 support

Cypress 13.15.2 includes this now https://github.com/salesforce/tough-cookie/releases/tag/v5.0.0 which I think would break NodeJS 16 support

EDIT: ahh nevermind
Node 14 support has been removed and Node 16 support has been deprecated. Node 16 may continue to work with Cypress v13, but will not be supported moving forward to closer coincide with [Node 16's end-of-life](https://nodejs.org/en/blog/announcements/nodejs16-eol) schedule. It is recommended that users update to at least Node 18.

@AtofStryker
Copy link
Contributor

Cypress 13.15.2 includes this now https://github.com/salesforce/tough-cookie/releases/tag/v5.0.0 which I think would break NodeJS 16 support

I bet that is the cause, considering Firefox is working for you @brunohgo in 13.15.1, which contained a lot of the work to use geckodriver and webdriver to automate Firefox. I don't think there is too much we can do to help since we do not support Node 16. As a heads up, we will also be dropping support for Angular 14 in Cypress 14 and will only be supporting Angular 17.2.0 and up to align with Angular's LTS schedule. I would highly encourage you to update Angular and Node to stay up to date with support/releases when you are soonest able.

Since you are unable to verify with Node 18+, I am unfortunately going to have to close the issue. But if you do update and the issue persists, please comment or open another issue and we will investigate!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants