WebDriverWait issue for AndroidElement

csw583 · May 16, 2018, 3:31am

The below method can’t peform for 1.8, but it can use for 1.7.2
public boolean waitForAeAppear(AndroidElement androidElement, int timeOutInSeconds) {
try {
WebDriverWait wait = new WebDriverWait(aDriver, timeOutInSeconds);
wait.until(ExpectedConditions.visibilityOf(androidElement));
return true;
} catch (Exception e) {
return false;
}
}

chrisdw · May 16, 2018, 10:41am

I am seeing the same issue having just upgraded to 1.8 the following code is throwing “An element could not be located on the page using the given search parameters…” immediately on being called.

        var wait = new WebDriverWait(driver, TimeSpan.FromSeconds(Constants.DefaultTimeout));
        wait.Until( x => x.FindElement(By.XPath(String.Format("//*[@text='{0}']", textToWaitFor))));

If I try to use
driver.Manage().Timeouts().ImplicitWait = TimeSpan.FromSeconds(Constants.DefaultTimeout);
I get an exception “Parameters were incorrect. We wanted “W3C protocol expects any of script, pageLoad or implicit to be set” and you sent {“type”:“implicit”,“ms”:60000}”

Does anyone have any suggestions how to wait for an element short of downgrading?

MrZigaS · May 17, 2018, 10:35am

If you are using java client 6.0.0 BETA 5, check the link below:

github.com

appium/java-client/blob/master/src/test/java/io/appium/java_client/appium/AppiumFluentWaitTest.java

/*
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * See the NOTICE file distributed with this work for additional
 * information regarding copyright ownership.
 * You may obtain a copy of the License at
 *
 *     http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

package io.appium.java_client.appium;

import static java.time.Duration.ofSeconds;
import static org.hamcrest.MatcherAssert.assertThat;

This file has been truncated. show original

… I implemented it like shown in this case (by creating a class like FakeElement) and it works perfect.

MrZigaS · May 17, 2018, 10:51am

The way you are calling wait.Until:

var wait = new WebDriverWait(driver, TimeSpan.FromSeconds(Constants.DefaultTimeout));
wait.Until( x => x.FindElement(By.XPath(String.Format(“//*[@text=‘{0}’]”, textToWaitFor))));

… x.FindElement will return null, which is not expected. Wait.util is expecting TRUE or FALSE and until false is returned, it will be trying to call again (Except if timeout hits). Check my comment above how you can solve it by creating “FakeElement” class.

I hope this helps.

Lavanya_Shelley · May 21, 2018, 9:56am

i used below c# code for webdriver wait. it’s working fine.

WebDriverWait Wait = new WebDriverWait(driver, TimeSpan.FromMinutes(2));

Wait.Until(ExpectedConditions.ElementToBeClickable(By.Id(“yourid”)));
driver.FindElement(By.Id(“yourid”)).Click();