-
Notifications
You must be signed in to change notification settings - Fork 70
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
[Windows Bug] Chromedriver verison problem #450
Comments
Additionally, as mentioned in #414 , the version of both Chromedriver and Chrome seemed to be consistent across updates, and it appears it always pulls the latest version of both, no matter the version of GHOSTS. Is it possible for the Windows version to have a similar feature? (Since I saw selenium-manager is shipped with binaries for both OS) I checked the repo and didn't figure out where GHOSTS called the selenium-manager, I'm assuming it's an implicit call done by the selenium package. However, I was able to get latest chrome along with chromedriver downloaded using the new selenium-manage (v0.4.25) found here (mentioned here) instead of the one provided in the archive (v0.4.20) which gives an error when run with
I think this problem can be fixed by running the correct version of selenium manager and fetching the matching version of driver and browser. |
Hi, thanks for the detail. Currently the windows client is still on the traditional windows-only .net framework and references: <PackageReference Include="Selenium.WebDriver">
<Version>4.20.0</Version>
</PackageReference>
<PackageReference Include="Selenium.WebDriver.ChromeDriver">
<Version>124.0.6367.9100</Version>
</PackageReference>
<PackageReference Include="Selenium.WebDriver.GeckoDriver">
<Version>0.34.0</Version>
</PackageReference> the linux version is using dotnetcore, now just dotnet (version 8) and so references different libraries. It looks like the library you suggest fixes this issue - https://www.nuget.org/packages/WebDriverManager/ But requires some code changes. Since I have to maintain a windows vm for the windows client side, these changes take a bit longer, but i'll try to look at it this week or next. |
Really though, I would love to move the windows client to dotnet 8 for ease of development purposes, and condensation of a great deal of code — but I'm not sure how this would affect the community. |
@sei-dupdyke thank you for this fast reply! I am looking forward to that! For now, I gonna continue with my workaround for now and I can provide more information here if it's stable. |
I would be so happy if you did, would modernise the whole project! |
I have been working with GHOSTS for nearly two months, and recently the
BrowserChrome
handler stopped working on Windows machines. It used to work with the chromedriver shipped in the archive, but now I have to download a newer version of chromedriver and overwrite it manually. The error message produced using the stock chromedriver from the archive looks like this:Please forgive me for running GHOSTS under Administrator. This is currently proof of concept, and I don't think this can be the cause of the problem.
FYI, the platform I'm running it on is an AWS EC2 instance (t3.small), with Windows Server 2022 21H2.
I'm very much interested in how the chrome/selenium packages are downloaded because I didn't see any explicit code related to that, is it provided by the
OpenQA.Selenium
package? It will be great if there's a way to pin both the version of chrome/selenium and chromedriver so that this version mismatch will not occur in production.Any thoughts or suggestions are welcomed, and thanks in advance!
The text was updated successfully, but these errors were encountered: