Cypress blocks my xhr request

[nehbehl]

Cypress blocks my xhr request

[KrzysztofWisniewskiAcc]

Got very similar issue, want to intercept an xhr/fetch call after clicking an input (checkbox)

cy.intercept('https://someurl').as('interceptRequest');
cy.get('#popover-basic input').check(['kw-test-123']);
cy.wait('@interceptRequest');

Feels like a bug or I'm missing something, although I have lots of places where I was doing this likely, although it was never a checkbox.

I can see from the console 2 scenarios

1. The request was done before the interception was triggered, although the 'wait' is placed right after the click call.
2. The interception blocked loading resource loading (after clicking, the request didn't trigger until interception died out of timeout, tried different timeouts so it's not a time issue)

Also tried on various versions of cypress
Cypress 13.6.0 or 13.7.2
node v20.11.1
chrome 123.0.6312.123
windows 11

What I also notice and mb it's somehow related, that the function in tested application, which is triggered after the click, is an 'async' one

saveFavorites: async (listId, performSync = true) => {

[jennifer-shehane]

Could you share some details on this request, like the headers?

[nehbehl]

Here are the header details, please assist to overcome this or understand the reason so that I can move ahead.

[jennifer-shehane]

@nehbehl Are there no errors in the console? I haven't seen this blocked behavior before in Cypress, but it probably has something to do with your application not playing well with how we render within an iframe. Some policy you have set or something is resulting in it being blocked?

[nehbehl]

@jennifer-shehane I get this error in console , what next steps would you suggest to resolve it?

[nehbehl]

Hi @jennifer-shehane , I have shared all the available details from my side and the marked stage still shows 'needs information'. Please let me know what else is required from my end.

[jennifer-shehane]

There's not much we can do without a way to reproduce it on our side. I did do some research into blocked requests and nothing really made sense in this case with what I know we're doing. It would require a deeper dive into the code with the problem.