Hello!
I've got some rare floating issue when executing element.findElement(locator) using Java language binding, WinAppDriver v1.2.1.
It can throw org.openqa.selenium.UnsupportedCommandException, and then the corresponding driver logs are:
==========================================
POST /session/CC36BFBE-AC57-4F8A-9018-A7F0B4CDB913/element//element HTTP/1.1
Accept-Encoding: gzip
Connection: Keep-Alive
Content-Length: 76
Content-Type: application/json; charset=utf-8
Host: 127.0.0.1:4723
User-Agent: selenium/3.141.59 (java windows)
### WinAppDriver::CommandHandler::Element::HandleCommandAsMidPoint - Command is not recognized
HTTP/1.1 404 Not Found
Content-Length: 153
Content-Type: application/json
{"status":9,"value":{"error":"unknown command","message":"Command not recognized: POST: /session/CC36BFBE-AC57-4F8A-9018-A7F0B4CDB913/element//element"}}
==========================================
As you can see there is a missed {element id} in the URI "/session/{session id}/element/{element id}/element":
POST /session/CC36BFBE-AC57-4F8A-9018-A7F0B4CDB913/element//element HTTP/1.1
How it even possible that the client sends inappropriate request to the server other than there is an issue on WinAppDriver Java client side?
I would expect to see some not empty {element id} in the URI and StaleElementReferenceException or NoSuchElementException for example, but definitely not UnsupportedCommandException.
So my question is if it is a known defect in WinAppDriver and I just need to find some workaround for my particular place in the code?
Thanks in advance!
Hello!
I've got some rare floating issue when executing element.findElement(locator) using Java language binding, WinAppDriver v1.2.1.
It can throw
org.openqa.selenium.UnsupportedCommandException, and then the corresponding driver logs are:As you can see there is a missed {element id} in the URI "
/session/{session id}/element/{element id}/element":POST /session/CC36BFBE-AC57-4F8A-9018-A7F0B4CDB913/element//element HTTP/1.1How it even possible that the client sends inappropriate request to the server other than there is an issue on WinAppDriver Java client side?
I would expect to see some not empty {element id} in the URI and
StaleElementReferenceExceptionorNoSuchElementExceptionfor example, but definitely notUnsupportedCommandException.So my question is if it is a known defect in WinAppDriver and I just need to find some workaround for my particular place in the code?
Thanks in advance!