-
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
Cypress can't find Chrome after update to 3.3.0 #4260
Comments
Thanks for the bug report. Does this work for you in 3.2.0? |
I actually am blocked now. I can't get it to find Chrome at all. I will try with a fresh 3.2 install though tomorrow |
Alright, cool. Also, try running this command too in Command Prompt, Cypress runs this internally to find your browser:
It should output something like If it doesn't output that, then this looks a duplicate of #3645, and you should be able to fix it by resetting your WMIC store by following the instructions from #3645. |
Some troubleshooting tips as well: https://on.cypress.io/debugging#Launching-browsers |
UPDATE: After installing 3.2.0: I'm also able to click "View App Data" without that crazy ENOENT error message above. |
Moved to #4410 DetailsSame here. Back to Cypress 3.2.0 and Chrome 74 runs again without problems. |
Error remains in 3.3.1 |
Moved to #4410 |
Hey @petermouton @PetMou, this looks like a different issue than the original post in this thread, so I've created a new issue to track this: #4410 Let's move discussion there. |
UPDATE 6-14-19: Another dev on my team implemented some new Cypress tests around a Vue component. We have multiple projects in the same solution using different "cypress test projects". The Cypress instances for my project (there are 2) still can't find Chrome after updating even to 3.3.1. Chrome is available in his project but neither of mine. Is there a setting per project (like maybe |
@jameseg Can you re-share your debug logs? The pastebin in the OP has expired. There aren't any per-project settings for browsers. Cypress attempts to find your browser on each run. Does it work if you manually specify the path to your browser? ex: Also, how are you launching Cypress? ex. via command prompt, powershell, powershell inside of VS code...? |
Here's the latest DEBUG logs: |
And to answer your question I'm running cypress in VS Code using powershell |
Hmm, looks similar to #3891. Cypress uses WMIC.exe to look up info about a potential browser. If it can't be launched, browser detection is broken. It looks like
...and then restart VS code to pick up the new system-wide PATH. Check that Environment variables on Windows are weird, you can obtain debug logs by using the
|
Ok, great. #3672 is also open to change the way we do browser detection to not use WMIC for reasons like this. Glad it's working! |
Warning to all: I ran this command and it deleted everything else in my PATH. Now I have to rewrite it from scratch. |
Aug 2023 - I installed Cypress and it wouldn't show Chrome as a selectable browser. I solved this issue based on #2834 I created a Directory Junction using mklink Now when I run |
Current behavior:
After upgrading to 3.3.0, Cypress is unable to use the existing Chrome installation it used prior. In addition, now even after uninstalling/reinstalling several times both Cypress and Chrome, I can't get Chrome to be available anymore.
When trying to clear the app data from the GUI:
DEBUG logs:
https://pastebin.com/u6kLMHZ0
^this is the piece that worries me, since the logs seem to indicate that Cypress found Chrome, but doesn't have it available for execution.
additional info:
https://stackoverflow.com/questions/56224598/how-do-i-get-cypress-to-detect-my-existing-chrome-browser-after-upgrade
Desired behavior:
Cypress is able to use the existing Chrome application for execution, and is available in the dropdown menu in the GUI
Steps to reproduce: (app code and test code)
Windows 10
Cypress 3.2.0
Chrome installed in the correct location
Versions
Cypress 3.2.0
Cypress 3.3.0
Windows 10
Chrome 74
The text was updated successfully, but these errors were encountered: