and unzip it to C:\Users\YOUR NAME\.cache\selenium\chromedriver\win32\1. Download chrome driver (Stable Version: 1.96 (r1160321) ) from. Create a new folder in C:\Users\YOURNAME\.cache\selenium\chromedriver\win32.Ĥ. Delete all existing folders in C:\Users\YOUR NAME\.cache\selenium\chromedriver\win32.ģ. Open C:\Users\YOUR NAME\.cache\selenium and adjust the selenium-manager.json file, setting the driver version to 1.96.Ģ. I've been struggling with a chrome driver 116 issue for some time but finally found a fix. Youre basically just spoofing it until you have a better option. I know its ruby but concepts are the same. Ln -s /path/to/new/chromedriver ~/.cache/selenium/chromedriver/mac-arm64/1.90/chromedriver Mv ~/.cache/selenium/chromedriver/mac-arm64/1.90/chromedriver ~/.cache/selenium/chromedriver/mac-arm64/1.90/chromedriver.oldįinally, wherever you unzipped your recent chromedriver, run: Next unzip chromedriver unzip chromedriver-mac-arm64.zip Unzip chrome for testing: unzip chrome-mac-arm64.zipremember where this unzips toWherever you set your Chrome options:add:Ĭapybara.register_driver :headless_chrome do |app|Ĭhrome_options = Selenium::WebDriver::Chrome::Options.newchrome_options.binary = '/Users/myuser/.cache/selenium/chrome/chrome-mac-arm64/1.96/Google Chrome for Testing.app/Contents/MacOS/Google Chrome for Testing'Īnd change chrome_options.binary to point to the recently downloaded chrome for testing Next Download stable chromedriver from that same branch:ie: However, if youre like us and stuck on 4.9.0 for whatever reason (we're not on ruby 3 or greater yet), what I had to do to get local tests working was:įirst, download stable chrome from for your architecture ie: If you can upgrade past Selenium 4.9.0, then 4.12.0 will support CDP files for v116. Well, I ran into this problem on the Ruby side of Selenium.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |