-
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
Cypress can't locate Chrome 85 exe in Windows #8425
Comments
Could you run Cypress in debug mode specifically logging |
I ran
|
|
Run:
|
|
Yah, your debug logs aren't logging for some reason. 😞 I've seen this occur with permissions issues with setting the environment variable in the terminal/shell. You may need to run your terminal in administrative mode or review your permission settings. |
(I didn't get debug logging either, but running |
We are having the same issue since chrome 85 on a ci machine. Here's the output from our log
|
As stated in the original post, Chrome 85 uses a different default installation directory. New-Item -ItemType SymbolicLink -Path "C:\Program Files (x86)\Google\Chrome" -Target "C:\Program Files\Google\Chrome" The site documentation does mension this but the original post was intended a problem for Chrome uses on Windows. If Google has defaulted to x64 version for Windows users, documentation should be updated to reflect this. Better yet, Cypress should be updated to look to this path for Windows x64 users. |
The code for the locations of browsers on Windows can be found here: https://github.com/cypress-io/cypress/blob/develop/packages/launcher/lib/windows/index.ts#L11:L11 We're open to a pull request to fix the executable location in Windows. |
The code for this is done in cypress-io/cypress#8449, 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:
cypress open
does not show Chrome as a browser option. This occured after update to Chrome 85, released 2020-08-25.I'm pretty sure this comes down to how Cypress is checking for the browser. While debugging, I came across a claim that cypress uses the following line to detect Chrome:
If this is true, Cypress won't work with Chrome 85 because it defaults to a x64 version (at least on my PC) which has a different default directory on Win10 x64 version:
Desired behavior:
I would like the ability to use Chrome 84 x64 as a browser.
Test code to reproduce
cypress open
Versions
OS:
Windows 10
Cypress:
4.9.0
and5.0.0
The text was updated successfully, but these errors were encountered: