Chromedriver picks up wrong version about chromedriver-helper HOT 13 CLOSED

@alexanderadam
run in terminal
chromedriver-update 2.36
that command will set version 2.36 for chromedriver-helper
after that you can run test normaly :)

from chromedriver-helper.

You may also want to delete the ~/.chromedriver-helper directory, and then run chromedriver-update 2.36 so that it's the only version installed in your environment.

Can you please let us know if this gets addressed, and if so, how? I'd like to improve the documentation and/or address the usability issue here.

from chromedriver-helper.

@Mihoid as I wrote earlier this didn't help. 😉
@flavorjones I did this and chromedriver recreated the ~/.chromedriver-helper/2.36 directory but it fails with the same message.

Is there anything I can do to debug this? Could anything interfere?

from chromedriver-helper.

from chromedriver-helper.

I checked it and I can't see anything.
I'm using Ubuntu and have no chromedriver installed via apt and brew info chromedriver returns

Error: No available formula with the name "chromedriver" 
It was migrated from homebrew/core to caskroom/cask.
You can access it again by running:
  brew tap caskroom/cask

so I guess it's not installed via homebrew either.

As you can see from the screenshot, I've set version 2.38 explicitly but in the error message it is version 2.34.

Any further advice?

from chromedriver-helper.

Sorry, I don't have any other ideas. It's clear that you have 2.34 installed somewhere on your system, if I were you I'd focus on locating it to understand how it's getting injected into your project's path.

from chromedriver-helper.

I agree that I seem to have 2.34 somewhere but isn't that a bug if I explicitly set the version with Chromedriver.set_version and it isn't picked up?
I would expect that just this version would be downloaded and just it's binary selected.

from chromedriver-helper.

I'm not denying it's potentially an issue that we can address -- that's why this Issue is still open. But unless you can help diagnose the issue, or help me reproduce it, I can't really fix anything.

from chromedriver-helper.

chromedriver-update 2.38 fixes this for Chrome 66.x

from chromedriver-helper.

@mlitwiniuk Thanks for posting, but I'm not sure your response addresses @alexanderadam's issue.

from chromedriver-helper.

That's right. The update is not related to the issue here.
@flavorjones I think I got it. There was also the webdrivers gems installed and it interferred with chromedriver-helper.

So it is fixed now (for me).
But I guess there is something that could be improved regarding the binary finding path. But I don't know how. 😉

from chromedriver-helper.

@alexanderadam can you help me reproduce what you were seeing?

from chromedriver-helper.

@flavorjones I'm sorry. Sure, I should have done that in the first place:

So as I described earlier the gem 'webdrivers' was in the same project and it created at some point $HOME/.webdrivers/chromedriver and $HOME/.webdrivers/chromedriver --version returned the faulty version.
So I guess webdrivers may have injected something as well(?) and messed up chromedriver-helper.

I just found it out by jumping into the selenium chromedriver service and read the @executable_path.

So I guess it might help to print a warning in case webdrivers is included in a project as well (they have a similar purpose so it should always just one gem be included, right?). And in case it is a false positive it should be avoidable as well (like setting a variable, constant or environment variable).

On the other hand it might help to have an initial call that really checks whether the right version is loaded. If I understood this correctly there is a chromedriverVersion field that can be returned, so it might be helpful if it will be checked and compared with the version that was set explicitly. I mean, I just found out about this because version 2.34 has a bug. Most of the users wouldn't find out unless they run into something like that.

Or just compare the path that selenium got with our path to see whether $something messed up the path (what if there's another gem that interferes?).

from chromedriver-helper.