Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"cannot determine loading status" and/or "unexpected command response" after a successful command #1421

Closed
mdmintz opened this issue Jul 15, 2022 · 3 comments · Fixed by #1422
Assignees
Labels
bug Uh oh... Something needs to be fixed

Comments

@mdmintz
Copy link
Member

mdmintz commented Jul 15, 2022

cannot determine loading status and/or unexpected command response after a successful command.

Seen after opening "https://wordpress.com/". The open command was successful, even though there was still an error thrown afterwards. Maybe it's safe to ignore those errors if they happen after a successful action.

Full errors:

Exception: unknown error: cannot determine loading status and selenium.common.exceptions.WebDriverException: Message: unknown error: unexpected command response.

@mdmintz mdmintz added the bug Uh oh... Something needs to be fixed label Jul 15, 2022
@mdmintz mdmintz self-assigned this Jul 15, 2022
@mdmintz
Copy link
Member Author

mdmintz commented Jul 15, 2022

This appears to be a relatively new issue in Chromium: https://bugs.chromium.org/p/chromedriver/issues/detail?id=4121

@mdmintz
Copy link
Member Author

mdmintz commented Jul 15, 2022

In all cases where I've seen this issue so far, the error happened after the intended action was already successfully completed. The best way to handle this situation is to wrap commands that would be affected by this, and then ignore these specific errors.

@mdmintz
Copy link
Member Author

mdmintz commented Jul 15, 2022

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Uh oh... Something needs to be fixed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant