WinAppDriver v1.2.99 Internal Error
See original GitHub issueUsing a simple get request to get the status returns a 500 internal error. I am using the x64 build on a x64 architecture. Below command does not throw an error on previous stable build v1.2.1.
Command:
wget http://127.0.0.1:4723/status
Response:
GET /status HTTP/1.1 Host: 127.0.0.1:4723 User-Agent: Mozilla/5.0 (Windows NT; Windows NT 10.0; en-US) WindowsPowerShell/5.1.19041.1023 HTTP/1.1 500 Internal Error Content-Length: 133 Content-Type: application/json {“status”:13,“value”:{“error”:“unknown error”,“message”:“An unknown error occurred in the remote end while processing the command.”}}
Issue Analytics
- State:
- Created 2 years ago
- Reactions:4
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Winappdriver is crashed during UITest execution
I am testing desktop application and running UI test on CI pipeline. This error occurs randomly: TearDown : OpenQA.Selenium.
Read more >WinAppDriver | Windows Application Driver - kandi
WinAppDriver is a C# library. WinAppDriver has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support....
Read more >WinApp Driver test automation blocking issues
Below are the blocking issues we are facing while using WinAppDriver (v1.2). Please note there are no build errors in the code and...
Read more >WinAppDriver and Desktop UI Test Automation
WinAppDriver is a test framework developed by Microsoft as an open source project, ... Download and Install the latest release (v1.1 now): ...
Read more >How To Automate Desktops Apps Using WinAppDriver
This blog deep dives by telling you How To Automate Desktops Apps Using WinAppDriver. It also leverages WinAppDriver on HyperExecute Cloud ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It looks like our build system didn’t stamp WinAppDriver with a version number (how curious!)
We’ll fix this in two ways:
/status
even if we cannot produce a version number, as/status
is required to work to begin a session with Appium.Is someone going to fix it? This problem is known for more than a year without any progress 🤷♂️