android and ios treat touchaction coordinates differently (relative vs absolute)

[TikhomirovSergey]

The problem

The problem is that the swiping on Android still consumes absolute values instead of relative (like iOS).
However the moveTo action consumes relative values on both Android and iOS. So it makes inconvenience on client side.

Also there is some weird behaviour.
When user tries to perform the swiping twise (may be more times) per one TouchAction then it fails with error that says that point is out of screen.

Environment

• Appium version 1.6.0, 1.6.1 and older:
• Desktop OS/version used to run Appium: I was trying it on Windows 7/8
• Node.js version (unless using Appium.app|exe): doesn't matter
• Mobile platform/version under test: Android
• Real device or emulator/simulator: Emulator

Details

I think the solution is to make the swiping accept relative coordinate values or to stop support it.

Link to Appium logs

Create a gist which is a paste of your full Appium logs, and link them here. Do not paste your full Appium logs here, as it will make this issue very long and hard to read! If you are reporting a bug, always include Appium logs!

Code To Reproduce Issue [ Good To Have ]

The client code

driver.findElementByAccessibilityId("Views").click();

AndroidElement chronometer = driver.findElementByAccessibilityId("Chronometer");
Point point1 = chronometer.getCenter();
int x1 = point1.getX();
int y1 = point1.getY();

AndroidElement focus = driver.findElementByAccessibilityId("Focus");
Point point2 = focus.getCenter();
int x2 = point2.getX();
int y2 = point2.getY();

TouchAction touchAction = new TouchAction(driver);
touchAction.press(x2, y2).waitAction(2000).moveTo(x1, y1).release()//swipe 1
           .press(x1, y1).waitAction(2000).moveTo(x2, y2).release() //swipe 2, seems it needs for relative values
           .perform();

server logs

However this code works

        driver.findElementByAccessibilityId("Views").click();

        AndroidElement chronometer = driver.findElementByAccessibilityId("Chronometer");
        Point point1 = chronometer.getCenter();
        int x1 = point1.getX();
        int y1 = point1.getY();

        AndroidElement focus = driver.findElementByAccessibilityId("Focus");
        Point point2 = focus.getCenter();
        int x2 = point2.getX();
        int y2 = point2.getY();

        TouchAction touchAction1 = new TouchAction(driver);
        touchAction1.press(x2, y2).waitAction(2000).moveTo(x1, y1).release().perform();

        TouchAction touchAction2 = new TouchAction(driver);
        touchAction2.press(x1, y1).waitAction(2000).moveTo(x2, y2).release()
                .perform();

server log

[SrinivasanTarget]

@triager please label:Bug, Android

[SrinivasanTarget]

@sravanmedarapu @imurchie Can you please look into this?

[jlipps]

android and ios should definitely follow the same semantics.

[saikrishna321]

@jlipps i see this issue on iOS side as well, with the below code it works fine - scroll down(legacy)
server logs are shows the right co-ordinates

Dimension dimensions = driver.manage().window().getSize();
Double screenHeightStart = dimensions.getHeight() * 0.5    
int scrollStart = screenHeightStart.intValue();
Double screenHeightEnd = dimensions.getHeight() * 0.30;
int scrollEnd = screenHeightEnd.intValue();
 driver.swipe(0, scrollStart, 0, scrollEnd, 1000);

