Android - Tap doesn't work correctly on Imageview

Support
1

Hi, I would like to click on a ImageView. This Imageview has attribute clickable to false, for this reason I am trying to use tap:

Appium v1.21.0 /// Android
new TouchAction(driver).tap(new PointOption().withCoordinates(400,900)).perform();

I have my device configured to see where I clink on screen. With the line before I can see that tap where it should be but its like not “clicked”, nothing happen.

Should I use another action?
Thanks

I attach an image from UI Automator Viewer

This is what get from Terminal:
[HTTP] --> POST /wd/hub/session/9a7c8a59-d335-4d06-a5f9-ca497e9606d6/touch/perform

[HTTP] {“actions”:[{“action”:“tap”,“options”:{“x”:400,“y”:900}}]}

[debug] [W3C (9a7c8a59)] Calling AppiumDriver.performTouch() with args: [[{“action”:“tap”,“options”:{“x”:400,“y”:900}}],“9a7c8a59-d335-4d06-a5f9-ca497e9606d6”]

[debug] [WD Proxy] Proxying [POST /appium/tap] to [POST http://127.0.0.1:8200/wd/hub/session/4e5cbbdb-a2c9-498c-8dfd-e73710958eb1/appium/tap] with body: {“x”:400,“y”:900,“undefined”:null}

[debug] [WD Proxy] Got response with status 200: {“sessionId”:“4e5cbbdb-a2c9-498c-8dfd-e73710958eb1”,“value”:null}

[debug] [W3C (9a7c8a59)] Responding to client with driver.performTouch() result: null

[HTTP] <-- POST /wd/hub/session/9a7c8a59-d335-4d06-a5f9-ca497e9606d6/touch/perform 200 142 ms - 14

10
Captura de pantalla 2021-07-01 a las 14.31.10.jpg2870×1470 528 KB

2

It could be that this fragment is intentionally made non-accessible because of security reasons. You could also try to enter PIN by sending appropriate keys as a possible workaround.

3

Thank you!
I can insert the PIN now with sendingKeys but I need to push “Enter” button, any idea?

Thank you again!

4

I would try https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/android/android-ime.md or to emulate the corresponding physical button press. This actually depends on the actual internal implementation of that control.

5

It doesn’t work, even using adb with “adb shell input keyevent 66”, nothing happens :disappointed_relieved:

Looks like there is a protection or something to avoid this :thinking:

6

I wouldn’t be surprised if there is to avoid brute-forcing PIN