Open mooragor opened 6 months ago
Is the developer mode ON? What kind of application is this win32, WPF or UWP? please go through the wiki?
Hi there - Developer mode is on. Ultimately I will be testing a WPF application, but I am getting these results when I try to start Notepad.exe
I have now had a go at cloning the WinAppDriver repo, and managed to successfully run the Notepad 'test' in there after standing up WinAppDriver.exe by itself, so I'm pretty sure there's not actually a problem with WinAppDriver by itself, maybe I need to move this question to an Appium forum as it may well be the Appium layer that I'm using incorrectly to pass the parameters through to WinAppDriver.
One thing I do notice as fairly different between the Appium example that I'm following and the Notepad Test code from the repo is that the Test code is using DesiredCapabilities(), where the Appium example is using AppiumOptions()
Both seem to be using OpenQA.Selenium.Appium.Windows, but I'm wondering if I've somehow got different versions of the package somehow.
There is an existing bug with appium where in it installs the winappdriver.exe at wrong location. Better to install winappdriver.exe first and then install appium.
As a bit of a final note on this. I eventually discovered that it was my application taking too long to start up, and WinAppDriver just thought it hadn't started properlt.
I added the following code to the DesiredCapabilities and it now can start my application
capabilities.SetCapability("ms:waitForAppLaunch", "10");
Please keep in mind that the maximum time out supported is 50 seconds.
I got same error running tests on Windows Server 2022, resolved it by unistalling WinAppDriver v1.2.99 and installed v1.2.1
@juzin's solution worked for me \o/
Hi there. I'm completely new to Appium/WinAppDriver, trying it for the first time, so apologies if I'm doing something really silly.
I've tried starting WinAppDriver by running Appium, and also by itself, but seem to be getting this same error whenever I try to use it or call Status on a process.
Below is my best guess at a reproduction without appium being involved, I think I'm starting it the same way Appium is, with the same parameters.
I have absolutely no idea where to even start working out what's going wrong, so any suggestions gratefully received!
Appium v2.5.1 WindowsDriver's BaseDriver version is 9.5.2 Node v21.1.0
Starting Appium gets the same sort of responses