This site is in read only mode. Please continue to browse, but replying, likes, and other actions are disabled for now.
Jan 2015
1 / 10
Jan 2015
Jul 2018
derek1106
Jan '15

Please use correct and latest chromedriver in Appium further release.

There are a lot of issues about chromedriver, like the links as below.


The root cause is from chromedriver itself, but chromedriver fixed it in the latest version 2.13.
Here is the issue link, https://code.google.com/p/chromedriver/issues/detail?id=845310.

Appium 1.3.4 still uses the old chromedriver, so please use correct and latest chromedriver in the further release.
Here is the link to get chromedriver 2.13 version.
http://chromedriver.storage.googleapis.com/index.html?path=2.13/588

Thanks
Derek

  • created

    Jan '15

  • last reply

    Jul '18
  • 9

    replies

  • 9.4k

    views

  • 7

    users

  • 5

    links

derek1106
Jan '15

Yes, the chromedriver issue is resolved.
Please ensure Appium will invoke the correct and latest chromedriver in the further release, that will help a lot for customers.

2 months later
derek1106
Mar '15

In which Appium version we start to use the correct and latest chromedriver?
Appium 1.3.4 is using the old one.

0x1masonLeader
Mar '15

Chromedriver is typically up-to-date at time of release. You can always update Chromedriver yourself by replacing the one in the Appium directories with the version of your choice.

1 year later
1 month later
1 month later
SharmaSumit
Apr '17

@sivashankar.st47 : I also faced this issue in appium 1.5.3 version. I did below to solve my problem and it worked for me.

  1. Download the latest version of chromedriver from https://sites.google.com/a/chromium.org/chromedriver/downloads172
  2. Move the above chromedriver to /usr/local/bin location
  3. Then change permissions: chmod 7555 /usr/local/bin/chromedriver to make this executable.
  4. Then check the version. using chromedriver --version
  5. Then set the below capabilities.
    capabilities.setCapability("chromedriverExecutable", "/usr/local/bin/chromedriver");

You can run appium as normal without problem.

The chromedriverExecutable allows you to specify your own chromedriver
executable thus bypassing the appium-chromedriver.

1 year later
sagar
Jul '18

Thanks @SharmaSumit. Its working properly now.