🐞 bug: Appium server stuck when calling to driver.page_source

[bwomsm1]

Is there an existing issue for this?

• I have searched the existing issues

Appium Version

2.17.1

Appium Host Type

Command Line

Current Behavior

I am currently still using appium version 2.17.1, that because appium NovaWindow driver is not capable of running with the latest appium 3 version.

I am facing a problem that appium is launching successfully my windows app,
At this point I am trying to access my tested app Window by using driver.switch_to call.
In some point when I am switching between the windows and calling in each window switch to driver.page_source, the appium server is getting stuck and not responding back to driver.page_source call.

Expected Behavior

The page source of the current window should be generated and returned back.

Appium Log

https://github.com/bwomsm1/AppiumLogs/blob/master/get_page_source_stuck

Environment Details

• Debug details (appium --show-debug-info):
• Last component version(s) which did not exhibit the problem: it did work with appium windows driver
• Platform and version of device under test:windows

Minimal Reproducible Example

driver.Remote
driver_.switch_to.window(window)

then the appium server is stuck on that line:
[0fff501f][NovaWindowsDriver@84c4] Calling AppiumDriver.getPageSource() with args: ["0fff501f-887a-46dd-87bd-66fcce0f821f"]

Further Information

No response

[bwomsm1]

@teo-nikolov, @n1xan any chance you can help us with this issue?
Its scenario is quite simple,
The app is launched,
We are trying to switch to the launched app window, but when we are calling to driver.page_source the appium server gets stuck and it is not responding.

[bwomsm1]

Guys, can I have some feedback about this issue?

[teo-nikolov]

Hello, sorry for the delayed response.

Can you give me more info about the type of app that you're trying to automate? Is it WinForms, WPF, UWP, Electron, any other type of hybrid app?

NovaWindows driver has issues with some technologies and sometimes traversing the whole automation tree can take a long time. I'll be happy to try to help when I have more info about the issue.

[bwomsm1]

@teo-nikolov if to be honest, I am not sure about the type of app,
Do you have an idea how I can check it with some command line?

[bwomsm1]

@teo-nikolov
Sharing here the appium server log, appium did manage to launch the app correctly:

[Appium] Welcome to Appium v3.2.2
[Appium] The autodetected Appium home path: C:\Users\bxw0531\.appium
[Appium] Attempting to load driver novawindows...
[Appium] Requiring driver at C:\Users\bxw0531\.appium\node_modules\appium-novawindows-driver\build\lib\driver.js
[Appium] NovaWindowsDriver has been successfully loaded in 0.587s
[Appium] Appium REST http interface listener started on http://0.0.0.0:4723
[Appium] You can provide the following URLs in your client code to connect to this server:
        http://10.212.138.78:4723/
        http://192.168.31.160:4723/
        http://127.0.0.1:4723/ (only accessible from the same host)
