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 downloads geckodriver-...macos-aarch64 instead of geckodriver-v0.30.0-macos for Intel mac #737
Comments
I am facing the same issue OS: macOS Monterey 12.0.1 My colleagues using windows machines do not have this issue. |
It seems the same issue as #734. To debug this problem, I would need you to post the WDM traces and TRACE level. I mean these traces: #700 (comment). |
@mNarraMine Please use the latest version of WebDriverManager. If the error persist there, please post the WDM traces at TRACE level. |
For getting the WebDriverManager logs, you need to include a Logback configuration file (for example, like this) in your project classpath. The name of this file should be
After that, when running a test, your should see something like this:
For further info about logging with with SLF4J and Logback you can see the following tutorial. |
for me this options are working for a workaround on the geckodriver on my mac:
use wdm.forceDownload if there is already the m1-version in the cache ... |
I'm closing this issue since I think it is fixed in the latest version. If the problem happens again, please open a new issue. |
Good day.
I got driver exception "Could not start a new session" when running my tests for Firefox on mac.
Under research the problem I figured out that my .cache contains geckodriver file that throws "Bad CPU type exception".
Download generic geckodriver for Intel platforms and replace it manually was fixed a problem. Therefore that means that the problem is in driver's binary that provides WebDriverManager.
Would be thankful for fixing it.
Thank you.
OS: macOS Monterey 12.0.1
Browser: Firefox v93.0
Webdriver: geckodriver 0.30.0
Driver manager: webdrivermanager 4.4.3
The text was updated successfully, but these errors were encountered: