cypress: Error: EISDIR: illegal operation on a directory
Current behavior:
Error message is thrown
Error: EISDIR: illegal operation on a directory,
open 'C:\Users\*********\AppData\Roaming\Cypress\cy\production\projects\CyDemo-f6363983d1108dd01027bb4ab06585aa\bundles
Desired behavior:
On clicking signIn button user should land on dashboard page
How to reproduce:
Submit userId and password in respective fields and hit signIn
Test code:
function loadFixture() {
cy.fixture('login').as('loginJson')
}
describe('Login', function () {
beforeEach(function () {
loadFixture()
})
before(function () {
cy.visit('https://*************.com');
})
it('It Should load in to the application', function () {
cy.title().should('contain', 'xyz');
})
it('It Should enter credentials and login', function () {
cy.get('#Username').type(this.loginJson.masterCoder.email).should('have.value', this.loginJson.masterCoder.email);
cy.get('#Password').type(this.loginJson.masterCoder.password).should('have.value', this.loginJson.masterCoder.password);
cy.get('.button-label.ng-binding').and('be.visible').click();
})
});
Additional Info (images, stack traces, etc)

- Operating System: Windows10 64bit
- Cypress Version: 1.4.1
- Browser Version: 63.0.3239.132
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 10
- Comments: 58 (16 by maintainers)
Commits related to this issue
- Split out tests for #1244 — committed to cypress-io/cypress by tgriesser 3 years ago
- Splitting out changes for #1244 into separate PR — committed to cypress-io/cypress by tgriesser 3 years ago
Wonder why this bug is labeled as “stage: needs information”? There are couple reproduce steps in the discussion. Is any Cypress team member looking at this?
This is an issue that blocks us to run integration tests in our build pipeline for months. It’s also intermittently failed to run local test files.
I’m getting the same issue on 4.0.1
The spec submits a form and loads a new page. The URL that should be loaded is: https://domain/#/integrations/id and the URL that Cypress is getting stuck on is https://domain/__/#integrations/id
Also it seems strange to me that there’s like… a testrunner window within the testrunner window?
@OliaYesss Thanks for providing a reproducible example. I can see this failing. Adding the new
experimentalSourceRewritingflag does not change the behavior in this case.reproducible example
debug logs
@jennifer-shehane I has resolved the issue for Cypress tests issue for our team. The root cause is not in Cypress, and is because of missing valid id to load the page (due to slow API), and Cypress couldn’t load the page, which ran into EISDIR: illegal operation…
The way we resolve it: intercept the API as alias and wait for the API complete then move on to next test.
Thank you for the help.
Running into the same issue. Reproduced using same steps to repro on: Cypress: 3.8.0 MacOS Mojave Chrome 79 See this in the console:
Related StackOverflow Question
This fix is available starting in
4.6.0as an experiment which you can access by setting this config option in yourcypress.jsonor elsewhere:The fix is experimental, so there may be some situations where the this is not fixed.
If you’re still this issue while setting the
experimentalSourceRewritingto true in 4.6.0 - open a new issue with a reproducible example + screenshots, etc - filling out our issue template.Hi, I´m having the same issue, these are my steps, done in a test webpage to practice:
And my Cypress configuration:
It seems to be an issue with the hash # in the URL, I still have the same issue.
Hi, I got the same issue:
Here is my test:
It reproduced in the almost blanked project (without any additional plugins, etc).
Same goes to me …I can reproduce the issue/error in 3.8.3
Maybe this example can help.
Current behavior:
When in app change hash location with delay (setTimeout) test will leave current page and go to parent page (cypress runner page). In my case http://localhost:8082/__/#/some/route/1
If set “chromeWebSecurity” to true, when run
cypress openand select test get errorIf set “chromeWebSecurity” to false, when run
cypress runget errorDesired behavior:
When in app change hash location with delay (
setTimeout) test will stay on current page. In my case http://localhost:8082/cy-issue-1244.htm#/some/route/1 Do not want to see any error.Steps to reproduce: (app code and test code)
cypress.json
App code:
Test code:
Versions
Cypress: package version: 3.6.1 Cypress: binary version: 3.6.1 Operating System: Windows10 64bit Browser: Chrome 78 Electron 73 (headless)