-
Notifications
You must be signed in to change notification settings - Fork 231
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
RPA.Browser.Seleniun can't read the latest Chrome webdriver #1200
Comments
Workaround for this is to download correct driver from here and place it into stable location and use Another issue with Chrome browser which affect automations is the new search engine selection popup on browser startup. That can be handled by adding new startup argument to Chrome options |
same issue |
Same issue occurs even after using both 32bit and 64 bit chromedriver zips in robot_runtime's webdrivers path. |
Hello, |
Same issue. Update webdriver-manager to 4.0.2 seems to work but has conflict with rpaframework. |
@mikahanninen |
this solution from stackoverflow worked for me: |
Thank you, @gonultasbu, but I have profound stuff to work with, which are based on the RPA.Browser.Selenium library. I managed to make the Open Browser keyword work with my settings, which directly has the parameter to give executable_path. |
Updating to 4.0.2 worked for me. |
Latest rpaframework |
the latest chrome webdriver added a file called THIRD_PARTY_NOTICES and this leads to the error “Webdriver version couldn't be read due to: [WinError 193] %1 is not a valid Win32 application".
Any solution for this error?
The text was updated successfully, but these errors were encountered: