I'm also experiencing this problem out of (seemingly) nowhere.
Portions of tests will pass but then end up with a "unexpected response, 
code=404 content-type="text/plain"
This if followed by "unknown command session/<hex>/element/name 
(Selenium::WebDriver::Error:WebDriverError)

I've tried doing a bundle-update, validating gem versions and dependencies, 
deleting the gem-lock file.. Nothing has worked.

Anyone else have a different solution?

Thanks.

On Wednesday, August 7, 2013 2:10:56 PM UTC-4, Chuck van der Linden wrote:
>
> On Tuesday, August 6, 2013 2:56:32 AM UTC-7, Željko Filipin wrote:
>
>> On Sat, Aug 3, 2013 at 12:15 AM, Chuck van der Linden <
>> [email protected]> wrote:
>>
>>> Is anyone else that tends to work with a mac and Chrome having problems 
>>> with the latest chromedriver?  after installing it all my scripts started 
>>> failing.
>>
>>
>> Sounds like a bug in chromedriver to me. Did you report it in their bug 
>> tracker?
>>
>> Željko
>> --
>> https://leanpub.com/watirbook
>>
>
> Found someone else reporting a similar error.  tried to produce a simple 
> script to reproduce the problem but it would NOT fail.. but the scripts 
> would..
>
> Long story short, I'm using bundler and it had an older version of 
> webdriver in the gemfile.lock  The problem was I think that updates to 
> chromedriver required a newer version of webdriver, and my system was 
> pulling in an older webdriver due to bundler.
>
> Ran 'bundle update' and the weird 404 errors have gone away (note that 
> they seem to have been related to using .exists? or .when_present) 
>
> Moral of the story, when using bundler, remember to use bundle update, not 
> just gem update. 
>

-- 
-- 
Before posting, please read http://watir.com/support. In short: search before 
you ask, be nice.

[email protected]
http://groups.google.com/group/watir-general
[email protected]

--- 
You received this message because you are subscribed to the Google Groups 
"Watir General" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to