Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Description: Multiple elements were matched - waitfor Error #1384

Closed
calcazar opened this issue May 14, 2019 · 2 comments
Closed

Description: Multiple elements were matched - waitfor Error #1384

calcazar opened this issue May 14, 2019 · 2 comments

Comments

@calcazar
Copy link

Describe the bug
await waitFor(element(by.id("someID"))).toBeVisible(); await waitFor(element(by.id(someOtherID)).atIndex(0)) .toBeVisible() .whileElement(by.id("someID")) .scroll(200, "down");

results in

"Description": Multiple elements were matched:

when there are multiple "someOtherID" elements. It looks like it's ignoring atIndex

To Reproduce

  • [X ] I have tested this issue on the latest Detox release and it still reproduces

Provide the steps necessary to reproduce the issue. If you are seeing a regression, try to provide the last known version where the issue did not reproduce.

Perform a waitFor and a scroll for an element that displays multiple times on the screen

If possible, please provide a small demo project that reproduces the issue, or attach a video with the reproduction - this would be very appreciated.

Expected behavior
It should not throw Multiple Elements were matched error

Screenshots

Environment (please complete the following information):

  • Detox: 12.7.0
  • React Native: 57.3
  • Node: 10.14.2
  • Device: iPhone 7
  • Xcode: 10.2
  • iOS: 12.2
  • macOS: Mojave
@LeoNatan
Copy link
Contributor

We have a test in the demo suite that tests atIndex().
Please provide a clean project where this reproduces. Thanks

@no-response
Copy link

no-response bot commented May 22, 2019

This issue has been automatically closed because there has been no response to our request for more information from the original author.

@no-response no-response bot closed this as completed May 22, 2019
@lock lock bot locked as resolved and limited conversation to collaborators May 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants