-
Notifications
You must be signed in to change notification settings - Fork 8
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
findElements method throws exception #26
Comments
What type of locator do you use with |
I am searching by by id. I am implementing to wait until the next page of the app loads. The code fires the command 'findElements' until the next page loads and it finds the element, after which it fires 'isElementDisplayed' command. This seems to work for shorter waits. For longer waits, after some time it throws Additional information: Unexpected error. System.Windows.Automation.ElementNotAvailableException: Element not available ---> System.Runtime.InteropServices.COMException: Operation timed out. (Exception from HRESULT: 0x80131505) |
This seems to be related to the fact, that elements becomes unavailable while the command is iterating tree, possible due to being called at same time as the transition occurs. What happens in the app at that moment, do you see app UI transitioning into new state? Are you calling Meanwhile, as a workaround you can try adding exception being thrown to the list of exceptions ignored by WebDriver Wait. In case of java, see https://seleniumhq.github.io/selenium/docs/api/java/org/openqa/selenium/support/ui/FluentWait.html#ignoring-java.lang.Class- for reference |
Sometimes findelements method throws this error
The text was updated successfully, but these errors were encountered: