When trying to automate the process of logging into a GSuite account with the new Google layout, inputting the user email works fine, but then, when transitioning to the password screen, a ResizeObserver loop completed with undelivered notifications is thrown, Cypress cannot catch it with the usual Cypress.on('uncaught:exception') command, and the test fails consistently.
Desired behavior
I'd expect the fallback exception handler (Cypress.on('uncaught:exception')) to kick in and prevent the test from crashing.
you'll need a valid GSuite account to run the project and reproduce the error (I can provide one, if necessary)
there's a Cypress.on('uncaught:exception') handler declared on /support/e2e.js, which doesn't seem to be invoked when the error is thrown
Cypress Version
13.7.2
Node version
v20.11.1
Operating System
Sonoma 14.3.1
Debug Logs
Debug logs are available as files within the Github project. Please see `stdout.txt` and `logs.txt`. The project was ran with the following shell command to save debug logs: DEBUG=cypress:* npx cypress open 1> stdout.txt 2> logs.txt
Current behavior
When trying to automate the process of logging into a GSuite account with the new Google layout, inputting the user email works fine, but then, when transitioning to the password screen, a
ResizeObserver loop completed with undelivered notifications
is thrown, Cypress cannot catch it with the usualCypress.on('uncaught:exception')
command, and the test fails consistently.Desired behavior
I'd expect the fallback exception handler (
Cypress.on('uncaught:exception')
) to kick in and prevent the test from crashing.Test code to reproduce
I've put together a small project to demo the error: https://github.com/felipecao/cypress-error-demo
Please notice that:
Cypress.on('uncaught:exception')
handler declared on/support/e2e.js
, which doesn't seem to be invoked when the error is thrownCypress Version
13.7.2
Node version
v20.11.1
Operating System
Sonoma 14.3.1
Debug Logs
Other
No response