New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The Cypress App could not be downloaded (Can't install via NPM I on WINDOWS 2012) #6315
Comments
Does your workplace require a proxy to be used to access the Internet? Or are you behind a firewall that may prohibit your network? Please follow the guidelines in Proxy Configuration if so. Also I see an |
My workplace doesn't require proxy and I can download cypress.zip via console. I know about warning EPERM it's not related to cypress, this is regular behaviour for rudiment dependencies. |
I got the same error on the azure pipeline but with yarn and I was able to workaround.
workaroundI remove from my package.json |
Getting the same thing for Zeit's Now, Netlify, and CircleCI: OperationCode/front-end#1076 Can install locally no problem. Weird. It seemed to resolve itself today. |
Getting this again today for 4.6.0. It seems like binaries get corrupted on some sort of random, self-resolving basis. |
Got same issue when downloading the v4.6. |
not windows, but
|
v.4.6.0 also gives me the headache regarding the same error
|
Im getting the same error for 4.7.0 version even though the proxy is configured. |
I have the same "corruption" issue where the checksum fails, but the filesize matches. #7761 For no reason at all, after trying to go back to 3.8.3, and then re-downloading 4.8.0, it worked. amazing. Lost about 8+ hours to this. |
I get this error always when 99% of packaged download successfully! |
If you're using yarn workspaces and getting some corrupt downloads, it may be this issue #6789. The original issue opened did not involve a corrupted download however, but it seems like most of the comments are referencing corrupted download issues. |
I always come back to this issue and find that it's always the fact there are two instances in the lockfile. I fix it by forcing the correct version via the "resolutions" field in |
Thanks @kylemh I would have guessed that npm/yarn would figure a out a good way to satisfy the requirements with just one version of Cypress, but i could see, like you said, there were two entries for different versions in the lockfile. |
If you see where the conflicting dependency is coming from, I urge y'all to go to those packages and open an issue asking that Cypress be listed as a peerDependency (or devDependency if they've simply made a mistake). |
@jennifer-shehane based on emoji reacts and my own personal experience, I feel like this issue can be closed if there were a better error during installation. Something to indicate that the dev likely has multiple instances listed in their lockfile. |
This can be solved using This issue should be closed. PS: I'm on a Mac OS |
Closing as duplicate of #4595 |
I'm also getting the same issue The Cypress App could not be downloaded. `The Cypress App could not be downloaded. Does your workplace require a proxy to be used to access the Internet? If so, you must configure the HTTP_PROXY environment variable before downloading Cypress.` |
Hi, try the below. |
It might be too late, but if you are on windows. Download the specific binary using
Should solve the issue, Thanks! |
tried Both same error |
Can you add bit more description and screen shots, of what exaclty you tried? |
Current behavior:
Can't install any Cypress version.
I do not use a proxy, I can also download the required version via the browser and console.
STR:
When I make:
I get:
Desired behavior:
The installation of the module should be successful.
Test code to reproduce
Log:
Versions
Cypress 3.7.0
Operating System: Windows Server 2012 R2 Standard 64-bit (6.3, Build 9600) (9600.winblue_ltsb_escrow.191014-1700)
The text was updated successfully, but these errors were encountered: