driver.page_source throws 500 error after connecting to the app with "appTopLevelWindow" param

[bwomsm1]

I need to use the functionality which attaches to a valid Win app running process and window.
I found that the flag appTopLevelWindow is not supported in the latest release of 1.2.1.
But after installing https://github.com/microsoft/WinAppDriver/releases/tag/v1.2.99 I noticed that C:\Program Files (x86)\Windows Application Driver folder remains empty.

[bwomsm1]

@anunay1 Can you please help with this issue?

[bxw0531]

@anunay1 I don't really care using version 1.2.1 its just that I need to attach to a valid running Win app process.
I have the running app hex window handler but I am getting an error that the http request for attaching is not supported.

Can you please help with that?

[bwomsm1]

@timotiusmargo can you please help me with accessing my app driver.page_souce? I manage to pass webdriver.Remote() but I get

Message: Request failed with status code 500
Stacktrace:
UnknownError: Request failed with status code 500
    at ProxyRequestError.getActualError (C:\Users\qahw\AppData\Roaming\npm\node_modules\appium\node_modules\@appium\base-driver\lib\protocol\errors.ts:960:12)
    at WADProxy.proxyReqRes (C:\Users\qahw\AppData\Roaming\npm\node_modules\appium\node_modules\@appium\base-driver\lib\jsonwp-proxy\proxy.js:407:58)
    at processTicksAndRejections (node:internal/process/task_queues:105:5)

when I am calling to driver.page_source.
I am running my appium server as a administrator.

[TwLife]

I have implemented a proxy layer to convert the W3C format request messages initiated by Selenium4.39 into the format required by WinAppDriver. Currently, a basic connection has been successfully established. You can also try this approach in Appium.