[🐛 Bug]: Selenium fails to find chrome binary after 4.20.1 about selenium HOT 11 CLOSED

@amcmillion3 This is correct, the deprecation will go away in the newer version of Rails.

from selenium.

@shouichi, thank you for creating this issue. We will troubleshoot it as soon as we can.

from selenium.

@titusfortner do you know if this is correct?

from selenium.

I am running into the same thing. Unless I pin to 4.19.0 I get Selenium::WebDriver::Error::UnknownError: unknown error: cannot find Chrome binary cc/ @p0deje

from selenium.

Ideally, Rails would not attempt to preload drivers/browsers via a direct API call of Selenium. Reading through the code, this is done to avoid race conditions when running tests in parallel. I think that Selenium should handle this internally so that concurrent attempts to preload the driver/browser would ensure there are no race conditions and wait for the first process to finish downloading, then yield to other binary calls. With this implementation in place, the related part of Rails code can be removed:

https://github.com/rails/rails/blob/dcfabdbe4e7e53fc757d0ebf89c77349899a35bb/actionpack/lib/action_dispatch/system_testing/browser.rb#L40-L49

It's a fairly simple change that I can do both in Selenium and Rails, but I am not sure if that suits the Rails users. @searls Do you happen to know if it would be fine for Rails to pin Selenium to say >= 4.20.2 in the next Rails version?

from selenium.

It's a fairly simple change that I can do both in Selenium and Rails, but I am not sure if that suits the Rails users. @searls Do you happen to know if it would be fine for Rails to pin Selenium to say >= 4.20.2 in the next Rails version?

I'm not on Rails core so it's not for me to say, but I would wager that simply releasing a fix in Selenium to allow anyone who runs into this to receive the fix via bundle update to a patch release would be plenty to resolve it, regardless

from selenium.

@searls @shouichi Can you see if 4.21.1 solve the problem for you?

from selenium.

@p0deje 4.21.1 solved the problem. Thank you!

from selenium.

Great!

from selenium.

Confirm: fixed me too

from selenium.

We're using selenium-webdriver 4.21.1 in our Rails application, but we're still seeing the deprecation message. Based on this discussion, it sounded like the deprecation warning going off is a byproduct of how Rails system tests work. Is it fair to assume that there's not direct action that we can take for the time being to resolve this issue?

from selenium.