Closed Pegieo closed 6 months ago
Try to add 'automationName' capability as well
Try to add 'automationName' capability as well
It still does not work.
If you are trying to use this client without Appium itself then it won't work as WAD does not support the W3C protocol.
But it worked with version 4.4.5 🤔
Which appium version are you using?
WinAppDriver v1.2.1 but also tried v1.3
I meant appium server driver. See this section on the Readme https://github.com/appium/dotnet-client#winappdriver-notice
Yes, using Appium instread of WinAppDriver directly resolved that problem. However, I got stuck with other issues for now e.g. https://github.com/microsoft/WinAppDriver/issues/1886 Thanks for help!
@Pegieo, Can I close this issue?
Description
Could not create WindowsDriver to start session with Windows applicaction. The code below throws exception: "OpenQA.Selenium.WebDriverArgumentException : Bad capabilities. Specify either app or appTopLevelWindow to create a session"
Environment
Windows, Desktop Appium.WebDriver" Version="5.0.0-rc.2"
Details
It works with version 4.4.5
Code To Reproduce Issue