swipe not act as expected

[truebit]

Description

trying to use element.swipe(UP, duration);, but the undergoing swipe(int startx, int starty, int endx, int endy, int duration) does not work as expected

Environment

• java client build version or git revision if you use some shapshot: 3.4.0
• Appium server version or git revision if you use some shapshot: 1.5.0
• Desktop OS/version used to run Appium if necessary: Mac OSX 10.11
• Node.js version (unless using Appium.app|exe) or Appium CLI or Appium.app|exe: 5.6.0
• Mobile platform/version under test: iPhone 9.2.1
• Real device or emulator/simulator: 6s plus

Details

I was trying to do element.swipe(UP, duration).
According to the debug level logs, after some getLocation and getSize requests , appium called swipe(int, int,int,int,int) as below:

[MJSONWP] Calling AppiumDriver.performTouch() with args: [[{"action":"press","options":{"x":207,"y":439}},{"action":"wait","options":{"ms":1000}},{"action":"moveTo","options":{"x":207,"y":298}},{"action":...

it was a correct swipe up action. but following logs showed that it interpreted the actions wrong to following commands:

[debug] [iOS] Executing iOS command 'performTouch'
[debug] [UIAuto] Sending command to instruments: target.touch([{"touch":[{"x":207,"y":439}],"time":0.2},{"touch":[{"x":207,"y":439}],"time":1.2},{"touch":[{"x":414,"y":737}],"time":1.4}])
[debug] [Instruments] [INST] 2016-03-29 08:44:34 +0000 Debug: Got new command 18 from instruments: target.touch([{"touch":[{"x":207,"y":439}],"time":0.2},{"touch":[{"x":207,"y":439}],"time":1.2},{"touch":[{"x":414,"y":737}],"time":1.4}])
[debug] [Instruments] [INST] 2016-03-29 08:44:34 +0000 Debug: evaluating target.touch([{"touch":[{"x":207,"y":439}],"time":0.2},{"touch":[{"x":207,"y":439}],"time":1.2},{"touch":[{"x":414,"y":737}],"time":1.4}])
[debug] [Instruments] [INST] 2016-03-29 08:44:34 +0000 Debug: target.touch(__NSCFArray)
[debug] [Instruments] [INST] 2016-03-29 08:44:35 +0000 Debug: point is not within the bounds of the screen
[debug] [UIAuto] Socket data received (70 bytes)
[debug] [UIAuto] Got result from instruments: {"status":17,"value":"point is not within the bounds of the screen"}
[HTTP] <-- POST /wd/hub/session/47695b97-9182-4258-a23b-a0f478210510/touch/perform 500 1763 ms - 131
[debug] [Instruments] [INST] 2016-03-29 08:44:35 +0000 Error: VerboseError: point is not within the bounds of the screen

please notice these commands were not swipe UP, but DOWN. and for the y:737 part, the screen size was only (414,736)

Code To Reproduce Issue [ Good To Have ]

no need

Ecxeption stacktraces

Please create a gist with pasted stacktrace of exception thrown by java.

Link to Appium logs

[TikhomirovSergey]

@truebit
Hi.
It is the server side bug which has been reported already.
appium/appium#6292
appium/appium#6299

[truebit]

After going through all these bug descriptions and related java-client source code. I think it's not server side bug.
It's the bug from java-client which does not adapt the new swipe logic in appium 1.5.
How to fix: rewrite the methods getEndX and getEndY in io.appium.java_client.SwipeElementDirection class to return relative coordinates of end x and end y

[TikhomirovSergey]

Ok. Now I've got it. I think that some refactoring is needed because the same method is used by Android and iOS now. Android still uses absolute coordinates. It seems that the swiping should be implemented differently.

[go2guy]

@TikhomirovSergey is there a workaround for swipe until 4.0.0 is released?

[truebit]

@nuggit32 You can override swipe(int startx, int starty, int endx, int endy, int duration) to something like:

new TouchAction(getDriver()).press(startx, starty).waitAction(duration).moveTo(endx - startx, endy - starty).release().perform();