"Unable to either launch or connect to Chrome"

[jayzes]

I'm guessing that this isn't directly related to chromedriver-helper, but I just started seeing this error consistently on a project using the helper and can't seem to track down the cause, so I'm curious if anyone else is seeing it.

Both on my dev machine and CI box (both Macs, one running Lion, one running Mountain Lion), I started seeing the following error today:

Unable to either launch or connect to Chrome. Please check that ChromeDriver is up-to-date. Using Chrome binary at: /Applications/Google Chrome.app/Contents/MacOS/Google Chrome (Selenium::WebDriver::Error::UnknownError)

Tried updating by Selenium-Webdriver gems, Chromedriver, Chrome itself, switching to Canary, etc., all to no avail. Doesn't seem to be related to my code as older versions that had passed are now failing. The weird thing is that Chrome does fire up, but it never goes to the URL for the test suite - it just hangs there with a blank page.

Anyway, out of curiosity - is anyone else seeing this or am I totally nuts? My hunch is that it's something related to a Chrome auto-update that broke the integration, but I have no way of telling whether Chrome updated itself today or not.

[caseyprovost]

im seeing this issue as well, currently applies to Chrome Version 21.0.1180.57

[flavorjones]

Confirmed -- let me try to find an update.

[flavorjones]

OK - For what it's worth, I upgraded the version of chromedriver with the following commands:

rm -rf ~/.chromedriver-helper
bundle exec chromedriver # and wait for download

I'm now running chromedriver_linux64_21.0.1180.4 with chrome 21.0.1180.49 beta and everything appears to be healthy again.

[flavorjones]

I've released chromedriver-helper 0.0.4 which includes chromedriver-update to force-upgrade chromedriver. Let me know if that works for you.

[supairish]

Had this same issue, and your chromedriver-update command worked like a charm, thanks!

[flavorjones]

Sweet, thanks for confirming! And thanks for using chromedriver-helper!