My system recently auto-updated to Chrome 89.0.4389.90, and RSelenium stopped being able to open it. After some debugging, I found that chromedriver 89.0.4389.23 was installed into ~/Library/Application Support/binman_chromedriver/mac64/89.0.4389.23, but when I went to that directory and ran it, I saw this error:

$ ./chromedriver --version
-bash: ./chromedriver: Bad CPU type in executable

The directory also held chromedriver_mac64_m1.zip and chromedriver_mac64.zip. I don't have an M1 chip in my laptop, so I unzipped the 2nd one to replace the chromedriver file, and now things are working again.

I'm assuming by the directory name it was binman that unpacked the wrong zip. I'd be happy to run other tests if you want to track this down, but for now my system is fixed.

In this issue ropensci/wdman#34 I pointed out that wdman can't download recent versions of chromedriver, because the Chrome developers have changed the way they are distributed. I think the new details can be found here: https://googlechromelabs.github.io/chrome-for-testing/.

I started looking into a PR for wdman to support the new scheme, but I see it uses binman::predl_google_storage for most of the work, so now I'm not sure if there should be a binman change as well to support the new scheme.

Similar to the issue above. Can't open Chrome (version 89.0.4389.xx) using RSelenium. I only have a chromedriver file for an M1 in the following folder:

/Users/blahblah/Library/Application Support/binman_chromedriver/mac64/89.0.4389.23

I'm not on an M1 Mac. Best I can tell, that's the root of the problem (see: "error=86, Bad CPU type in executable")