You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes webdriver.Remote will hang, and it will timeout at any point.
The same goes for using find_elements, if WDA crashes/hangs, then it will never timeout.
I've tried setting appium:newCommandTimeout to 5, but it will still just hang forever.
The only thing I've found that worked, was sitting driver.command_executor.keep_alive = False and driver.command_executor.set_timeout(5).
It's quite unclear, what the best/correct way, is to set a timeout for "anything" so that it cannot just hang indefinitely.
Expected Behavior
That it would timeout after 5 seconds, and there would be a clear documented way of doing this.
Based on the default value of that, it doesn't work. I've had tests hang for hours, and the default value specifies 120s.
Most of the time, the case is that the WDA server becomes unresponsive, and Appium will just hang forever waiting for a response.
Is there an existing issue for this?
Current Behavior
Sometimes
webdriver.Remote
will hang, and it will timeout at any point.The same goes for using
find_elements
, if WDA crashes/hangs, then it will never timeout.I've tried setting
appium:newCommandTimeout
to 5, but it will still just hang forever.The only thing I've found that worked, was sitting
driver.command_executor.keep_alive = False
anddriver.command_executor.set_timeout(5)
.It's quite unclear, what the best/correct way, is to set a timeout for "anything" so that it cannot just hang indefinitely.
Expected Behavior
That it would timeout after 5 seconds, and there would be a clear documented way of doing this.
Minimal Reproducible Example
The find_elements in a slow app (ie. TikTok) will never return.
Environment
appium
CLI...appium --version
): 2.0.0-beta.58node --version
): v18.12.1npm
version (output ofnpm --version
): 8.19.2appium
version which did not exhibit the problem: ?Link to Appium Logs
No response
Futher Information
No response
The text was updated successfully, but these errors were encountered: