-
Notifications
You must be signed in to change notification settings - Fork 111
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
Webdrivers::NetworkError, probably due to new chromedriver naming #237
Comments
Thanks to your helpful Version Pinning docs ❤️ , my system tests are running great on the previous version: # test/application_system_test_case.rb
require 'test_helper'
class ApplicationSystemTestCase < ActionDispatch::SystemTestCase
Webdrivers::Chromedriver.required_version = '106.0.5249.21' # <= this version works
driven_by :selenium, using: :headless_chrome, screen_size: [1400, 1400]
end |
Same issue here. |
Oh Google... Updating webdrivers/lib/webdrivers/chromedriver.rb Lines 109 to 111 in 268827f
Could either of you submit a PR? If not then I can try to take a look this week. |
@kapoorlakshya I have submitted a PR for this issue |
No worries, I have added some tests in this PR #240 |
* Update webdriver gem to 5.2.0 version - Reason: SeleniumHQ/selenium#11066 - titusfortner/webdrivers#237 * Add NodeJS installation step in setup & README * Update google-protobuf gem version to match Gemfile.lock
Summary
It looks like Webdrivers'
download_file
gets a 404 because Google changed chromedriver's filename scheme with 106.0.5249.61.Debug Info
Expected Behavior
download_file
should download:https://chromedriver.storage.googleapis.com/106.0.5249.61/chromedriver_mac_arm64.zip
Actual Behavior
download_file
tried to download:https://chromedriver.storage.googleapis.com/106.0.5249.61/chromedriver_mac64_m1.zip
Looking through https://chromedriver.storage.googleapis.com/, the naming seems to change with chromedriver 106.0.5249.61.
It looks like driver_filename always returns "mac64_m1" but should start returning "mac_arm64" for new chromedriver releases.
The text was updated successfully, but these errors were encountered: