Appium Inspector with WinAppDriver Failed to create session
WeiweiCaiAcpt opened this issue · 3 comments
I'm newer on Appium with Windows Application Driver. But I cannot start session from Appium Inspector. Following is detailed information, am I missing anything here? Thanks in advanced.
Operating System:
Edition: Windows 10 Enterprise
Version: 21H2
OS Build: 19044.1766
Tools installed:
Appium Server GUI 1.22.3-4
Appium Inspector 2022.5.4
Windows Application Driver 1.2.99
Repro Steps
- Launch Appium Server GUI and set the settings as this screenshot shows:
- Start Server. Following logs shows in Appium Server GUI:
[HTTP] Waiting until the server is closed
[HTTP] Received server close event
[Appium] Welcome to Appium v1.22.3
[Appium] Non-default server args:
[Appium] allowCors: true
[Appium] address: 127.0.0.1
[Appium] relaxedSecurityEnabled: true
[Appium] allowInsecure: {
[Appium] }
[Appium] denyInsecure: {
[Appium] }
[Appium] You have enabled CORS requests from any host. Be careful not to visit sites which could maliciously try to start Appium sessions on your machine
[Appium] Appium REST http interface listener started on 127.0.0.1:4723
- Launch Appium Inspector and fille Remote Path and Desired Capabilities as below screenshot shows:
- Click Start Session button.
Excepted Result:
The Windows Store App session will be started successfully.
in remote path you are using wb/hub it should be wd/hub
@anunay1 Thanks for helping checking this.
After change the remote path to wd/hub, then start session, I get this error:
Attachment shows the logs in Appium Server GUI:
appium-server-logs.txt
At the beginning of the logs, it shows Appium Server is listening on 127.0.0.1:4723
[info] �[35m[Appium]�[39m Appium REST http interface listener started on 127.0.0.1:4723
But after starting session from Appium Inspector, the logs shows "WinAppDriver exists, but the checksum did not match. Was it replaced manually?" and "GET http://127.0.0.1:4724/wd/hub/status". It seems the session request is calling 127.0.0.1:4723 and seems something wrong when Appium Server communicate with WinAppDriver. Is it the problem? How can I configure Appium Server can communicate with WinAppDriver as normal?
[info] �[35m[Appium]�[39m Appium v1.22.3 creating new WindowsDriver (v1.19.1) session
[info] �[35m[Appium]�[39m Applying relaxed security to 'WindowsDriver' as per server command line argument. All insecure features will be enabled unless explicitly disabled by --deny-insecure
[debug] �[35m[BaseDriver]�[39m W3C capabilities and MJSONWP desired capabilities were provided
[debug] �[35m[BaseDriver]�[39m Creating session with W3C capabilities: {
[debug] �[35m[BaseDriver]�[39m "alwaysMatch": {
[debug] �[35m[BaseDriver]�[39m "platformName": "Windows",
[debug] �[35m[BaseDriver]�[39m "appium:app": "50582LuanNguyen.NuGetPackageExplorer_w6y2tyx5bpzwa!App",
[debug] �[35m[BaseDriver]�[39m "appium:deviceName": "WindowsPC",
[debug] �[35m[BaseDriver]�[39m "appium:newCommandTimeout": 3600,
[debug] �[35m[BaseDriver]�[39m "appium:connectHardwareKeyboard": true
[debug] �[35m[BaseDriver]�[39m },
[debug] �[35m[BaseDriver]�[39m "firstMatch": [
[debug] �[35m[BaseDriver]�[39m {}
[debug] �[35m[BaseDriver]�[39m ]
[debug] �[35m[BaseDriver]�[39m }
[warn] �[35m[BaseDriver]�[39m The following capabilities were provided, but are not recognized by Appium:
[warn] �[35m[BaseDriver]�[39m connectHardwareKeyboard
[info] �[35m[BaseDriver]�[39m Session created with session id: 030f22bc-d237-4d13-b12a-51475d940192[warn] �[35m[WinAppDriver]�[39m WinAppDriver exists, but the checksum did not match. Was it replaced manually?[info] �[35m[WinAppDriver]�[39m Spawning 'C:\Program Files\Windows Application Driver\WinAppDriver.exe' with args: ["4724/wd/hub"]
[debug] �[35m[WD Proxy]�[39m Matched '/status' to command name 'getStatus'
[debug] �[35m[WD Proxy]�[39m Proxying [GET /status] to [GET http://127.0.0.1:4724/wd/hub/status] with no body
[debug] �[35m[WinAppDriver]�[39m Windows Application Driver listening for requests at: http://127.0.0.1:4724/wd/hub
when I run it on vmware(appium2.0, winappdriver 1.2.99,win10) , there are no issuees;but when I run it locally, the same sa your issue.My God