robocorp
RPA.Browser.Seleniun can't read the latest Chrome webdriver
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?
Workaround for this is to download correct driver from here and place it into stable location and use executable_path parameter to point into correct driver executable.
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
options.addArguments("–disable-search-engine-choice-screen");
Same issue occurs even after using both 32bit and 64 bit chromedriver zips in robot_runtime's webdrivers path.
Same issue. Update webdriver-manager to 4.0.2 seems to work but has conflict with rpaframework.
https://stackoverflow.com/questions/78789819/issue-with-selenium-and-webdriver/78796998
@mikahanninen Is it possible to add the executable path with the Open Available Browser keyword?
this solution from stackoverflow worked for me:
https://github.com/SergeyPirogov/webdriver_manager/issues/665#issuecomment-2271582009
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.
Same issue. Update webdriver-manager to 4.0.2 seems to work but has conflict with rpaframework. https://stackoverflow.com/questions/78789819/issue-with-selenium-and-webdriver/78796998
Updating to 4.0.2 worked for me.
Latest rpaframework 28.6.2 includes webdriver-manager 4.0.2 https://updates.robocorp.com/release/51XaM-rpa-framework-2862 It is recommended to remove existing drivers under %LOCALAPPDATA/robocorp/webdrivers folder when taking this new release into use.
