-
-
Notifications
You must be signed in to change notification settings - Fork 211
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
Support touch actions that don't start with press #171
Comments
Seems easy to fix, I will get a PR with tests against this bug and a fix done tomorrow. |
tiagoshibata
added a commit
to tiagoshibata/appium-android-driver
that referenced
this issue
Jul 27, 2016
tiagoshibata
added a commit
to tiagoshibata/appium-android-driver
that referenced
this issue
Aug 9, 2016
tiagoshibata
added a commit
to tiagoshibata/appium-android-driver
that referenced
this issue
Aug 9, 2016
tiagoshibata
added a commit
to tiagoshibata/appium-android-bootstrap
that referenced
this issue
Aug 14, 2016
Support touch actions starting and ending at different moments
imurchie
added a commit
to appium-boneyard/appium-android-bootstrap
that referenced
this issue
Aug 23, 2016
tiagoshibata
added a commit
to tiagoshibata/appium-android-driver
that referenced
this issue
Aug 24, 2016
imurchie
added a commit
that referenced
this issue
Aug 24, 2016
Fixes #171, removes unused state.touch parameters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi all! I have one more request for a fix on touch actions.
The problem
For some specific tests I'd like to be able to start a drag action and then zoom in the screen (start with a single finger and later touch another finger). The following Python code exemplifies my desired behavior:
However, Appium crashes when the touch action doesn't start with a press checking the yet undefined x/y coordinates. In the example above, it crashes on the second contact, which starts with wait.
Environment
Link to Appium logs
Here, relevant parts:
Code To Reproduce Issue
Given above.
Could some of you provide a fix? I might try to get a PR done if you guys are busy with other issues.
Thanks!
The text was updated successfully, but these errors were encountered: