Can't upgrade to version 2.0 and above
See original GitHub issue- Operating System: OS X High Sierra
- Cypress Version: 2.0 and above
- Browser Version: Chrome 64
Is this a Feature or Bug?
Bug
Current behavior:
When I install cypress through npm, at the verification step the process fail with the message:
cypress:cli cli starts with arguments [".nodenv/versions/8.9.0/bin/node","node_modules/.bin/cypress","verify"] +0ms
cypress:cli program parsing arguments +2ms
cypress:cli verifying Cypress app +0ms
cypress:cli path to info.json file /node_modules/cypress/dist/info.json +0ms
cypress:cli { version: '2.1.0', verifiedVersion: null } +14ms
cypress:cli installed version is 2.1.0 comparing to 2.1.0 +16ms
cypress:cli checking if executable exists node_modules/cypress/dist/Cypress.app/Contents/MacOS/Cypress +0ms
cypress:cli path to info.json file node_modules/cypress/dist/info.json +3ms
cypress:cli has verified version null +1ms
cypress:cli run verification check? true +0ms
cypress:cli running binary verification check 2.1.0 +0ms
It looks like this is your first time using Cypress: 2.1.0
cypress:cli writing verified version string "null" +3ms
cypress:cli path to info.json file node_modules/cypress/dist/info.json +3ms
cypress:cli path to info.json file node_modules/cypress/dist/info.json +1ms
cypress:cli running smoke test +3ms
cypress:cli using Cypress executable node_modules/cypress/dist/Cypress.app/Contents/MacOS/Cypress +0ms
cypress:cli needs XVFB? false +0ms
cypress:cli smoke test command: node_modules/cypress/dist/Cypress.app/Contents/MacOS/Cypress --smoke-test --ping=290 +0ms
✖ Verifying Cypress can run node_modules/cypress/dist/Cypress.app
→ Cypress Version: 2.1.0
Cypress failed to start.
This is usually caused by a missing library or dependency.
The error below should indicate which dependency is missing.
https://on.cypress.io/required-dependencies
If you are using Docker, we provide containers with all required dependencies installed.
----------
----------
Platform: darwin (17.4.0)
Cypress Version: 2.1.0
Desired behavior:
I should just pass the verification step and start normally.
How to reproduce:
install it from npm and run cypress verify or cypress open
Additional Info (images, stack traces, etc)
I tried to reproduce the smoke test step directly and got Segmentation Fault 11
. If I go to the directory and open Cypress.app it opens normally.
Version 1.4.2 works as expected.
I already removed the node_modules directory and made a clean install but got the same result.
Issue Analytics
- State:
- Created 6 years ago
- Comments:13 (10 by maintainers)
Top Results From Across the Web
Cannot upgrade to version 2 even when Virtual Machine ...
I have enabled the VirtualMachinePlatform as instructed, but I am still unable to upgrade my distribution to version 2: PS ...
Read more >Can't upgrade from 20.0 to 22.04 due to apt version
The usual recommendation is to simply re-enable -updates , then run sudo apt update , then sudo apt upgrade . This will provide...
Read more >Can't update, even though I have TPM 2.0
I've been trying to update to Windows 11 with no luck. PC Health Check says "TPM 2.0 Enabled on this PC". The UEFI...
Read more >[FIXED] The PC must support TPM 2.0 error while upgrading ...
1. Use Microsoft’s PC Health Check App. 2. Run the Tpm.msc Command.. 3. Copy Files from a Windows 10 ISO File to a...
Read more >How to Upgrade Your Ledger Nano X to Firmware Version 2.0 ...
00:00 Intro 01:00 Make Sure Your Ledger Live Software is Up to Date02:15 How to See the Update Firmware Alert02:56 MAKE SURE YOU...
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
@nvangiessel thanks for tracking this down, never heard of this Node option!
Ok on Darwin too this silently fails
Something for me to work on!
@bahmutov I’ve managed to start a new docker container locally (with our own Dockerfile) and install cypress on it without any problems. Found out that it had to do with a environment var which was set on my machine+build. If you set this ENV var, the installation fails:
export NODE_OPTIONS=--max_old_space_size=4096