WebView2 Issues with WinAppDriver

[Ahamed-Ali]

In Windows, when a WinUI app has WebView2, Appium does not connect to the app for inspection. It shows only the loading screen. After a long time, it throws this error.

So I have logged the issue with the Appium appium/appium#22217

Further investigation revealed that WinAppDriver is encountering an issue where the source endpoint returns a 500 Internal Server Error in this case.

Reference : appium/appium#22217 (comment)

I have attached the logs below

appium2withWebView (1).txt

Appium2withoutwebview (1).txt

For more information, Please refer this issue report appium/appium#22217

[TimVanDyke]

Experiencing the same issue, is this library maintained anymore?

[projectsbyandy]

Just a suggestion, have you tried launching the program and then using playwright for automating the webview2 content? I did something similar for new outlook

[TimVanDyke]

Hey I appreciate the suggestion. In our case we're actually testing everything around the web view in our app, it's primarily a windows native app. Whatever changed in April is preventing our stack from attaching to the app on pages where there is a web view in place. If we were trying to test the contents of the web view we definitely would try that.

[liljohnak]

Tim Van Dyke (@TimVanDyke) no I don't think it is maintained anymore.

[hiSandog]

For WebView2 cases, the useful split is whether WinAppDriver cannot attach to the top-level WinUI app, or whether it attaches but cannot enumerate the WebView2 subtree. Please include the WebView2 runtime version, the Appium/WinAppDriver session capabilities, and whether the same app can be inspected before the WebView2 control is created. That would narrow this down to a WebView2 accessibility/UIA exposure issue versus a session startup timeout.