cypress: Loading and Crashing issues with Cypress v3.0.1

Current behavior:

When I try to run Cypress via npm I get the following:

C:\Users\aallford\Documents\elprd-risk-assessment-app>C:\Users\aallford\Documents\elprd-risk-assessment-app\node_modules\.bin\cypress run

It looks like this is your first time using Cypress: 3.0.1

 ×  Verifying Cypress can run C:\Users\aallford\AppData\Local\Cypress\Cache\3.0.1\Cypress
   → Cypress Version: 3.0.1
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: win32 (6.3.9600)
Cypress Version: 3.0.1

ALSO If I try to run Cypress from the local install of 3.0.1, it crashes when I try to run an integration test.

Desired behavior:

Cypress will open from npm, and not crash and close if run from local install

Steps to reproduce:

As Current behaviour

Versions

Cypress = v3.0.1 OS = Win 8 Browser = Chrome

About this issue

Original URL
State: closed
Created 6 years ago
Reactions: 7
Comments: 64 (25 by maintainers)

Links to this issue

e2e testing - Cypress failed to start on MacOS - Stack Overflow

Most upvoted comments

Same issue here after I installed Cypress as a dependency of my nodejs project. Finally found a workaround.

clear C:\Users[username]\AppData\Local\Cypress\Cache
start a command prompt as administrator
run npm i cypress -g
run cypress open (not sure if this is needed)
close command prompt
return back to your node.js project and run the tests

lazytesting on Jun 20, 2018

I’m having the same issue (Smoke test failed/Cypress failed to start) on macOS after running initial cypress open.

cypress 3.0.3 macOS High Sierra iTerm

vladzhigulsky on Aug 10, 2018

It worked after doing this for me. Step1: Delete the cache folder Library/Caches/Cypress/ Step2: Run cypress install npm command locally.

This will download and install cypress as a fresh copy.

skumar7 on Oct 23, 2018

Awesome! Thank you @filipenevola . It’s worked. I am very happy now.

linhsonit on May 7, 2019

Wow. Thank you @Bkucera, now it worked. It seems like that was the issue since always. Now I can finally run cypress and really start to use it. Thank you again!

As I’m always using NODE_OPTIONS for other projects I’ll have to always disable it for Cypress but better than nothing 😉 at least now I can use Cypress.

filipenevola on Mar 11, 2019

I had the exact same problem, and installing " Microsoft Visual C++ Redistributable for Visual Studio 2017" resolved it. I had to also delete …\AppData\Local\Cypress\Cache .

The problem didn’t occur on a computer with the same setup which already had the 2017 Redistributable.

D-Alexis on Oct 26, 2018

Cleared the cache and re-installed seems to have fix it. Dunno if stuff did previously was the actual fix, but a new cache was also needed, or if just clearing the cache was the actual fix.

Tried installing using npm, then using yarn. Both failed. Couldn’t run the direct download as a path-length issue was thrown up (even tho I’m enabled for long paths); an unzipping issue rather than Cypress,

Installed VS C++ 2017 Redist and restarted. Still no joy.

Cleared cache and did a reinstall (when Cypress whinges after clearing cache). Cypress Opened fine…

v-mwalk on Jul 8, 2018

I suspect you are downloading the Cypress binary as one user, and attempting to launch Cypress as another. This goes for Administrator privileges as well: in a Dockerfile you execute commands as root by default, and when you run the Cypress, you may not have root.

I checked every single step and I’m always the same user (administrator).

SeriousM on Jun 18, 2018