-
-
Notifications
You must be signed in to change notification settings - Fork 159
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
Selenium [DEPRECATION] Selenium::WebDriver::Error::TimeOutError is deprecated. Use Selenium::WebDriver::Error::TimeoutError (ensure the driver supports W3C WebDriver specification) instead. #869
Comments
It is expected for now. selenium-webdriver ruby gem raises the message. As backwards compatibility, appium ruby gem also has the |
appium/ruby_lib_core#175 (Selenium 4 update issue) |
i do not plan to switch to selenium4 @KazuCocoa |
You can specify the lower selenium-webdriver version to prevent the message. |
Is there a fix for this problem other than |
No, so far. Bump minimal selenium-webdriver version and remove https://github.com/appium/ruby_lib_core/blob/fc7149cbaa199c5bd460d7af49efa2ef09b04243/lib/appium_lib_core/common/base/search_context.rb#L138-L139 is another way. |
I checked again. Probably appium/ruby_lib_core#267 prevents the timeout error warning without updating selenium-webdriver dependencies. (I tested a bit on my local) |
I've pushed appium/ruby_lib_core#267 as appium_lib_core (3.10.0) |
This is a
Summary
Environment
ruby_lib
version: 10.5.0Actual behaviour and steps to reproduce
using exists method throws Selenium [DEPRECATION] Selenium::WebDriver::Error::TimeOutError is deprecated. Use Selenium::WebDriver::Error::TimeoutError (ensure the driver supports W3C WebDriver specification) instead.
Expected behaviour
No deprecation warning shown
Link to Appium/Ruby logs
Create a GIST which is a paste of your full Appium logs, and link them here.
Any additional comments
The text was updated successfully, but these errors were encountered: