6.3: Error: Could not process 'take:screenshot'. No automation clients connected.
See original GitHub issueCurrent behavior
Under Cypress 6.3, tests randomly fail with Error: Could not process 'take:screenshot'. No automation clients connected.
. This did not happen in 6.2.1 or earlier versions.
Desired behavior
The above error should not occur
Test code to reproduce
Sadly, our project is proprietary, but the setup is fairly vanilla and we do nothing out of the ordinary.
Versions
OS: Centos7 Cypress: 6.3.0 Node: 14 Browser: Chrome 87
Issue Analytics
- State:
- Created 3 years ago
- Reactions:12
- Comments:12 (1 by maintainers)
Top Results From Across the Web
Issue in take a screenshot on VM - Help - UiPath Forum
We are trying to capture a screenshot on VM via orchestrator. We trigger the bot and got error like this. Object reference not...
Read more >How to fix common Selenium errors? - Ultimate QA
The Problem. The problem here is that the element that you are trying to click is either covered by another element, or simply...
Read more >Solved: Error when connecting to the ESXi Web interface
Solved: Anyone know how to fix this issue? It started happening seemingly at random. I've tried rebooting the host and clearing my browser...
Read more >WebDriver - W3C
WebDriver is a remote control interface that enables introspection and control of user agents. It provides a platform- and language-neutral ...
Read more >Changelog - Cypress Documentation
In these cases cy.origin() is not required and users would be better served by not using the command. Fixes #24169; Fixed an 11.0.0...
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 Free
Top 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
Same behavior. A few of my tests, in github actions, now seem to hang for a few minutes. I can’t see the screenshot, because of this error:
It looks like this message is separate from the actual error causing my tests to fail. It looks like, when they fail, it tries to take a screenshot for the cypres dashboard, which results in the above error.
If I upgrade cypress to 6.3, the builds are still green locally but fail constantly in CI (Github Actions). @samueloakley If this error really only happens when taking a screenshot after a test failure, then fixing this error will only reveal the real error underneath.
For now, I’ve no other choice but to stay with cypress 6.2.1 which work perfectly fine.