Can't find an element on the screen by using Android Find By

Issues/Bugs
1

hi,

There are several EditText in my screen and I want to specify them by uiAutomator , these are several ways I tried:
#approach 1
@AndroidFindBy(uiAutomator = “new UiSelector().className(“android.widget.TextView”).index(1)”)
@iOSFindBy(xpath = “//UIAApplication[1]/UIAWindow[1]/UIAScrollView[1]/UIAButton[3]”)
public WebElement garden;

#approach 2
androidDriver.findElementByAndroidUIAutomator(“new UiSelector().className(“android.widget.EditText”).index(0)”).sendKeys(“2”);

These 2 way cause a NoSuchElementException.

but this way works:
((WebElement)driver.findElementsByClassName(“android.widget.EditText”).get(0)).sendKeys(“2”);

I use java_client 3.0.0 and Appium server 1.4.0.0.

Any suggestions and discussion are welcomed, thanks!

2

paste the main log here:

org.openqa.selenium.NoSuchElementException: An element could not be located on the page using the given search parameters. (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 1.36 seconds
For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html
Build info: version: ‘2.46.0’, revision: ‘61506a4624b13675f24581e453592342b7485d71’, time: ‘2015-06-04 10:22:50’
System info: host: ‘58-PC’, ip: ‘10.58.36.26’, os.name: ‘Windows 7’, os.arch: ‘amd64’, os.version: ‘6.1’, java.version: ‘1.7.0_79’
*** Element info: {Using=-android uiautomator, value=new UiSelector().className(“android.widget.EditText”).index(2)}
Session ID: 5d88ccd2-733b-4d4c-bbd5-255a87467551
Driver info: io.appium.java_client.android.AndroidDriver
Capabilities [{platform=LINUX, javascriptEnabled=true, browserName=Android, networkConnectionEnabled=true, desired={deviceName=252e4425, platformName=Android, unicodeKeyboard=true, resetKeyboard=true}, locationContextEnabled=false, platformVersion=5.0, databaseEnabled=false, deviceName=252e4425, platformName=Android, webStorageEnabled=false, unicodeKeyboard=true, resetKeyboard=true, warnings={}, takesScreenshot=true}]
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:204)
at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:156)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:605)
at io.appium.java_client.DefaultGenericMobileDriver.execute(DefaultGenericMobileDriver.java:27)
at io.appium.java_client.AppiumDriver.execute(AppiumDriver.java:1)
at io.appium.java_client.android.AndroidDriver.execute(AndroidDriver.java:1)
at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:358)
at io.appium.java_client.android.AndroidDriver.findElementByAndroidUIAutomator(AndroidDriver.java:266)
at entity.house.publish.HousePublishPage.selectHouseType(HousePublishPage.java:168)

3

Simple way would be

List<…AndroidElements> L1 = driver.findElements(By.classname(“xyz”)):
For(AndroidElements e1:l1)
{

Put condition based on index
E1.sendkeys(“xyz”);

}

4

I know this way is simple and worked ,but I want to use one script for two platform(android and ios) so I prefer to use @AndroidFindBy and @iOSFindBy to achieve that.

5

I have got the TextViews on the screen by findElementsByAndroidUIAutomator, after that I use findElementByAndroidUIAutomator(“new UiSelector().className(”**").index(4)") to get the fifth item(I have confirmed that the fifth item exist) it still throw a NoSuchElementException.

till now ,seems we can locate the issue to be use index to locate an element?

Can anyone try this way and test if this is a common issue?

I can use other ways to go through this issue in my work ,but every issue fix will make appium better, let’s do that together.