Windows: Discrepancy in API When Launching Application vs. Attaching to Existing Application

The problem

Preface: I am using Appium/WebDriverIO to test a native application, specifically on Windows.

I have two testing scenarios:

1. Having Appium launch a Windows application
2. Having Appium attach to an existing application

Both are possible with the Windows Appium Driver (the former being most common). Specifically, using the appTopLevelWindow capability.

I run the exact same test code in both instances. However, when I attach to an existing application, one of the API’s I use doesn’t work (500 internal error).

Specifically, the touchScroll, which is apart of the JSON Wire Protocol. And which the Windows Application Driver has full capacity to handle.

Summarize: I am running the exact same test code in two different instances. One when I have Appium launch an application, and one when I have Appium attach to an application. The latter causes a 500: internal error error when using the touchScroll API. An API that I had never had problem with before trying to attach to an application.

Environment

• Appium version (or git revision) that exhibits the issue: “appium”: “2.0.0-beta.41”
• Last Appium version that did not exhibit the issue (if applicable):
• Desktop OS/version used to run Appium: Windows 10
• Node.js version (unless using Appium.app|exe): Node v14.20
• Npm or Yarn package manager: Npm v8
• Mobile platform/version under test: Windows
• Real device or emulator/simulator:
• Appium CLI or Appium.app|exe: Via WebDriverIO

Details

If necessary, describe the problem you have been experiencing in more detail.

Link to Appium logs

Please see LOG

[samuelfreiberg]

@bwomsm1 I have not. I’ve looked in the logs. The API [POST] calls are the exact same. I’m not sure what is going wrong. My only thought is something with the driver gets spawned differently with Appium when launching the application itself vs. attaching.

I don’t think this is a WinAppDriver issue. My assumption is something with the Appium Windows Driver, but I can’t put my finger on it and it’s driving me crazy.

[bwomsm1]

@samuelfreiberg my scenario is when the appium driver reaches driver_.find_element method