Appium windows app driver returns 200 on "click" but doesn't actually perform the click

[SimiNagrani28]

This is similar to what we are using:

WebDriverWait wait = new WebDriverWait(driver, Duration.ofSeconds(timeOutInSeconds));
wait.until(ExpectedConditions.elementToBeClickable(AppiumBy.accessibilityId(idValue)));
element = driver.findElement(AppiumBy.accessibilityId(idValue));
element.click();

This is working fine on Windows 11 but on windows 10 it returns response 200 but doesn't actually click on the element.

Appium version - v2.13.1

Appium logs: https://gist.github.com/SimiNagrani28/0089749f95a3e831d66c74e4a8affb15

I had opened the issue with Appium https://github.com/appium/appium/issues/20894 but this was the response:

After proxying the click request to the WinAppDriver, the actual behavior depends on https://github.com/microsoft/WinAppDriver. Please consider reporting it to the driver.

[d8371227][HTTP] --> POST /wd/hub/session/d8371227-3bc7-44c2-92f8-552290484724/element/42.394030.4.90/click {"id":"42.394030.4.90"}
[d8371227][WindowsDriver@f0a6] Driver proxy active, passing request on via HTTP proxy
[d8371227][WindowsDriver@f0a6] Matched '/wd/hub/session/d8371227-3bc7-44c2-92f8-552290484724/element/42.394030.4.90/click' to command name 'click'
[d8371227][WindowsDriver@f0a6] Proxying [POST /wd/hub/session/d8371227-3bc7-44c2-92f8-552290484724/element/42.394030.4.90/click] to [POST http://127.0.0.1:4724/wd/hub/session/E293D0BE-7853-4F69-975B-E23E4108AFE5/element/42.394030.4.90/click] with body: {"id":"42.394030.4.90"}
[d8371227][WindowsDriver@f0a6] ==========================================
POST /wd/hub/session/E293D0BE-7853-4F69-975B-E23E4108AFE5/element/42.394030.4.90/click HTTP/1.1

[anunay1]

Can you check the page source? Also can you try clicking with co-ordinates.