Appium is ignoring ecplicit Wait timeouts

Issues/Bugs
1

Appium 1.3.4
Here is the method that invokes the wait object:

public static Boolean waitForElementNotVisible(By by, AppiumDriver driver, int seconds) {
        WebDriverWait wait = new WebDriverWait(driver, seconds);
        Boolean elementIsNotVisible = true;
        try {
            elementIsNotVisible = wait.until(ExpectedConditions.invisibilityOfElementLocated(by));
        } catch (WebDriverException e) {
            elementIsNotVisible=false;
        }
        return elementIsNotVisible;
    }

When I pass in, say 5 seconds as the explicit Wait timeout argument, it will still wait for the default 30 seconds.

Console snippet:

info: [debug] [BOOTSTRAP] [debug] Got command of type ACTION
info: [debug] [BOOTSTRAP] [debug] Got command action: find
info: [debug] [BOOTSTRAP] [debug] Finding com.xxx.android.rentals:id/progress using ID with the contextId: multiple: false
info: [debug] [BOOTSTRAP] [debug] Using: UiSelector[INSTANCE=0, RESOURCE_ID=com.xxx.android.rentals:id/progress]
info: [debug] Waited for 28477ms so far
info: [debug] [BOOTSTRAP] [debug] Returning result: {“value”:“No element found”,“status”:7}
info: [debug] Pushing command to appium work queue: [“find”,{“strategy”:“id”,“selector”:“com.xxx.android.rentals:id/progress”,“context”:"",“multiple”:false}]
info: [debug] [BOOTSTRAP] [debug] Got data from client: {“cmd”:“action”,“action”:“find”,“params”:{“strategy”:“id”,“selector”:“com.xxx.android.rentals:id/progress”,“context”:"",“multiple”:false}}
info: [debug] [BOOTSTRAP] [debug] Got command of type ACTION
info: [debug] [BOOTSTRAP] [debug] Got command action: find
info: [debug] [BOOTSTRAP] [debug] Finding com.xxx.android.rentals:id/progress using ID with the contextId: multiple: false
info: [debug] [BOOTSTRAP] [debug] Using: UiSelector[INSTANCE=0, RESOURCE_ID=com.xxx.android.rentals:id/progress]
info: [debug] Waited for 29479ms so far
info: [debug] [BOOTSTRAP] [debug] Returning result: {“value”:“No element found”,“status”:7}
info: [debug] Pushing command to appium work queue: [“find”,{“strategy”:“id”,“selector”:“com.xxx.android.rentals:id/progress”,“context”:"",“multiple”:false}]
info: [debug] [BOOTSTRAP] [debug] Got data from client: {“cmd”:“action”,“action”:“find”,“params”:{“strategy”:“id”,“selector”:“com.xxx.android.rentals:id/progress”,“context”:"",“multiple”:false}}

2

Set the implicit wait to zero then the code will work.

3

Don’t you think that solving issues by turning off features is not a solution? He is using implicit wait for a reason.

4

Unfortunately Appium java-client 3.3.0 still have this bug. This is critical important if one wants to check if element is displayed.Furthermore, if Timeout exception is not handled, error is displayed in console, yet timeout doesn’t work. Here is code that shows error:

Driver creation:
try {
driver = new AndroidDriver(new URL(“http://127.0.0.1:4723/wd/hub”), capabilities);
} catch (MalformedURLException e) {
e.printStackTrace();
}
driver.manage().timeouts().implicitlyWait(2, TimeUnit.MINUTES);

public static boolean isOpened(AndroidDriver driver) {
By element = By.id(<element=ID>);
WebDriverWait wait = new WebDriverWait(driver, 3);
System.out.println(new Date(System.currentTimeMillis()));
try {
wait.until(ExpectedConditions.visibilityOfElementLocated(element));
System.out.println(new Date(System.currentTimeMillis()));
return true;
} catch (TimeoutException ignored) {
System.out.println(new Date(System.currentTimeMillis()));
return false;
}
}