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
WebdriverManager does not download the correct architecture for my Apple M1 #697
Comments
I wasn't aware about the ARM64 versions of chromedriver in Mac. I think it's the artifact which contains https://chromedriver.storage.googleapis.com/index.html?path=93.0.4577.63/ I have just committed a patch to support it. Unfortunately I don't have a Mac to test it. Can you please test it your machine? You should to bump WebDriverManager to 5.0.2-SNAPSHOT. This version (containing the last patch) is in the sonatype snapshots repositories. If using Maven, you also need to include the following:
... its equivalent in Gradle:
To ensure you are using a fresh cache, you can invoke WebDriverManager as follows:
To check that the patch is working, you should see that WebDriverManager is downloading the
|
5.0.2-SNAPSHOT |
@bonigarcia great job, works like a charm! You're a star! |
Description of the problem:
The issue seems to be that whenever I auto download the Chromedriver, it chooses the Intel version rather than the ARM64 for M1 Chips. How can I ensure it downloads the correct architecture?
Browser and version:
Version 93.0.4577.63 (Official Build) (arm64)
Operating system: macOS Big Sur Version 11.5.2
WebDriverManager version: 5.0.1
WebDriverManager call:
WebDriverManager traces:
14:14:22.762 [main] INFO n.s.c.w.d.ChromeDriverProvider - Using automatically driver download
14:14:22.984 [main] INFO i.g.bonigarcia.wdm.WebDriverManager - Using chromedriver 93.0.4577.15 (resolved driver for Chrome 93)
14:14:22.990 [main] INFO i.g.bonigarcia.wdm.WebDriverManager - Exporting webdriver.chrome.driver as /Users/levi/.cache/selenium/chromedriver/mac64/93.0.4577.15/chromedriver
Error log:
The text was updated successfully, but these errors were encountered: