Finding element (singular) using xpath does not return single element results (Android)

[glorylo]

I tried doing a simple find element via xpath and a predicate of [1]. However I get back 3 elements so finding element does not evaluate the predicate correctly.. This is for android

[glorylo]

Note I am using 1.3-beta build

[bootstraponline]

Is this fix in the beta build?

[jlipps]

@bootstraponline yes

[glorylo]

I just tried the same search on 1.2.0 and it works. So something has changed in 1.3.0-beta

[jlipps]

can you try on 1.2.3?

[paymand]

@jlipps: I think you meant 1.2.4 ?

[jlipps]

well at the time i wrote that 1.2.4 wasn't out yet, but yes now i mean 1.2.4 :-)

[glorylo]

Sorry I'm stuck with "could not launch appium inspector" after trying to get 1.2.4 and it doesn't launch in 1.3.0-beta either. :( I wasn't able to do the same test.

[glorylo]

Err...I don't know why the inspector is not launching... I want to retry the finds.

[glorylo]

I don't know what was the inspector issue.. i did an Mac update and it resolve it. Weird!

And I can confirm it does not work on 1.2.4. (it works on 1.2.0)

[JessicaSachs]

Let me know what the status is on this -- I think I'm seeing similar things and can provide logs if needed,

[Jonahss]

I think there is a basic misunderstanding of how xpath works.
//android.widget.FrameLayout[1] does NOT mean "get the first FrameLayout node". It means "get all the FrameLayout nodes which are the first child of their parent".

If you want the first FrameLayout, this is the xpath expression you would use:
(//android.widget.FrameLayout)[1]

In which case, not a bug?

http://stackoverflow.com/questions/3674569/how-to-select-specified-node-within-xpath-node-sets-by-index-with-selenium

[glorylo]

Thanks Jonah. The xpath used had a unintended intent to retrieve the element. There is still behavior difference from 1.2.4 vs 1.2.0 using that same xpath, so something is off. May likely be resolved once we know what the issue is.

[Jonahss]

We messed around with xpath implementation a bit around 1.2.0 to 1.2.3 I'm pretty sure, but it should be stable going forward :)

[0x1mason]

@Jonahss Can we close this?

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.