question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Failed to locate open application window issue appID and Processid.

See original GitHub issue

Hi,

I am having a problem with an application, I’ve successfully managed sessions for other apps using the root session. This app is behaving differently though for that code path just at the basic launch app steps, the app when launched manually seems to from monitoring task manager getting and retaining the same process ID.

However when run through a coded WinAppDriver session, I can see the session launch with a processID and then it closes then my code crashes.

` var capabilities = new AppiumOptions();

        capabilities.AddAdditionalCapability(MobileCapabilityType.App, @"C:\Program Files\QDAQ\QDAQ.exe");
        capabilities.AddAdditionalCapability(MobileCapabilityType.PlatformName, "Windows");
        capabilities.AddAdditionalCapability(MobileCapabilityType.DeviceName, "NOELF-L-W10");

        WindowsDriver<WindowsElement> session = new WindowsDriver<WindowsElement>(new Uri("http://127.0.0.1:4723"), capabilities);`

I am not really sure how to handle this, do I need to somehow ignore the initial process ID?

I am getting some developer help this afternoon but wanted to know if there was a standard way to address this.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:7

github_iconTop GitHub Comments

1reaction
Noelf21commented, Jul 28, 2020

Yes we used Nlog for this application, we’ve narrowed the problem now to the launching through WinAppDriver the app launches but then checks for the Nlog.config file in the Windows Application Driver root instead where it should be looking in the app directory. On reflection it’s probably not a WinAppDriver issue.

image

0reactions
anunay1commented, Jul 28, 2020

“Nlog file path can’t be found” are you using Nlog for logging?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Failed to locate opened application window with appId"xxx" ...
WinAppDriver by default tries to locate the first top-level window with the same processID. It looks like WinAppDriver was unable to determine ...
Read more >
Failed to locate opened application window with appId - ...
Hi, I'm new a beginner in the katalon studio, So I'm facing some issues while running the test cases. I'm trying to start...
Read more >
Code is not able to locate my application - Support
And when I run my code , I am getting error as. Failed to locate opened application window with appId: C:\Windows\System32\calc.exe, ...
Read more >
OpenQA.Selenium.WebDriverException : Failed to locate ...
taskschd test issue: OpenQA.Selenium.WebDriverException : Failed to locate opened application window with appId: C:\\WINDOWS\\System32\\taskschd ...
Read more >
What application types are supported by winappdriver
Winappdriver can start executables (generally .exe files on Windows). I suspect your .msc file is a management saved console?
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found