Repository navigation
bug: Unable to timeout find_elements and webdriver.Remote #855
Description
Is there an existing issue for this?
- I have searched the existing issues
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 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.
Minimal Reproducible Example
from appium import webdriver
from appium.webdriver.common.appiumby import AppiumBy
ios_caps = {
"appium:automationName": "XCUITest",
"platformName": "iOS",
"appium:udid": "00008020-001655400E82002E",
"appium:webDriverAgentUrl": "http://localhost:7777",
"appium:newCommandTimeout": 5,
}
driver = webdriver.Remote("http://127.0.0.1:4723", ios_caps)
driver.command_executor.set_timeout(5)
driver.find_elements(by=AppiumBy.IOS_PREDICATE, value="type LIKE '**'")The find_elements in a slow app (ie. TikTok) will never return.
Environment
- Operating system:
- If running via
appiumCLI...- Appium CLI version (output of
appium --version): 2.0.0-beta.58 - Node.js version (output of
node --version): v18.12.1 npmversion (output ofnpm --version): 8.19.2- Last
appiumversion which did not exhibit the problem: ?
- Appium CLI version (output of
- If running Appium Desktop, its version:
- Appium driver(s) and their version(s): - xcuitest@4.21.1 [installed (npm)]
- Appium plugin(s) and their version(s): go-ios (gist attached later)
- Platform and version under test: iOS 16.4.1
- Real device or emulator/simulator: real device
Link to Appium Logs
No response
Futher Information
No response
Activity
eyJhb commentedon Apr 27, 2023
@mykola-mokhnach is there a way to do this for other clients?
mykola-mokhnach commentedon Apr 27, 2023
I don't know. xcuitest driver has the
appium:commandTimeoutscapability, which might be helpful in such situationeyJhb commentedon Apr 27, 2023
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.
lana-20 commentedon Feb 27, 2025
@eyJhb
Suggestions:
In addition to the 5 required caps, we need 4 new caps to run tests on a real device with Appium:
xcodeOrgId,xcodeSigningId,udid, andupdatedWDABundleId.Ref: https://medium.com/@begunova/automating-real-ios-devices-with-appium-1fa729b58f51#:~:text=Test%20Setup%20for%20Real%20Devices
A couple of optional caps to try:
derivedDataPath,noReset,showXcodeLog.Ref: https://appiumpro.com/editions/77-optimizing-webdriveragent-startup-performance
Example:
If any caps were intentionally omitted from the provided Minimal Reproducible Example for brevity, then please ignore my comment. This is a mere suggestion.
fix: keep the user client config when switching to a direct connect e…
fix: keep user client config when switching to direct connect endpoint (