Open bzang opened 6 years ago
I was facing the same issue. Thanks to @WillBrock I was able to resolve this.
There might be a process which is running the 2.33 version of chromedriver. Kill that process and everything should work like normal.
// To list all commands
ps
// To kill the chromedriver process
kill -9 [PID]
With the 0.0.10 update, chromeDriver no longer seems to load correctly, returning the following error:
It seems to be defaulting to chromeDriver version
2.33
even though the default settings specify2.36
. I'm running selenium3.6.0
, wdio4.12.0
.