Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

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

See original GitHub issue

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.

Versions

Cypress 3.2.0 Chrome and Chromium 72 Linux NixOS 4.14.98

Issue Analytics

State:
Created 4 years ago
Reactions:5
Comments:13 (1 by maintainers)

Top GitHub Comments

2reactions

rasendubicommented, Nov 1, 2019

This PR should fix that: https://github.com/cypress-io/cypress/pull/5579

0reactions

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.

Top Results From Across the Web

Fix Chrome update problems & failed updates - Google Support

Reboot your computer. The update might not have completed on your computer. Try rebooting your computer and updating Chrome again.

Changelog - Cypress Documentation

Fixed a regression introduced in the Electron browser in Cypress 10.8.0 where the CYPRESS_EVERY_NTH_FRAME environment variable was not being set ...

Google Chrome - Wikipedia

Google Chrome is a cross-platform web browser developed by Google. It was first released in 2008 for Microsoft Windows, built with free software...

Chromium - ArchWiki

(This is only supported by the chromium launcher script and will not work when using chrome-flags.conf with the google-chromeAUR package.).

What's New | Oracle, Software. Hardware. Complete.

Packages Released on Oracle Linux Yum Server · xrdp-0.9.21-1.el9 - Open source remote desktop protocol (RDP) server (Update) · voms-api-java-3.3.2-11. · rust- ...