[BUG] iOS Appium “ dragfromtoforduration” function failed , while calling this in webdrvieragent(facebook) works well #7672

Open
huanglik opened this Issue Jan 10, 2017 · 6 comments

Projects

None yet

3 participants

@huanglik

when i write test for iOS Appium using “ dragfromtoforduration” function
it doesn‘t work
I check the server log of appium, it wronglly changes the “toY” and “toX” to call wda
client send fromX,fromY(160,85.2) endX,endY(160,511.2)

but appium changes the value of endX,endY to (320, 596.4)
thus that my test fail !!!!!!!!

image

At the same time,i using this command to test wda, it works well

curl -X POST -d '{"fromX": "160", "fromY": "85.2", "toX":"160", "toY":"511.2" ,"duration":"0.8"}' 'http://localhost:8100/session/7EFFFFB1-CA11-48B2-A91D-03B9F62EE251/uiaTarget/0/dragfromtoforduration'

hope appium fix that, thanks a lot

@triager triager added the NeedsTriage label Jan 10, 2017
@mykola-mokhnach
Collaborator
mykola-mokhnach commented Jan 10, 2017 edited

Can you paste your code snipped for appium client? Maybe, TouchAction interface just calculates coordinates differently from what you expect?

@huanglik

In appium client , my code is
driver.swipe(160,85.2,160,511.2,800)
it‘s nothing wrong with TouchAction interface 。

you can see the appium server log。
MSJSONWP prints the right fromX,fromY 、endX,endY
however
JSONWP Proxy changes the value endX,endY

I think problem is in JSONWP Proxy,can you help me?

@mykola-mokhnach
Collaborator

Just be kind to provide what I've asked. I won't be able help without the log and full code snippet.

@huanglik

appium client
def swipe(self, start_x, start_y, end_x, end_y, duration=None)
this function input arguments here declared is end_x and end_y (not offset_x, not offset_y)
image

however, in appium server, it changes my arguments end_x , end_y
it is end_x, end_y, not offset x, offset y, ok?
Obviously, it's bug of appium ( appium client code did not change for a long time)

image

image

@mykola-mokhnach
Collaborator

yes, this might be documentation issue. These values should be calculated as relative offsets to the recent touch point. You 're welcome to push a fix for that.

@huanglik

thank you so much
I am looking forward to see the code after you fix that, plesae comment back after you fix ok
thank you so much again

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