Cypress is often not connecting / UI is blocked due to underlying socket problems
See original GitHub issueEver since 0.18.0
and possibly even as early as 0.17.11
we have noticed a dramatic increase in the number of CI failures due to the remote client / browser never connecting.
When running tests in Cypress locally we are also noticing times where the UI “hangs” on a full page refresh due to the underlying socket connection either being blocked for multiple seconds, or sometimes erroring with “Socket is in a disconnected / closed state”.
The root cause still has yet to be determined.
Issue Analytics
- State:
- Created 7 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Troubleshooting | Cypress Documentation
Open Cypress via cypress open · Go to Developer Tools -> View App Data · This will take you to the directory in...
Read more >cypress-io/cypress - Gitter
I have cypress whitelisted but video uploads are being blocked. ... There's a whole bunch of errors about sentry and query selectors not...
Read more >upgrade - Cant run cypress using UI - Stack Overflow
1 Answer 1 · Remove your package-lock.json file and node_modules folder. · In your package.json , change the cypress version to 10.1.0 ·...
Read more >Moon - A cross browser Selenium, Cypress, Playwright and ...
A Selenium, Cypress, Playwright and Puppeteer testing platform running in Kubernetes or Openshift clusters. Fully compatible with Selenium Webdriver ...
Read more >Oxygen-3 User Guide - Cypress Solutions
When logging into the web interface, the Oxygen-3 Wireless Gateway will show its ... a) Since connectivity issues sometimes happen immediately after the ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Although we worked around this problem by retrying, it was truly caused by #572 which has been fixed and will be released next.
Thanks, yah the underlying issue is still unknown but retrying 3 times should be enough not to break CI runs. We’re still looking into it.