-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Appium Inspector with WinAppDriver Failed to create session #1739
Comments
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: At the beginning of the logs, it shows Appium Server is listening 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?
|
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 |
Spawning 'C:\Program Files\Windows Application Driver\WinAppDriver.exe' with args: ["4724/wd/hub"] but failed |
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
Excepted Result:
The Windows Store App session will be started successfully.
Actual Result:
This error shows in Appium Inspector:
The text was updated successfully, but these errors were encountered: