Use correct and latest chromedriver in Appium

[derek1106]

Please use correct and latest chromedriver in Appium further release.

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

Did not get session redirect from Chromedriver

Hi, Issue is resolved using Chromedriver from below link: https://dl.dropboxusercontent.com/u/2350370/chromedriver_dev.exe Thanks, Sujata

Chromedriver create session did not work. Status was 200 and body was.... Chrome version must be >= 33

setWebContentsDebuggingEnabled is set to true. I tried different devices with 4.4.3 and 4.4.4 Android versions. Also tried different versions of chromedriver. Chrome on device has latest version. Trying to switch context during testing hybrid app using set_context method but getting next error: … info: [debug] Getting a list of available webviews info: [debug] executing: “/Applications/android-sdk/platform-tools/adb” -s 04d5ef159c58e935 shell “cat /proc/net/unix” info: [debug] WEBVIEW_20798…

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=845.

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/

Thanks
Derek

[sujata_kalluri]

Hi @derek1106,

Thanks alot. The above suggestion helps solve ChromeDriver issues with Appium.

Regards,
Sujata

[derek1106]

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.

[derek1106]

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

[0x1mason]

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.

[derek1106]

Great to hear we update the chromedriver in the new release.

[Ravi-ratnakaram]

@0x1mason

directories

I found the path of chrome driver and updated. Now , it’s working fine. Thanks.

[sivashankar.st47]

@Ravi-ratnakaram
Hi Can you please help me to give the path of chrome driver . I’m unable to launch and run the test in chrome browser successfully.

Thanks,
Siva

[SharmaSumit]

@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/downloads
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.

[sagar]

@SharmaSumit

Download the latest version of chromedriver from Sign in - Google Accounts
Move the above chromedriver to /usr/local/bin location
Then change permissions: chmod 7555 /usr/local/bin/chromedriver to make this executable.
Then check the version. using chromedriver --version
Then set the below capabilities.
capabilities.setCapability(“chromedriverExecutable”, “/usr/local/bin/chromedriver”);

Thanks @SharmaSumit. Its working properly now.