cypress: Cypress.automation('remote:debugger:protocol') command started failing in Cypress 7.3.0

Thanks @asmirnov-style!

I adapted mine a bit too:

const goOffline = () => {
    cy.log('**go offline**')
        // stub every request with a StaticResponse to simulate network error
        .then(() => cy.intercept('*', { forceNetworkError: true }))
        .then(() =>
            cy.window().then((win) => win.dispatchEvent(new Event('offline')))
        )
}
const goOnline = () => {
    cy.log('**go online**')
        // go back to normal network behavior
        .then(() => cy.intercept('*'))
        .then(() =>
            cy.window().then((win) => win.dispatchEvent(new Event('online')))
        )
}

Can we please get this working? None of the workarounds above works anymore. I hate to be stuck with version 6.9 because of this

Cypress 12.6.0, still has the same issue! How do you guys test offline/online in Cypress??

Same here. Stuck with 6.9.1 because of this issue

According to my investigation, this issue may be injected by this commit in socketio/engine.io-client repo. It supports a listen to the "offline" event feature in version 5.0.0 (2021-03-10).

The problemic code is as follows:

+ if (this.hostname !== "localhost") {
+   this.offlineEventListener = () => {
+     this.onClose("transport close");
+   };
+   addEventListener("offline", this.offlineEventListener, false);
+ }

The socket is closed after sending CDP command: { "command": "Network.emulateNetworkConditions", "parameters": { "offline": true } }. Then the command response is never received and Cypress.automation('remote:debugger:protocol', { ... }) is timeout.

Kind a way for simulate OFFLINE (while Cypress team fixing 4 y.o bug)

` goOfflineIntercept() {
        cy.log("**go offline**").then(() => {
            cy.intercept(
                {
                    method: "GET",
                    url: "*",
                },
                {
                    statusCode: 404, // if you like and need it
                }
            );
        });
    }

goOnlineIntercept() {
        cy.log("**go online**").then(() => {
            cy.intercept("GET", "*", (req) => {
                req.continue();
            });
        });
    }`

We were also going offline and online in tests and are missing it… +1 here.

I am also suffering with this issue. I have confirmed Cypress 6.9.1 is still working properly. I have tested Cypress 6.9.1 against Chrome 96 and Electron 87 (working properly in both cases). Cypress 8.7.0 fails, Cypress 9.0.0 fails. So, or we go back to 6.9.1, or…

I am also experiencing this issue on our project when I upgraded to v8.6.0. Is there a provided solution or an ETA for a fix? We cannot upgrade till this is fixed. 😭

Another “work around”. With the fact that Network.emulateNetworkConditions and offline: true did set the Chrome network to offline, but Cypress cannot receive the command execution result. So we can tell Cypress to ignore this particular error, and continue to run our test specs.

cy.on('fail', e => {
  if (
    e.name === 'CypressError'
    && e.message.includes('timed out')
    && e.message.includes('remote:debugger:protocol')
    && e.message.includes('Network.emulateNetworkConditions')
    && e.message.includes('offline: true')
  ) {
    // do not fail the test
    return false;
  }
});

cy.log('**go offline**')
  .then(() =>
    Cypress.automation('remote:debugger:protocol', { command: 'Network.enable' })
  )
  .then(() =>
    Cypress.automation('remote:debugger:protocol', {
      command: 'Network.emulateNetworkConditions',
      params: {
        offline: true,
        latency: -1,
        downloadThroughput: -1,
        uploadThroughput: -1
      }
    })
  );

Modifying the real onLine attribute, tested in Cypress 12.11.0:

// go offline
cy.window().then((win) => {
  cy.stub(win.navigator, 'onLine').value(false);
  cy.wrap(win).trigger('offline');
});

// go online
cy.window().then((win) => {
  cy.stub(win.navigator, 'onLine').value(true);
  cy.wrap(win).trigger('online');
});

Same, still not working in 9.1.1

Do anyone know alternative solution to simulate browser offline mode?

Any update on this? My tests are also failing where this functionality is required

@szhong-becls your workaround did not work for me, unfortunately.

The same regression issue in 8.0.0

+1 to this. I’m seeing the same problem.

Is this issue fixed in v13?

I tried this test and the results are as follows:

• v12.17.4: failed
• v13.0.0: passed

Cypress 12.6.0, still has the same issue! How do you guys test offline/online in Cypress??

@AlanCodega mock all requests

Cypress 12.6.0, still has the same issue! How do you guys test offline/online in Cypress??

Pls check my answer (the final answer in the issue discussion) at https://github.com/cypress-io/cypress/issues/235 (i couldn’t cite the issue), that workaround worked for me.

Hope everyone had a happy holiday season! As of v12.3.0 looks like the remote:debugger:protocol still fails to go back online. Can anyone else confirm?

Another “work around”. With the fact that Network.emulateNetworkConditions and offline: true did set the Chrome network to offline, but Cypress cannot receive the command execution result. So we can tell Cypress to ignore this particular error, and continue to run our test specs.

cy.on('fail', e => {
  if (
    e.name === 'CypressError'
    && e.message.includes('timed out')
    && e.message.includes('remote:debugger:protocol')
    && e.message.includes('Network.emulateNetworkConditions')
    && e.message.includes('offline: true')
  ) {
    // do not fail the test
    return false;
  }
});

cy.log('**go offline**')
  .then(() =>
    Cypress.automation('remote:debugger:protocol', { command: 'Network.enable' })
  )
  .then(() =>
    Cypress.automation('remote:debugger:protocol', {
      command: 'Network.emulateNetworkConditions',
      params: {
        offline: true,
        latency: -1,
        downloadThroughput: -1,
        uploadThroughput: -1
      }
    })
  );

This workaround worked for my with cypress open but hangs for cypress run