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
I'm using the Winium.WebDriver 0.1.0-1 Maven artifact.
When starting the WiniumDriverService with any port other than 9999, the service always times out while trying to connect to the webdriver process.
Here's what my setup looks like:
service = newWiniumDriverService.Builder()
.usingPort(12345)
.withVerbose(true)
.buildDesktopService();
service.start();
The output is always:
Starting Windows Desktop Driver on port 9999
hh:mm:ss [DEBUG] Waiting for a connection...
org.openqa.selenium.WebDriverException: Timed out waiting for driver server to start.
...
Now, the root cause seems to be that the port isn't passed to the web driver executable as a command-line argument, when spawning the child process. So it will always be the default 9999.
Please find the freeport from your machine and lauch the driver on the free port and try. There is no need to open only on 9999. Winium will intiate the application on any immediate free port.
I'm using the Winium.WebDriver 0.1.0-1 Maven artifact.
When starting the WiniumDriverService with any port other than 9999, the service always times out while trying to connect to the webdriver process.
Here's what my setup looks like:
The output is always:
Now, the root cause seems to be that the port isn't passed to the web driver executable as a command-line argument, when spawning the child process. So it will always be the default 9999.
I think the port argument must be set in WiniumDriverService.createArgs(); at least, that's how the ChromeDriverService seems to to it in ChromeDriverService.createArgs().
The text was updated successfully, but these errors were encountered: