-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ask for latest compatible driver? #23
Comments
There isn't an automated way to do that yet, but you can list available chrome drivers and manually pass the compatible version to > binman::list_versions("chromedriver")
$win32
[1] "73.0.3683.20" "73.0.3683.68" "74.0.3729.6" > rs <- RSelenium::rsDriver(chromever = "73.0.3683.68") |
I've written some logic a while ago that automatically determines the latest ChromeDriver version compatible with the stable Chrome binary of your system, see ropensci/RSelenium#221. It should work on Linux, macOS and Windows. I'd be happy to revise that code (for example we shouldn't rely on |
I resorted to this code inside r, to download the latest driver automatically. This works for Linux. library(rvest) chrome_driver_url <- chrome_driver_url <- directory_path <- "$HOME/.local/share/binman_chromedriver/linux64/" |
Please fill the following template:
Operating System:
MacOS 10.13.6
Please describe Expected behaviour
I'm trying to use RSelenium to drive Google Chrome. For a long time I've had
chromever="latest"
in the
RSelenium::rsDriver
call; it passes the version towdman::selenium
, and that opens the driver.Please describe Actual behaviour
Today the latest Chrome driver is
74.0.3729.6
, which doesn't work with my Chrome73.0.3683.75
, so thersDriver
call fails. Here's what I see:Is there some way to say "the latest compatible version" instead of the "latest"?
Steps to reproduce the behaviour
I think the only thing necessary is to try to open the latest chromedriver on a system that doesn't have Chrome 74.x.
The text was updated successfully, but these errors were encountered: