Application under test was upgraded to .net 4.8 and all element requests are timing out

The dev team at my org upgraded their WinForms app to .net version 4.8 and all element requests began timing out. The timeout is on the call to find the element and no response is returned after 60 seconds and the server times out. I tried raising the timeout to 4 min but it still times out. It was all working prior to the .net upgrade. Other commands such as windows maximizing and getting title of window still works. But anything involving FindElement times out. I tried also modifying the version to 1.2.99 and using ms:experimental-webdriver: true. Has anyone experienced this before or have any ideas of what could cause this to be the case?

Using: Selenium 4.0.1 with WinAppDriver v1.2.1/v1.2.99 and Appium v5.0.0-beta01

Sample of Logs from Appium where element call is made and connection times out:

2022-02-22 19:43:05:595 [HTTP] <-- GET /wd/hub/session/5b0c7fc5-5cda-4300-8172-ffde6e1ec076/title 200 27 ms - 81
2022-02-22 19:43:05:596 [HTTP] 
2022-02-22 19:43:05:627 [HTTP] Request idempotency key: 6a444302-74f3-4553-a280-c4ce5172190e
2022-02-22 19:43:05:629 [HTTP] --> POST /wd/hub/session/5b0c7fc5-5cda-4300-8172-ffde6e1ec076/element
2022-02-22 19:43:05:629 [HTTP] {"using":"xpath","value":"//*[@AutomationId='txtClaimID']"}
2022-02-22 19:43:05:631 [W3C (5b0c7fc5)] Calling AppiumDriver.findElement() with args: ["xpath","//*[@AutomationId='txtClaimID']","5b0c7fc5-5cda-4300-8172-ffde6e1ec076"]
2022-02-22 19:43:05:632 [BaseDriver] Valid locator strategies for this request: xpath, id, name, class name, accessibility id
2022-02-22 19:43:05:632 [WD Proxy] Matched '/element' to command name 'findElement'
2022-02-22 19:43:05:633 [WD Proxy] Proxying [POST /element] to [POST http://127.0.0.1:4724/wd/hub/session/009498D5-33C1-4C43-A5C7-E411B05AB27F/element] with body: {"using":"xpath","value":"//*[@AutomationId='txtClaimID']"}
2022-02-22 19:43:05:635 [WinAppDriver] ==========================================

2022-02-22 19:43:05:635 [WinAppDriver] POST /wd/hub/session/009498D5-33C1-4C43-A5C7-E411B05AB27F/element HTTP/1.1


2022-02-22 19:43:05:635 [WinAppDriver] Accept: application/json, */*


2022-02-22 19:43:05:635 [WinAppDriver] Connection: keep-alive


2022-02-22 19:43:05:635 [WinAppDriver] Content-Length: 59


2022-02-22 19:43:05:636 [WinAppDriver] Content-Type: application/json; charset=utf-8


2022-02-22 19:43:05:636 [WinAppDriver] Host: 127.0.0.1:4724


2022-02-22 19:43:05:636 [WinAppDriver] User-Agent: appium


2022-02-22 19:43:05:636 [WinAppDriver] 


2022-02-22 19:43:05:636 [WinAppDriver] {"using":"xpath","value":"//*[@AutomationId='txtClaimID']"}
2022-02-22 19:44:05:641 [HTTP] <-- POST /wd/hub/session/5b0c7fc5-5cda-4300-8172-ffde6e1ec076/element - - ms - -
2022-02-22 19:44:05:641 [HTTP] 
2022-02-22 19:44:05:642 [HTTP] Could not cache the response identified by '6a444302-74f3-4553-a280-c4ce5172190e', because it has not been completed
2022-02-22 19:44:05:642 [HTTP] Does the client terminate connections too early?

[Shakevg]

I am also using .Net Framework 4.8 with WinAppDriver for several years and didn’t have any issues

[VinayBerry]

@anunay1 yeah its app specific I have also run that experiment of targeting a hello-world app on 4.8 and everything worked ok. I worked around it a little by directly using accessibility ids/names instead of xpath, I guess it was just too slow after the 4.8 upgrade for whatever reason. But there’s still issues when the app is spending a lot of time loading the appium connection tends to trigger a timeout. Still havent found a way around that unfortunately.