Skip to content
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

Closed
2 tasks
hardik-plume opened this issue Dec 4, 2019 · 8 comments

Comments

@hardik-plume
Copy link

This is a

  • [/] Bug report
  • Question
  • Freature Request

Summary

Environment

  • Appium version (or git revision): 1.15.1
  • ruby_lib version: 10.5.0
  • Mobile platform/version/device under test: iPhone 11 simulator

Actual 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

@KazuCocoa
Copy link
Member

KazuCocoa commented Dec 5, 2019

It is expected for now. selenium-webdriver ruby gem raises the message.

As backwards compatibility, appium ruby gem also has the TimeOutError error to support lower selenium-webdriver version. I'm planning to remove it in switching it to selenium 4 base.
(Or I can remove the message with stopping to support lower selenium-webdriver version.)

@KazuCocoa
Copy link
Member

appium/ruby_lib_core#175 (Selenium 4 update issue)

@hardik-plume
Copy link
Author

i do not plan to switch to selenium4 @KazuCocoa

@KazuCocoa
Copy link
Member

KazuCocoa commented Dec 23, 2019

You can specify the lower selenium-webdriver version to prevent the message.
Maybe 3.14.1 has no it.

@kayner
Copy link

kayner commented Jun 8, 2020

Is there a fix for this problem other than Selenium::WebDriver.logger.level = :error or changing selenium-webdriver version?

@KazuCocoa
Copy link
Member

@KazuCocoa
Copy link
Member

KazuCocoa commented Jun 8, 2020

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)
Could you try it when you have a change?

@KazuCocoa
Copy link
Member

I've pushed appium/ruby_lib_core#267 as appium_lib_core (3.10.0)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants