Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Difference behaviour between iOS and Android regarding with `swipe` action #7702
I've investigated about
from appium/ruby_lib#461 (comment)
I checked swipe's logs for Android and iOS. Then I found the difference between them.
For Android, the following command's
swipe(start_x: start_x, start_y: start_y, offset_x: start_y, offset_y: offset_y)
command and logs on Appium1.6.3
Link to Appium logs
Attached the above.
case1: support only
referenced this issue
Jan 16, 2017
Thanks for investigating this @KazuCocoa. We should not have any discrepancies between the platforms. It seems to me that the server should deal in absolute values, and if clients want to deal in offsets, they are free to provide the ability to do so. @imurchie do you agree? I tried to read the current webdriver spec for guidance but it has diverged so much from the implementation of TouchAction we use it was hard to follow.
This is also the case with the python library. There was apparently a point in time (during 1.4) where the TouchAction for iOS used absolute values. After 1.5, swipe for IOS has been taking relative values for end_x and end_y... not sure if this is the intended behavior or not.
We don't need to change the python client since the client sends it to the server without any calculations in client side.