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

TouchAction.moveTo() assumes relative coordinates on iOS and absolute coordinates on Android #5847

rshanley opened this Issue Nov 18, 2015 · 4 comments


None yet
7 participants
Copy link

rshanley commented Nov 18, 2015

Using Appium Java Client 3.2.0

TouchAction.moveTo(int x, int y) assumes absolute coordinates on Android.

On iOS however it assumes relative coordinates.

This breaks the platform independence.

We recreated this with the following Java test:

new TouchAction(driver).longPress(start.getX(), start.getY()).moveTo(end.getX(), end.getY()).release().perform()

@triager triager added the NeedsTriage label Nov 18, 2015


This comment has been minimized.

Copy link

scottdixon commented Mar 8, 2016

@rshanley - please try Appium 1.5 npm install -g appium

Let me know if the issue persists.


This comment has been minimized.

Copy link

rshanley-micro-focus commented Jul 5, 2016

@scottdixon this issue still persists. we have been using a workaround.


This comment has been minimized.

Copy link

denniskpw commented Jul 8, 2016

Can confirm this is reproducible with the python client on Appium 1.5.3.


This comment has been minimized.

Copy link

dpgraham commented Dec 14, 2016

Closing. If this problem still occurs on Appium 1.6.x please post the error logs and I'll re-open it.

@dpgraham dpgraham closed this Dec 14, 2016

@imurchie imurchie removed the NeedsTriage label Jul 13, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment