Unexpected error on CLI on Mac OS X
See original GitHub issueI’m getting the following error when typing: cypress open in the command line for version 1.0.0.
An unexpected error occurred while verifying the Cypress executable.
Please search Cypress documentation for possible solutions:
https://on.cypress.io
Check if there is a GitHub issue describing this crash:
https://github.com/cypress-io/cypress/issues
Consider opening a new issue.
----------
TypeError: Cannot read property 'pipe' of null
----------
Platform: darwin (16.7.0)
Cypress Version: 1.0.0
Also, when running tests on the CLI, the output is not colored anymore.
Issue Analytics
- State:
- Created 6 years ago
- Comments:14 (13 by maintainers)
Top Results From Across the Web
Workaround for “operation can't be completed unexpected ...
Some Mac users running macOS Ventura have noticed a series of “operation can't be completed because an unexpected error occurred” error ...
Read more >If an error occurred while updating or installing macOS
If an error occurred while updating or installing macOS · Check your internet connection · Install in safe mode · Install after repairing...
Read more >macOS error codes and what they mean - MacPaw
It could be caused by something simple and harmless, such as a permissions issue with a file that can be easily fixed. Or...
Read more >7 Ways to Fix Unexpected Error Code 8076 on Mac (2022)
How to fix Mac error code 8076? · Way 1: Check permissions in Finder · Way 2: Uncheck "Ignore permissions on this device"...
Read more >List Of Mac OS X Error Codes - Krypted
List Of Mac OS X Error Codes · General Errors paramErr = -50, /*error in user parameter list*/ · Scrap Manager errors noScrapErr...
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

Yes it’s all the same issue. Going to be fixed once all tests pass for
1.0.1Fixed in
1.0.1.