[debug] [MJSONWP] Calling AppiumDriver.performTouch() with args: [[{"action":"press","options":{"x":0,"y":284}},{"action":"wait","options":{"ms":1000}},{"action":"moveTo","options":{"x":0,"y":-114}},{"action":"release","options":{}}],"9cf39378-bb3b-4720-956e-ee119290d586"]
[debug] [iOS] Executing iOS command 'performTouch'
[debug] [UIAuto] Sending command to instruments: au.dragApp(0, 284, 0, 170, 1)
[debug] [Instruments] [INST] 2017-03-06 05:50:29 +0000 Debug: Got new command 99 from instruments: au.dragApp(0, 284, 0, 170, 1)
[debug] [Instruments] [INST] 2017-03-06 05:50:29 +0000 Debug: evaluating au.dragApp(0, 284, 0, 170, 1)
[debug] [Instruments] [INST] 2017-03-06 05:50:29 +0000 Debug: target.dragFromToForDuration({x:"0", y:"284"}, {x:"0", y:"170"}, "1")
[debug] [Instruments] [INST] 2017-03-06 05:50:30 +0000 Debug: evaluation finished
[debug] [Instruments] [INST] 2017-03-06 05:50:30 +0000 Debug: responding with:
[debug] [Instruments] [INST] 2017-03-06 05:50:30 +0000 Debug: Running system command #100: /usr/local/Cellar/node/7.5.0/bin/node /usr/local/lib/node_modules/appium/node_modules/appium-uiauto/build/lib/bin/command-proxy-client.js /var/folders/yx/q5fqv2j55_ddwj2m5_x8jv7h0000gn/T/instruments_sock 2,{"status":0,"value":""}...
[debug] [UIAuto] Socket data received (25 bytes)
[debug] [UIAuto] Got result from instruments: {"status":0,"value":""}
[debug] [MJSONWP] Responding to client with driver.performTouch() result: ""
[HTTP] <-- POST /wd/hub/session/9cf39378-bb3b-4720-956e-ee119290d586/touch/perform 200 1856 ms - 74
[HTTP] --> POST /wd/hub/session/9cf39378-bb3b-4720-956e-ee119290d586/touch/perform {"actions":[{"action":"press","options":{"x":0,"y":284}},{"action":"moveTo","options":{"x":160,"y":-252}},{"action":"release","options":{}}]}

With TouchActions it does not work on iOS but works on Android

new TouchAction(driver).press(0, scrollStart).
                    moveTo(0,scrollEnd).release().perform();

[debug] [MJSONWP] Calling AppiumDriver.performTouch() with args: [[{"action":"press","options":**{"x":0,"y":284}},{"action":"moveTo","options":{"x":0,"y":170}}**,{"action":"release","options":{}}],"9cf39378-bb3b-4720-956e-ee119290d586"]
[debug] [iOS] Executing iOS command 'performTouch'
[debug] [UIAuto] Sending command to instruments: target.touch([{"touch":**[{"x":0,"y":284}],"time":0.2},{"touch":[{"x":0,"y":454}]**,"time":0.4}])
[debug] [Instruments] [INST] 2017-03-06 05:51:33 +0000 Debug: Got new command 101 from instruments: target.touch([{"touch":[{"x":0,"y":284}],"time":0.2},{"touch":[{"x":0,"y":454}],"time":0.4}])
[debug] [Instruments] [INST] 2017-03-06 05:51:33 +0000 Debug: evaluating target.touch([{"touch":[{"x":0,"y":284}],"time":0.2},{"touch":[{"x":0,"y":454}],"time":0.4}])
[debug] [Instruments] [INST] 2017-03-06 05:51:33 +0000 Debug: target.touch(__NSCFArray)
[debug] [Instruments] [INST] 2017-03-06 05:51:33 +0000 Debug: evaluation finished
[debug] [Instruments] [INST] 2017-03-06 05:51:33 +0000 Debug: responding with:
[debug] [Instruments] [INST] 2017-03-06 05:51:33 +0000 Debug: Running system command #102: /usr/local/Cellar/node/7.5.0/bin/node /usr/local/lib/node_modules/appium/node_modules/appium-uiauto/build/lib/bin/command-proxy-client.js /var/folders/yx/q5fqv2j55_ddwj2m5_x8jv7h0000gn/T/instruments_sock 2,{"status":0,"value":""}...
[debug] [UIAuto] Socket data received (25 bytes)
[debug] [UIAuto] Got result from instruments: {"status":0,"value":""}
[debug] [MJSONWP] Responding to client with driver.performTouch() result: null
[HTTP] <-- POST /wd/hub/session/9cf39378-bb3b-4720-956e-ee119290d586/touch/perform 200 1587 ms - 76

client sends y:170 and target.touch(takes it as 454)

@TikhomirovSergey

[TikhomirovSergey]

UPD: The swipe is not supported now. So the problem is moveTo. It seems that it it should accept absolute coordinates for all supported platfoms.

ping @mykola-mokhnach

[mykola-mokhnach]

This has been now merged to beta

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.