You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please maybe somebody has experienced the following situation? I am developing a program in c#, that works fine in the main features of using Winium, i.e. I don't have any issue related to using the driver or finding elements. But, after some executions, I noticed that if I close or kill abruptly the running program (because I am still debugging it) the next executions of program falls in the problem reporting this error message:
I searched for alive Winium driver elements in Task Manager but could not find anyone, so the only solution I have for now is rebooting the machine (Windows 10). So, my question is what is causing this behavior and how can I fix it without restarting the affected PC?
This is the basic code I have:
**var options = new DesktopOptions { ApplicationPath = ApplicationPathEXE };
var service = WiniumDriverService.CreateDesktopService(@"Winium.Desktop.Driver");
using (var driver = new WiniumDriver(service, options, TimeSpan.FromSeconds(10)))
{
var credentialsTxtBoxes = driver.FindElementsByClassName("MyClassName"); ...
}**
I am running Winium WebDriver version 0.1.0, C#, Windows 10 64 bits.
Thanks a lot for your help!
The text was updated successfully, but these errors were encountered:
Hello!
Please maybe somebody has experienced the following situation? I am developing a program in c#, that works fine in the main features of using Winium, i.e. I don't have any issue related to using the driver or finding elements. But, after some executions, I noticed that if I close or kill abruptly the running program (because I am still debugging it) the next executions of program falls in the problem reporting this error message:
The HTTP request to the remote WebDriver server for URL http://localhost:64904/session/AwesomeSession/elements timed out after 10 seconds.
I searched for alive Winium driver elements in Task Manager but could not find anyone, so the only solution I have for now is rebooting the machine (Windows 10). So, my question is what is causing this behavior and how can I fix it without restarting the affected PC?
This is the basic code I have:
I am running Winium WebDriver version 0.1.0, C#, Windows 10 64 bits.
Thanks a lot for your help!
The text was updated successfully, but these errors were encountered: