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

"Browser was not launched through Cypress" after 3.3.0 upgrade #4410

Closed
flotwig opened this issue Jun 7, 2019 · 9 comments
Closed

"Browser was not launched through Cypress" after 3.3.0 upgrade #4410

flotwig opened this issue Jun 7, 2019 · 9 comments

Comments

@flotwig
Copy link
Member

@flotwig flotwig commented Jun 7, 2019

After installing 3.3.0 I get the Whoops' window ('This browser was not launched through Cypress'), trying to run Chrome 74.
The Cypress add-in is loaded in to Chrome. The add-in is shown as version 0.0.0
The tests run fine under Electron 61.

Back to Cypress 3.2.0 and Chrome 74 runs again without problems.

Originally posted by @petermouton in #4260 (comment)


Cypress 3.3.1

Cypress_Chrome_error

Originally posted by @PetMou in #4260 (comment)

@flotwig
Copy link
Member Author

@flotwig flotwig commented Jun 7, 2019

@petermouton @PetMou It looks like Chrome is being launched with an incorrect path to the spec, which is causing this error. Can you share the full DEBUG logs, from the time to when you launch Cypress to when you launch Chrome and experience this error? Instructions for debug logs are here: https://docs.cypress.io/guides/guides/debugging.html#Print-DEBUG-logs

@PetMou
Copy link

@PetMou PetMou commented Jun 11, 2019

Thanks Zach. I added the debug log
cypress_debug_4410.log

@PetMou
Copy link

@PetMou PetMou commented Jun 18, 2019

Parallel to issue #4260, I tried several options. Extra information:

  • We run in a Windows 10 environment
  • I now have more cypress installations next to eachother on the same disk. 3.3.1 to try options, 3.2.0 for the daily jobs. Testlife must go on...
  • command cypress open --browser chrome will open the project correcly, whereas cypress open --browser "C:<path>\chrome.exe" displays a message that cypress can't find a browser at that location. Which is strange, because the path is correct, and chrome does start, using this path.
  • To start 3.3.1 I have to use a command file because I need to set NO_PROXY=undefined beforehand to avoid cypress saying it can't start the server
  • I have installed cypress from within IntellIJ

Hope this gives some extra clues.

@flotwig
Copy link
Member Author

@flotwig flotwig commented Jun 18, 2019

Hey @PetMou, I was able to reproduce your issue, can you try something for me? Run with NO_PROXY=undefined,localhost.

The core problem is that requests for Cypress's internal server on localhost are going through your proxy, which will be fixed with #4358 (should be out in 3.3.2).

@PetMou
Copy link

@PetMou PetMou commented Jun 18, 2019

Wow. That did the trick!
Thank you!

Check, one more happy customer! :))

@cypress-bot
Copy link

@cypress-bot cypress-bot bot commented Jun 19, 2019

The code for this is done in cypress-io/cypress#4358, but has yet to be released.
We'll update this issue and reference the changelog when it's released.

@cypress-bot
Copy link

@cypress-bot cypress-bot bot commented Jun 27, 2019

Released in 3.3.2.

@munna73
Copy link

@munna73 munna73 commented Jul 20, 2020

I am having this issue in Cypress 4.10.0. I am using my work computer.Works fine on electron 80 but when I select chrome it gives error The browser was not launched through cypress , tests can not run

@jennifer-shehane
Copy link
Member

@jennifer-shehane jennifer-shehane commented Jul 21, 2020

This issue will be closed to further comment as the exact issue here was resolved and tested.

@munna73 If you're experiencing a bug similar to this in Cypress, please open a new issue with a fully reproducible example that we can run. There may be a specific edge case with the issue that we need more detail to fix.

@cypress-io cypress-io locked as resolved and limited conversation to collaborators Jul 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

4 participants