[Appium] Available drivers:
[Appium]   - novawindows@1.3.1 (automationName 'NovaWindows')
[Appium] No plugins have been installed. Use the "appium plugin" command to install the one(s) you want to use.
[HTTP] Request idempotency key: dc3f7d2b-4457-45c1-a385-f15a90310efa
[HTTP] --> POST /session {"capabilities":{"firstMatch":[{}],"alwaysMatch":{"appium:automationName":"NovaWindows","platformName":"Windows","appium:win_app_driver_host":"http://127.0.0.1:4723","appium:app":"C:\\\\Program Files (x86)\\\\Arial\\\\Arial.exe"}}}
[AppiumDriver@5d92] Calling AppiumDriver.createSession() with args: [{"firstMatch":[{}],"alwaysMatch":{"appium:automationName":"NovaWindows","platformName":"Windows","appium:win_app_driver_host":"http://127.0.0.1:4723","appium:app":"C:\\\\Program Files (x86)\\\\Arial\\\\Arial.exe"}},{"firstMatch":[{}],"alwaysMatch":{"appium:automationName":"NovaWindows","platformName":"Windows","appium:win_app_driver_host":"http://127.0.0.1:4723","appium:app":"C:\\\\Program Files (x86)\\\\Arial\\\\Arial.exe"}},{"firstMatch":[{}],"alwaysMatch":{"appium:automationName":"NovaWindows","platformName":"Windows","appium:win_app_driver_host":"http://127.0.0.1:4723","appium:app":"C:\\\\Program Files (x86)\\\\Arial\\\\Arial.exe"}}]
[AppiumDriver@5d92] Event 'newSessionRequested' logged at 1774184674151 (15:04:34 GMT+0200 (Israel Standard Time))
[Appium] Attempting to find matching driver for automationName 'NovaWindows' and platformName 'Windows'
[Appium] The 'novawindows' driver was installed and matched caps.
[Appium] Will require it at C:\Users\bxw0531\.appium\node_modules\appium-novawindows-driver
[Appium] Requiring driver at C:\Users\bxw0531\.appium\node_modules\appium-novawindows-driver\build\lib\driver.js
[AppiumDriver@5d92] Appium v3.2.2 creating new NovaWindowsDriver (v1.3.1) session
[AppiumDriver@5d92] Checking BaseDriver versions for Appium and NovaWindowsDriver
[AppiumDriver@5d92] Appium's BaseDriver version is 10.2.2
[AppiumDriver@5d92] NovaWindowsDriver's BaseDriver version is 10.2.1
[NovaWindowsDriver@c3fa] Creating NovaWindows driver session...
[NovaWindowsDriver@c3fa]
[NovaWindowsDriver@c3fa] Creating session with W3C capabilities: {
  "alwaysMatch": {
    "platformName": "Windows",
    "appium:automationName": "NovaWindows",
    "appium:win_app_driver_host": "http://127.0.0.1:4723",
    "appium:app": "C:\\\\Program Files (x86)\\\\Arial\\\\Arial.exe"
  },
  "firstMatch": [
    {}
  ]
}
[NovaWindowsDriver@c3fa] The following provided capabilities were not recognized by this driver:
[NovaWindowsDriver@c3fa]   win_app_driver_host
[dbbcbb76][NovaWindowsDriver@c3fa] Session created with session id: dbbcbb76-2f55-4019-a0de-fc76b2628050
[dbbcbb76][NovaWindowsDriver@c3fa] Application path specified in capabilities: C:\\Program Files (x86)\\Arial\\Arial.exe
[dbbcbb76][NovaWindowsDriver@c3fa] Detected the following environment variables in app path:
[dbbcbb76][NovaWindowsDriver@c3fa] Detected app path to be in the classic format.
[dbbcbb76][NovaWindowsDriver@c3fa] Process IDs of 'arial' processes: 25268
[dbbcbb76][NovaWindowsDriver@c3fa] Waiting for the process window to appear... (1/20)
[dbbcbb76][NovaWindowsDriver@c3fa] Started session dbbcbb76-2f55-4019-a0de-fc76b2628050.
[dbbcbb76][AppiumDriver@5d92] New NovaWindowsDriver session created successfully, session dbbcbb76-2f55-4019-a0de-fc76b2628050 added to master session list
[dbbcbb76][AppiumDriver@5d92] Event 'newSessionStarted' logged at 1774184686025 (15:04:46 GMT+0200 (Israel Standard Time))
[dbbcbb76][NovaWindowsDriver@c3fa] Cached the protocol value 'W3C' for the new session dbbcbb76-2f55-4019-a0de-fc76b2628050
[dbbcbb76][NovaWindowsDriver@c3fa] Responding to client with driver.createSession() result: {"capabilities":{"platformName":"Windows","automationName":"NovaWindows","win_app_driver_host":"http://127.0.0.1:4723","app":"C:\\\\Program Files (x86)\\\\Arial\\\\Arial.exe","shouldCloseApp":true}}
[dbbcbb76][HTTP] <-- POST /session 200 11882 ms - 259
[dbbcbb76][HTTP] --> POST /session/dbbcbb76-2f55-4019-a0de-fc76b2628050/window {"handle":"14092414"}
[dbbcbb76][NovaWindowsDriver@c3fa] Calling AppiumDriver.setWindow() with args: ["14092414","dbbcbb76-2f55-4019-a0de-fc76b2628050"]
[dbbcbb76][NovaWindowsDriver@c3fa] Responding to client with driver.setWindow() result: null
[dbbcbb76][HTTP] <-- POST /session/dbbcbb76-2f55-4019-a0de-fc76b2628050/window 200 59 ms - 14
[dbbcbb76][HTTP] --> GET /session/dbbcbb76-2f55-4019-a0de-fc76b2628050/source
[dbbcbb76][NovaWindowsDriver@c3fa] Calling AppiumDriver.getPageSource() with args: ["dbbcbb76-2f55-4019-a0de-fc76b2628050"]

[bwomsm1]

@teo-nikolov I can say that the windows app was developed with C-Sharp