-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Browser: 'chrome' was not found on your system or is not supported by Cypress. #16322
Comments
Are you using Docker? Please see our troubleshooting guide on Launching Browsers Could you run Cypress in debug mode specifically logging |
I downgraded from 9.5.1 to 9.4.1 to avoid a separate bug, and this just started happening after the downgrade. Running on Windows 10 via Git Bash. Cypress info
This log seems odd, that location is actually where Chrome is:
Full launcher logs:
|
I also tried clearing app data folder and explicitly adding C:\Windows\System32\wbem to my PATH as recommended in other issues, but that hasn't helped. Fresh install of node_modules including cypress didn't help either. |
@jennifer-shehane
Full cypress:launcher log
package.json
|
Have the same issue on GitLab CI, and it's funny that I get chromium instead of chrome |
i do have also the same issue on an m1 max macbook |
I'm able to reproduce this issue with official docker container: |
The issue for me on Windows seems to be a permissions issue when running the
Even though when I run that command manually in CMD it successfully returns the version. I have a pretty locked down PC in my work environment, but surely if I'm providing Cypress with the path to chrome it can just use that path. |
That's not how permissions work. The user that's using the path should have execution related permissions on that path first. Otherwise, anyone with a path can run anything no matter how much you lock your system down. |
@abhi1693 My user has permission to run chrome, and my user is running Cypress. |
@abhi1693 Are you perhaps using a machine with a corporate proxy? It's difficult to investigate this issue since it is specific to your machine. If you are part of a team, Is this happening to anyone else? Any additional context would be appreciated so we can investigate further. |
Right now there doesn't seem to be enough information to reproduce the problem on our end. Unless we receive a reliable reproduction, we'll eventually have to close this issue until we can reproduce it. This does not mean that your issue is not happening - it just means that we do not have a path to move forward. Please provide a reproducible example of the issue you're encountering. Here are some tips for providing a Short, Self Contained, Correct, Example and our own Troubleshooting Cypress guide. |
@warrensplayer I provided the cause of the issue in my case in a previous comment. the problem was caused by not having permission to run wmic. So ideally there would be an option to specify the exact path to Chrome and not use wmic at all. |
@rooby please feel free to submit that feature request. Based on our current priorities I do not see us prioritizing that work though. |
When I am using Cypress I can only se Electron browser. Although I have both firefox & chrome in my computer by Cypress only detects Electron & says:
**Can't run because you've entered an invalid browser name.
Browser: 'chrome' was not found on your system or is not supported by Cypress.**
The text was updated successfully, but these errors were encountered: