cypress: Cypress stuck at cy.visit() on saucedemo.com
Current behavior
I have experienced the following issue before and reported it here #27185 but the website in question was really problematic and the discussion went anywhere but to the point.
I am now experiencing it in the most simple webapp possible: saucedemo.com
The error is this
Your page did not fire its load event within 60000ms
It seems to work is some cases, but I’ll provide instructions on how to reproduce it consistently.
Desired behavior
Cypress should not get stuck at cy.visit()
Test code to reproduce
Run both tests in this repo headed (npx cypress run --headed), or open the suite and run the tests. https://github.com/esbarila/crowdar/tree/master
Cypress Version
12.17.3
Node version
18.16.0
Operating System
Linux (tried in Ubuntu 22.10 and Linux Mint 21)
Debug Logs
CypressError: Timed out after waiting `60000ms` for your remote page to load.
Your page did not fire its `load` event within `60000ms`.
Other
No response
About this issue
- Original URL
- State: open
- Created 3 years ago
- Reactions: 18
- Comments: 49 (9 by maintainers)
I was facing this issue. My solution was cypress->developer tools -> View Appdata. here I deleted the “production” folder closed cypress and open it again
cypress 12.17.4 node v20.5.0
Any update on this issue?
Hi, I was having the same issue (Chrome) and my solution was : cypress.config added chromeWebSecurity: false
Cypress v13.6.4
Solution: https://github.com/cypress-io/cypress/issues/19826 cc: @cachafla
I can confirm this is happening in the example repo provided. There are a couple ways I’m able to reproduce the issue show below where the AUT url is not displaying even though the AUT itself appears to have loaded:
I can trigger this when running the following command:
npx cypress run --headedNote: this only appears to happen in electron
I can also trigger it in open mode using the following command:
npx cypress openNote: this appears to happen in every browser
I fixed the problem with this code:
As you can see, the sauce demo site has this broke url that always respond with a HTTP 401 status, so i block then and my sample project works fine now. Solution tested in Chrome and Firefox.
Cypress: 13.13.2
The trick is: open the Cypress Runner, find some broken URLs, and block them all. Be careful, you have superpowers now
I have the same issue and none of those workarounds worked for me ;[ the funny thing is that:
Having the same issue with latest cypress 13.6.2 The tests with Chrome 120, stucks at visit command
Hello everybody, I’ve noticed that while I
unregisterservice worker (using pwa in nuxt) everything works. So with this founding I usedand my tests seems to work, hope that will help you all 😃
This issue is mentioned on https://filiphric.com/how-to-wait-for-page-to-load-in-cypress together with a resolution:
I was not able to get this to work, but perhaps this hint may help in some way?
Same issue here, first test passes but the subsequent tests are facing :
“Your page did not fire its load event within 60000ms.” Even though my page seems to have loaded. Headed or not does not fix the issue. The tests were running fine before, nothing has changed on my end.
Cypress 13.6.2
I’m getting the same issue after setting up vite-pwa on a Vue application. Removing the file provided by @renzho7 fixed it on the GUI, but it still failed headlessly… currently the only way I got it to work was by deleting the service worker
In my case, I discovered resources (JS and Images) that:
To resolve this, I added the blockHosts configuration to the cypress.config.js file (example below):
blockHosts: [ "www.googletagmanager.com", "analytics.google.com", "www.google-analytics.com" ],And it started working normally.
Cypress 13.13.0 Linux Any browser (including electron).
There was a bug with Chromium https://issues.chromium.org/issues/347724924
Updating to the latest version (126.0.6478.127) solved the issue for me.
tks!!!
Having the same issue with latest cypress 13.6.2 The tests with Chrome 120, stucks at visit command
I have this same issue and it only happens on Chrome 120 headlessly (headed works fine)
Chrome 118 the exact same test passes fine headless and headed
Thank you @renzho7! After removing the production folder it worked for me for the only one test run and I had to remove it every time and rerun cypress. Thanks for your answer I decided to figure out where exactly in that folder is the problem. So I’ve finally found that you just need to delete this folder:
~/Library/Application Support/Cypress/cy/production/browsers/chrome-stable/interactive/Default/Service Worker/CacheStorage. After removing this folder saucedemo visit constantly works.The path and the result is here: https://youtu.be/AdcBb6CAofs cc: @MikeMcC399
The tests hang at the visit command when the spec file contains more than one test. This issue occurs on Chrome, Firefox, and Electron, and persists across different Cypress versions, both older and latest.
Cypress Version: 13.15.1 (stable) System Platform: darwin (23.5.0)
@GilbertoGNG Great news! We are facing same issue, and we applied 2 temporary solutions:
if you have images try to stub them like this before calling cy.visit(“/”)
Use environment variable is an option. Set
TEST_ENV = trueflag for the CYPRESS run, and use it to control if we want a script to load or not in code.I had this issue with Cypress 13.6.6 (latest) and the Electron browser. The first test is working, but some subsequent tests are failing, similar to what @TiltUp-Rad described in https://github.com/cypress-io/cypress/issues/27501#issuecomment-1810392987
In my case (which no doubt is different from many of the other cases described above) I think what happens is this:
/awhich is loaded into Electron just fine. The browser JS application then fetches/bbased on (Cypress simulated) user interaction; this also works fine. Apparently the/bresponse is stored in some kind of cache by Electron or otherwise remembered./b, which Electron loads from its cache(?), but theloadevent is never triggered, so the operation times out after 60 seconds.There is no problem visiting
/cin the second test, because it hasn’t been cached by Electron. The second test can also visit/b?foo=barjust fine. It’s only when the exact same URL visited in the second test has already been fetched in the first test that thecy.visitgets stuck.Using
--browser chromeworks around the problem so this appears to be specific to Electron (but in limited testing, similar problems happen with Firefox as well).This may be a niche situation, but I think it sheds light on the caching behavior of Electron, which could be the underlying reason for at least some of the problems reported here.
Having the same issue with latest cypress 13.6.2 The tests with Chrome 120 stucks at visit command
the first one runs but all below fail, any work around guys?
This works just fine for me 😃 Thanks!
In our case the problem was caused by an external resource that had no route in our internal network, so it ran into a connection timeout which in turn used up the 60 seconds of the Cypress connection test before the actual tests gets executed.
So I am not sure if this is actually the problem described in this issue but I was able to debug it using the DEBUG env-variable to get extended debug information:
DEBUG="cypress:*" cypress ...I hope this helps someone with the same issue.
@omartaghlabi
This issue is about the site https://www.saucedemo.com/ producing the error message
You have a different error message, so it would be better for you to open a different issue so that you can supply all the relevant details, including, for instance, which browser isn’t connecting.
@sumabala9
Sorry for any confusion! I was also not able to get the workaround to solve the problem. We need to wait for further feedback from the Cypress team.