0

I am using Selenium Standalone Server on OS X together with facebook/php-webdriver. I am trying to run a PHP script using ChromeDriver 2.28 which is up to date. If I launch selenium-server-standalone-2.53.0, my script works perfectly. If I launch selenium-server-standalone-3.3.1, my script dies with the message Driver info: driver.version: unknown. I have tried to add -Dwebdriver.chrome.driver=chromedriver in my Java command but it does not change anything. Chrome, ChromeDriver and the selenium-server-standalone-3.3.1.jar are in the Applications directory and I launch my Java command line from that directory.

thesailorbreton
  • 363
  • 4
  • 12
  • Are you using chromedriver version 2.28? – Kushal Bhalaik Mar 24 '17 at 12:56
  • You should add some examples, what are you running and the stack-trace error. See if my answer from here helps http://stackoverflow.com/questions/42032960/unknown-option-dwebdriver-chrome-driver-when-running-selenium-server-standalon – lauda Mar 24 '17 at 12:58
  • Try using latest chromedriver – Kushal Bhalaik Mar 24 '17 at 13:08
  • I am using the latest version of Chrome Driver, with regards to logs. In the terminal window where selenium Server is running, I don't get any error, no exception is generated. In the terminal where I run my PHP command I get : Build info: version: '3.3.1', revision: '5234b32', time: '2017-03-10 09:04:52 -0800' System info: host: 'iMac', ip: XXXXX', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.11.6', java.version: '1.8.0_92' Driver info: driver.version:: unknown – thesailorbreton Mar 24 '17 at 13:34
  • try http://stackoverflow.com/questions/15140045/selenium-remotewebdriver-connection-to-selenium-standalone-server-fail-driver – fearis May 04 '17 at 16:29

1 Answers1

0

Sorry, I found the answer, it's an issue between facebook/php-webdriver and the new selenium-server-standalone-3.3.1.jar. With the previous version of selenimum server, the \Facebook\WebDriver\RemoteRemoteDriver::createBySessionID() was creating a new session when the session id passed as an argument was null whereas it now fails with the message Driver info: driver.version:unknown. I don't think it can be considered as a bug apart from the fact that the error it triggers does not help to determine its origin.

thesailorbreton
  • 363
  • 4
  • 12