Skip to content
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

After upgrading to 3.2.0 specs won't run on chrome or chromium only on Electron browser #3852

acyuta108 opened this issue Apr 1, 2019 · 13 comments · Fixed by #17800


Copy link

Current behavior:

Can't start server
EACCES: permission denied, unlink '/home/acyuta/.config/Cypress/cy/production/browsers/chrome/interactive/CypressExtension/background.js'  


Debug output:

$ DEBUG=cypress:* 
cypress:server:events send error: { Error: EACCES: permission denied, unlink '/home/acyuta/.config/Cypress/cy/production/browsers/chrome/interactive/CypressExtension/background.js'   cause: { Error: EACCES: permission denied, unlink '/home/acyuta/.config/Cypress/cy/production/browsers/chrome/interactive/CypressExtension/background.js'   errno: -13, code: 'EACCES', syscall: 'unlink', path: '/home/acyuta/.config/Cypress/cy/production/browsers/chrome/interactive/CypressExtension/background.js' }, isOperational: true, errno: -13, code: 'EACCES', syscall: 'unlink', path: '/home/acyuta/.config/Cypress/cy/production/browsers/chrome/interactive/CypressExtension/background.js' } +21ms                                                                
  cypress:server:events sending ipc data { type: 'launch:browser', data: { id: 0.19919725450670933, __error: { name: 'Error', stack: 'Error: EACCES: permission denied, unlink \'/home/acyuta/.config/Cypress/cy/production/browsers/chrome/interactive/CypressExtension/background.js\'\n\n', message: 'EACCES: permission denied, unlink \'/home/acyuta/.config/Cypress/cy/production/browsers/chrome/interactive/CypressExtension/background.js\'', cause: [Object], isOperational: true, errno: -13, code: 'EACCES', syscall: 'unlink', path: '/home/acyuta/.config/Cypress/cy/production/browsers/chrome/interactive/CypressExtension/background.js' } } } +1ms

Desired behavior:

Browser should open and run selected spec(s)

Steps to reproduce: (app code and test code)

$(npm bin)/cypress open # which currently points to ~/.cache/Cypress/3.2.0/Cypress/Cypress
Click on any spec
Error shows on app screen

If I clear (rm -rf ~/.config/Cypress) the config folder it gets recreated on next run, but error persists.
If I switch to Electron browser, specs run as expected.
If I run specs from the cli ($(npm bin)/cypress run), specs run as expected.


Cypress 3.2.0
Chrome and Chromium 72
Linux NixOS 4.14.98

Copy link

The only change I can think of from 3.2.0 with the extension was us adding an extension id

The Cypress Chrome extension now has a static ID of caljajdfkjjjdehjdoimjkkakekklcck. This allows Cypress to be added to extension whitelists for those working under corporate policies that prohibit extensions. Addresses #3673, #1239 and #2494

Had you at some point set up some permissions around allowing Cypress as a Chrome extension within your company or anything in the past?

Copy link

I did read that in the CHANGELOG. I am pretty certain that's not the case. Another user reported the same issue to me via Nixos/nixpkgs repo.
I'll dig in to see if there is anything else we need to do in order to get Cypress 3.2.0 working on NixOS.

Copy link

mmahut commented Jul 16, 2019

I confirm this persist in 3.4.0.

Copy link

acSpock commented Aug 7, 2019

Getting this same error in 3.4.0 and in 3.3.1

Copy link

I am also able to see this error. I have latest cypress version and my chrome version is 75.

Copy link

This issue has fixed for me it was only happends for chrome 75 version. Now i have chrome 76 version

Copy link

mmahut commented Aug 22, 2019

Having the same problem with chrome 76.

Copy link

try used sudo before using cypress UI interface

Copy link

I have encountered this issue. Using sudo yarn cypress open works though.

Copy link

kliu128 commented Sep 28, 2019

I believe the problem is that all the cypress files in the NixOS store are readonly. Doing chmod 777 /nix/store/...-cypress-3.4.1/opt fixes the problem, but is obviously a major hack (you have to remount the nix store read-write).

Copy link

rasendubi commented Nov 1, 2019

This PR should fix that: #5579

@cypress-bot cypress-bot bot added stage: needs review The PR code is done & tested, needs review and removed stage: work in progress labels Aug 23, 2021
Copy link

cypress-bot bot commented Sep 7, 2021

The code for this is done in cypress-io/cypress#17800, but has yet to be released.
We'll update this issue and reference the changelog when it's released.

@cypress-bot cypress-bot bot removed the stage: needs review The PR code is done & tested, needs review label Sep 7, 2021
Copy link

cypress-bot bot commented Sep 13, 2021

Released in 8.4.0.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v8.4.0, please open a new issue.

@cypress-bot cypress-bot bot locked as resolved and limited conversation to collaborators Sep 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
8 participants