appium/appium-inspector

Xpath's are not getting recognised on webview2 app via Appium Inspector

lalithkumar97 opened this issue · 3 comments

lalithkumar97 commented

Do I have the most recent component updates?

  • I use the most recent available driver/plugin and server versions

Is the component officially supported by the Appium team?

  • I have verified the component repository is present under the Appium organization in GitHub

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

Not able to recognise the Absolute or Relative xpath via Appium Inspector for webview2 application.

Please see the attached screen shots.

Screenshot 1: Trying to search for an element using Relative xapth
813935BC-7819-4F9B-9D53-605276FE090B

Screnshot 2: Trying to search for an element using absolute xpath
BB5BAA11-120F-4EE2-988E-225CF2065350

ScreenShot 3: Not able to Identity the element after clicking on search for Absolute and Relative xpath
CAF7E7EB-3CE6-4A17-ACFD-5641FCC12248

Screenshot 4: Referring to the XML Source highlighting the element which I'm trying to locate via Xpath
7508FD4B-A8E7-4C21-8145-D7921E6D67F9

Expected Behavior

Appium inspector to identify the xpath and interact with the elements.

Minimal Reproducible Example

Desired Capabilities used in the Inspector.
{
"deviceName": "WindowsPC",
"platformName": "Windows",
"platformVersion": "11",
"app": "{{appId}}"
}

No need of code snippet since the absolute xpath is not been identified by the Appium inspector

Environment

  • Operating system: Windows
  • Appium server version (output of appium --version): 1.22.0
  • Appium Inspector: 2023.8.4
  • Platform and version under test: Windows 11

Link to Appium Logs

No response

Further Information

No response

jlipps commented

Please attach your complete appium log which demonstrates the issue

lalithkumar97 commented

[WinAppDriver] Windows Application Driver listening for requests at: http://127.0.0.1:4724/wd/hub
[WinAppDriver] Press ENTER to exit.
[WinAppDriver] ==========================================
[WinAppDriver] GET /wd/hub/status HTTP/1.1
[WinAppDriver] Accept: application/json, /
[WinAppDriver] Connection: keep-alive
[WinAppDriver] Content-Type: application/json; charset=utf-8
[WinAppDriver] Host: 127.0.0.1:4724
[WinAppDriver] User-Agent: appium
[WinAppDriver] HTTP/1.1 200 OK
[WinAppDriver] Content-Length: 147
[WinAppDriver] Content-Type: application/json
[WinAppDriver]
[WinAppDriver] {"build":{"revision":"18001","time":"Tue Sep 18 18:35:38 2018","version":"1.1.1809"},"os":{"arch":"amd64","name":"windows","version":"10.0.22000"}}
[WD Proxy] Got response with status 200: {"build":{"revision":"18001","time":"Tue Sep 18 18:35:38 2018","version":"1.1.1809"},"os":{"arch":"amd64","name":"windows","version":"10.0.22000"}}
[WinAppDriver] Starting WinAppDriver session. Will timeout in '20000' ms.
[WD Proxy] Matched '/session' to command name 'createSession'
[WD Proxy] Proxying [POST /session] to [POST http://127.0.0.1:4724/wd/hub/session] with body: {"desiredCapabilities":{"platformName":"windows","platformVersion":"11","app":"com.manh.storeuiv2_tkjnczvns4zyj!com.manh.storeuiv2","automationName":"windows","newCommandTimeout":3600,"connectHardwareKeyboard":true}}
[WinAppDriver] ==========================================
[WinAppDriver] POST /wd/hub/session HTTP/1.1
[WinAppDriver] Accept: application/json, /
[WinAppDriver] Connection: keep-alive
[WinAppDriver] Content-Length: 216
[WinAppDriver] Content-Type: application/json; charset=utf-8
[WinAppDriver] Host: 127.0.0.1:4724
[WinAppDriver] User-Agent: appium
[WinAppDriver] HTTP/1.1 200 OK
[WinAppDriver] Content-Length: 181
[WinAppDriver] Content-Type: application/json
[WinAppDriver]
[WinAppDriver] {"sessionId":"76AE1E23-5E4B-4432-A086-2BF544A1B901","status":0,"value":{"app":"com.manh.storeuiv2_tkjnczvns4zyj!com.manh.storeuiv2","platformName":"windows","platformVersion":"11"}}
[WD Proxy] Got response with status 200: {"sessionId":"76AE1E23-5E4B-4432-A086-2BF544A1B901","status":0,"value":{"app":"com.manh.storeuiv2_tkjnczvns4zyj!com.manh.storeuiv2","platformName":"windows","platformVersion":"11"}}
[WD Proxy] Determined the downstream protocol as 'MJSONWP'
[Appium] New WindowsDriver session created successfully, session ba674a0f-5f24-422b-8015-25afa1557c96 added to master session list
[BaseDriver] Event 'newSessionStarted' logged at 1694153979500 (23:19:39 GMT-0700 (Pacific Daylight Time))
[W3C (ba674a0f)] Cached the protocol value 'W3C' for the new session ba674a0f-5f24-422b-8015-25afa1557c96
[W3C (ba674a0f)] Responding to client with driver.createSession() result: {"capabilities":{"platformName":"windows","platformVersion":"11","app":"com.manh.storeuiv2_tkjnczvns4zyj!com.manh.storeuiv2","automationName":"windows","newCommandTimeout":3600,"connectHardwareKeyboard":true}}
[HTTP] <-- POST /wd/hub/session 200 3541 ms - 270
[HTTP]
[HTTP] --> GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/screenshot
[HTTP] {}
[W3C (ba674a0f)] Driver proxy active, passing request on via HTTP proxy
[WD Proxy] Matched '/wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/screenshot' to command name 'getScreenshot'
[WD Proxy] Proxying [GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/screenshot] to [GET http://127.0.0.1:4724/wd/hub/session/76AE1E23-5E4B-4432-A086-2BF544A1B901/screenshot] with no body
[WinAppDriver] ==========================================
[WinAppDriver] GET /wd/hub/session/76AE1E23-5E4B-4432-A086-2BF544A1B901/screenshot HTTP/1.1
[WinAppDriver] Accept: application/json, /
[WinAppDriver] Connection: keep-alive
[WinAppDriver] Content-Type: application/json; charset=utf-8
[WinAppDriver] Host: 127.0.0.1:4724
[WinAppDriver] User-Agent: appium
[WinAppDriver] HTTP/1.1 200 OK
[WinAppDriver] Content-Length: 8258
[WinAppDriver] Content-Type: application/json
[WinAppDriver]
[WinAppDriver] {"sessionId":"76AE1E23-5E4B-4432-A086-2BF544A1B901","status":0,"value":"iVBORw0KGgoAAAANSUhEUgAABsIAAAQQCAIAAADXj9kSAAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8YQUAABeiSURBVHhe7d0xSFtbGAfw1zdJ4VYIFBGLmzgExMGgIIIuzg4uToK4CA6Opt0j3UuzFMFBXbOI6FoUSzclgzoJKd2CIYtjDzn3BfH19SZWAq/+fnDh+845Otxsf8655y8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACAZ+pFeJrNZmwAAAAAAB5IkuTvtAQAAAAA+A9iRAAAAAAggxgRAAAAAMggRgQAAAAAMogRAQAAAIAMYkQAAAAAIIMYEQAAAADIIEY [...]
[WD Proxy] Got response with status 200: {"sessionId":"76AE1E23-5E4B-4432-A086-2BF544A1B901","status":0,"value":"iVBORw0KGgoAAAANSUhEUgAABsIAAAQQCAIAAADXj9kSAAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8YQUAABeiSURBVHhe7d0xSFtbGAfw1zdJ4VYIFBGLmzgExMGgIIIuzg4uToK4CA6Opt0j3UuzFMFBXbOI6FoUSzclgzoJKd2CIYtjDzn3BfH19SZWAq/+fnDh+845Otxsf8655y8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACAZ+pFeJrNZmwAAAAAAB5IkuTvtAQAAAAA+A9iRAAAAAAggxgRAAAAAMggRgQAAAAAMogRAQAAAIAMYkQAAAAAIIMYEQAAAADIIEYEAAAAADKIEQEAAACADGJEAAAAACBDFzHi0dFR0jIyMlKv19NRAAAAAKBla2srBmjRmzdvNjc307lemZ6ePj8/T5t7wmCYSpvudRojVqvVd+/e3dzcNJvNSqUS2nq9PjExEYp0BQAAAAA8b8VisXnP6enp7e1tqVRKp3uiXC4vLS09SBJDGwbDVNp3r9MYsVarDQwMvHz5MtT5fH5mZiaOAwAAAAAP9iFGu7u779+///jxY7qoJ8bGxvb39+8niTFDDINhKo48QqcxYqFQuLq6+vTpU2zr9frk5OTl5eXU1NTa2loYqVarQ0ND8QUdHR3FNRMTE6urq/EQdHuBM9EAAAAA/GFKpVKtVkt3IbaENgz29/c3Go10Ua/cTxKfJEMMOo0Rc7ncxcXF4eFhTAlD++XLl9HR0bOzs3K5XK/XFxYWtre3wwsKIxsbG/Gwc3hH4+Pj19fXoV5eXj4+Pg4LPnz4sLe31/qvAAAAAPB4+Xy+tavtJ8JUuqhX+vv706rlQdtj7STxSTLEoIsrVvr6+g4ODs7OzlZWVuJ+w7bv37+H91IoFEIdfqHZ2dlarRbqMDg3N...
[WD Proxy] Replacing sessionId 76AE1E23-5E4B-4432-A086-2BF544A1B901 with ba674a0f-5f24-422b-8015-25afa1557c96
[HTTP] <-- GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/screenshot 200 141 ms - 8247
[HTTP]
[HTTP] --> GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/window/rect
[HTTP] {}
[W3C (ba674a0f)] Driver proxy active, passing request on via HTTP proxy
[WD Proxy] Matched '/wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/window/rect' to command name 'getWindowRect'
[WD Proxy] Proxying [GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/window/rect] to [GET http://127.0.0.1:4724/wd/hub/session/76AE1E23-5E4B-4432-A086-2BF544A1B901/window/rect] with no body
[WinAppDriver] ==========================================
[WinAppDriver] GET /wd/hub/session/76AE1E23-5E4B-4432-A086-2BF544A1B901/window/rect HTTP/1.1
[WinAppDriver] Accept: application/json, /
[WinAppDriver] Connection: keep-alive
[WinAppDriver] Content-Type: application/json; charset=utf-8
[WinAppDriver] Host: 127.0.0.1:4724
[WinAppDriver] User-Agent: appium
[WinAppDriver] ### WinAppDriver::CommandHandler::Window::HandleCommandAsMidPoint - Command is not recognized
[WinAppDriver] HTTP/1.1 404 Not Found
[WinAppDriver] Content-Length: 147
[WinAppDriver] Content-Type: application/json
[WinAppDriver]
[WinAppDriver] {"status":9,"value":{"error":"unknown command","message":"Command not recognized: GET: /session/76AE1E23-5E4B-4432-A086-2BF544A1B901/window/rect"}}
[WD Proxy] Got response with status 404: {"status":9,"value":{"error":"unknown command","message":"Command not recognized: GET: /session/76AE1E23-5E4B-4432-A086-2BF544A1B901/window/rect"}}
[W3C] Matched W3C error code 'unknown command' to UnknownCommandError
[HTTP] <-- GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/window/rect 404 91 ms - 751
[HTTP]
[HTTP] --> GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/source
[HTTP] {}
[W3C (ba674a0f)] Driver proxy active, passing request on via HTTP proxy
[WD Proxy] Matched '/wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/source' to command name 'getPageSource'
[WD Proxy] Proxying [GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/source] to [GET http://127.0.0.1:4724/wd/hub/session/76AE1E23-5E4B-4432-A086-2BF544A1B901/source] with no body
[WinAppDriver] ==========================================
[WinAppDriver] GET /wd/hub/session/76AE1E23-5E4B-4432-A086-2BF544A1B901/source HTTP/1.1
[WinAppDriver] Accept: application/json, /
[WinAppDriver] Connection: keep-alive
[WinAppDriver] Content-Type: application/json; charset=utf-8
[WinAppDriver] Host: 127.0.0.1:4724
[WinAppDriver] User-Agent: appium
[WinAppDriver] HTTP/1.1 200 OK
[WinAppDriver] Content-Length: 25604
[WinAppDriver] Content-Type: application/json
[WinAppDriver]
[WinAppDriver] {"sessionId":"76AE1E23-5E4B-4432-A086-2BF544A1B901","status":0,"value":"
[WD Proxy] Got response with status 200: {"sessionId":"76AE1E23-5E4B-4432-A086-2BF544A1B901","status":0,"value":"
[WD Proxy] Replacing sessionId 76AE1E23-5E4B-4432-A086-2BF544A1B901 with ba674a0f-5f24-422b-8015-25afa1557c96
[HTTP] <-- GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/source 200 1366 ms - 25593
[HTTP]
[HTTP] --> GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/timeouts
[HTTP] {}
[W3C (ba674a0f)] Driver proxy active, passing request on via HTTP proxy
[WD Proxy] Matched '/wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/timeouts' to command name 'getTimeouts'
[WD Proxy] Proxying [GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/timeouts] to [GET http://127.0.0.1:4724/wd/hub/session/76AE1E23-5E4B-4432-A086-2BF544A1B901/timeouts] with no body
[WinAppDriver] ==========================================
[WinAppDriver] GET /wd/hub/session/76AE1E23-5E4B-4432-A086-2BF544A1B901/timeouts HTTP/1.1
[WinAppDriver] Accept: application/json, /
[WinAppDriver] Connection: keep-alive
[WinAppDriver] Content-Type: application/json; charset=utf-8
[WinAppDriver] Host: 127.0.0.1:4724
[WinAppDriver] User-Agent: appium
[WD Proxy] Got response with status 405: {"status":103,"value":{"error":"unknown method","message":"The requested command matched a known URL but did not match an method for that URL."}}
[WinAppDriver] HTTP/1.1 405 Method Not Allowed
[WinAppDriver] Content-Length: 145
[WinAppDriver] Content-Type: application/json
[WinAppDriver]
[WinAppDriver] {"status":103,"value":{"error":"unknown method","message":"The requested command matched a known URL but did not match an method for that URL."}}
[W3C] Matched W3C error code 'unknown method' to UnknownMethodError
[HTTP] <-- GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/timeouts 405 6 ms - 855
[HTTP]
[HTTP] --> POST /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/element
[HTTP] {"using":"xpath","value":"/Window/Pane"}
[W3C (ba674a0f)] Calling AppiumDriver.findElement() with args: ["xpath","/Window/Pane","ba674a0f-5f24-422b-8015-25afa1557c96"]
[BaseDriver] Valid locator strategies for this request: xpath, id, name, class name, accessibility id
[WD Proxy] Matched '/element' to command name 'findElement'
[WD Proxy] Proxying [POST /element] to [POST http://127.0.0.1:4724/wd/hub/session/76AE1E23-5E4B-4432-A086-2BF544A1B901/element] with body: {"using":"xpath","value":"/Window/Pane"}
[WinAppDriver] ==========================================
[WinAppDriver] POST /wd/hub/session/76AE1E23-5E4B-4432-A086-2BF544A1B901/element HTTP/1.1
[WinAppDriver] Accept: application/json, /
[WinAppDriver] Connection: keep-alive
[WinAppDriver] Content-Length: 40
[WinAppDriver] Content-Type: application/json; charset=utf-8
[WinAppDriver] Host: 127.0.0.1:4724
[WinAppDriver] User-Agent: appium
[WinAppDriver] HTTP/1.1 404 Not Found
[WinAppDriver] Content-Length: 139
[WinAppDriver] Content-Type: application/json
[WinAppDriver]
[WinAppDriver] {"status":7,"value":{"error":"no such element","message":"An element could not be located on the page using the given search parameters."}}
[WD Proxy] Got response with status 404: {"status":7,"value":{"error":"no such element","message":"An element could not be located on the page using the given search parameters."}}
[W3C] Matched W3C error code 'no such element' to NoSuchElementError
[W3C (ba674a0f)] Encountered internal error running command: NoSuchElementError: An element could not be located on the page using the given search parameters.
[W3C (ba674a0f)] at errorFromW3CJsonCode (C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\protocol\errors.js:780:25)
[W3C (ba674a0f)] at ProxyRequestError.getActualError (C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\protocol\errors.js:663:14)
[W3C (ba674a0f)] at WADProxy.command (C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:272:19)
[W3C (ba674a0f)] at processTicksAndRejections (internal/process/task_queues.js:85:5)
[HTTP] <-- POST /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/element 404 1657 ms - 812
[HTTP]
[HTTP] --> GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/timeouts
[HTTP] {}
[W3C (ba674a0f)] Driver proxy active, passing request on via HTTP proxy
[WD Proxy] Matched '/wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/timeouts' to command name 'getTimeouts'
[WD Proxy] Proxying [GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/timeouts] to [GET http://127.0.0.1:4724/wd/hub/session/76AE1E23-5E4B-4432-A086-2BF544A1B901/timeouts] with no body
[WinAppDriver] ==========================================
[WinAppDriver] GET /wd/hub/session/76AE1E23-5E4B-4432-A086-2BF544A1B901/timeouts HTTP/1.1
[WinAppDriver] Accept: application/json, /
[WinAppDriver] Connection: keep-alive
[WinAppDriver] Content-Type: application/json; charset=utf-8
[WinAppDriver] Host: 127.0.0.1:4724
[WinAppDriver] User-Agent: appium
[WD Proxy] Got response with status 405: {"status":103,"value":{"error":"unknown method","message":"The requested command matched a known URL but did not match an method for that URL."}}
[W3C] Matched W3C error code 'unknown method' to UnknownMethodError
[HTTP] <-- GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/timeouts 405 7 ms - 743
[HTTP]
[WinAppDriver] HTTP/1.1 405 Method Not Allowed
[WinAppDriver] Content-Length: 145
[WinAppDriver] Content-Type: application/json
[HTTP] --> GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/timeouts
[HTTP] {}
[W3C (ba674a0f)] Driver proxy active, passing request on via HTTP proxy
[WD Proxy] Matched '/wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/timeouts' to command name 'getTimeouts'
[WD Proxy] Proxying [GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/timeouts] to [GET http://127.0.0.1:4724/wd/hub/session/76AE1E23-5E4B-4432-A086-2BF544A1B901/timeouts] with no body
[WinAppDriver] ==========================================
[WinAppDriver] GET /wd/hub/session/76AE1E23-5E4B-4432-A086-2BF544A1B901/timeouts HTTP/1.1
[WinAppDriver] Accept: application/json, /
[WinAppDriver] Connection: keep-alive
[WinAppDriver] Content-Type: application/json; charset=utf-8
[WinAppDriver] Host: 127.0.0.1:4724
[WinAppDriver] User-Agent: appium
[WinAppDriver] HTTP/1.1 405 Method Not Allowed
[WinAppDriver] Content-Length: 145
[WinAppDriver] Content-Type: application/json
[WD Proxy] Got response with status 405: {"status":103,"value":{"error":"unknown method","message":"The requested command matched a known URL but did not match an method for that URL."}}
[W3C] Matched W3C error code 'unknown method' to UnknownMethodError
[HTTP] <-- GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/timeouts 405 8 ms - 743
[HTTP]
[HTTP] --> GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/timeouts
[HTTP] {}
[W3C (ba674a0f)] Driver proxy active, passing request on via HTTP proxy
[WD Proxy] Matched '/wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/timeouts' to command name 'getTimeouts'
[WD Proxy] Proxying [GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/timeouts] to [GET http://127.0.0.1:4724/wd/hub/session/76AE1E23-5E4B-4432-A086-2BF544A1B901/timeouts] with no body
[WinAppDriver] ==========================================
[WinAppDriver] GET /wd/hub/session/76AE1E23-5E4B-4432-A086-2BF544A1B901/timeouts HTTP/1.1
[WinAppDriver] Accept: application/json, /
[WinAppDriver] Connection: keep-alive
[WinAppDriver] Content-Type: application/json; charset=utf-8
[WinAppDriver] Host: 127.0.0.1:4724
[WinAppDriver] User-Agent: appium
[WD Proxy] Got response with status 405: {"status":103,"value":{"error":"unknown method","message":"The requested command matched a known URL but did not match an method for that URL."}}
[WinAppDriver] HTTP/1.1 405 Method Not Allowed
[WinAppDriver] Content-Length: 145
[WinAppDriver] Content-Type: application/json
[WinAppDriver]
[WinAppDriver] {"status":103,"value":{"error":"unknown method","message":"The requested command matched a known URL but did not match an method for that URL."}}
[W3C] Matched W3C error code 'unknown method' to UnknownMethodError
[HTTP] <-- GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/timeouts 405 8 ms - 855
[HTTP]
[HTTP] --> GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/screenshot
[HTTP] {}
[W3C (ba674a0f)] Driver proxy active, passing request on via HTTP proxy
[WD Proxy] Matched '/wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/screenshot' to command name 'getScreenshot'
[WD Proxy] Proxying [GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/screenshot] to [GET http://127.0.0.1:4724/wd/hub/session/76AE1E23-5E4B-4432-A086-2BF544A1B901/screenshot] with no body
[WinAppDriver] ==========================================
[WinAppDriver] GET /wd/hub/session/76AE1E23-5E4B-4432-A086-2BF544A1B901/screenshot HTTP/1.1
[WinAppDriver] Accept: application/json, /
[WinAppDriver] Connection: keep-alive
[WinAppDriver] Content-Type: application/json; charset=utf-8
[WinAppDriver] Host: 127.0.0.1:4724
[WinAppDriver] User-Agent: appium
[WinAppDriver] HTTP/1.1 200 OK
[WinAppDriver] Content-Length: 58530
[WinAppDriver] Content-Type: application/json
[WinAppDriver]
[WinAppDriver] {"sessionId":"76AE1E23-5E4B-4432-A086-2BF544A1B901","status":0,"value":"iVBORw0KGgoAAAANSUhEUgAABsIAAAQQCAIAAADXj9kSAAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8YQUAAKrqSURBVHhe7N0JnBx1mT/+ntzn5A65gHBMwiEkQEI4ghrFXVhADsEgoquiIC4CArqL65pFXQ/+AQmyIKysF0cCckTlR1zBKAlIOMNNMhwBcpFkJsnkPudf1dXT03N+Z3rCZHryfps8+fTT36ruGfJqK89UdacAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA9lBF0e9169YlNwAAAAAAaundu3eHTAQAAAAAaIAxIgAAAAAQYIwIAAAAAAQYIwIAAAAAAc [...]
[WD Proxy] Got response with status 200: {"sessionId":"76AE1E23-5E4B-4432-A086-2BF544A1B901","status":0,"value":"iVBORw0KGgoAAAANSUhEUgAABsIAAAQQCAIAAADXj9kSAAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8YQUAAKrqSURBVHhe7N0JnBx1mT/+ntzn5A65gHBMwiEkQEI4ghrFXVhADsEgoquiIC4CArqL65pFXQ/+AQmyIKysF0cCckTlR1zBKAlIOMNNMhwBcpFkJsnkPudf1dXT03N+Z3rCZHryfps8+fTT36ruGfJqK89UdacAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA9lBF0e9169YlNwAAAAAAaundu3eHTAQAAAAAaIAxIgAAAAAQYIwIAAAAAAQYIwIAAAAAAcaIAAAAAECAMSIAAAAAEGCMCAAAAAAEGCMCAAAAAAHGiAAAAABAgDEiAAAAABDQjDHin/70p95pJSUl5eXlmS4AAAAAkPajH/0oGaAlRowY8W//9m+Z+1rL8ccf/+KLL2Zu5Iia0V2ZG83X1DHiK6+88u///u/vvPPOunXrHnzwwehmeXn5uHHjopBZAQAAAAB7tquvvnpdjieeeGLNmjU//OEPM3e3iltuueUzn/lMrUlidDNqRndlbjdfU8eIixcv3muvvXr06BHlQw899IQTTkj6AAAAAECt8xATd955509+8pObb745s6hVHH744XfffXfuJDGZIUbN6K6kk4emjhHHjx+/cOHCX/ziF8nN8vLyCRMmLFiw4Jhjjrn44oujziuvvDJ8+PDkG/SnP/0pWTNu3Lgvf/nLyUXQ2QWuiQYAAACgnfnhD3+4ePHizFmIadHNqNmnT5+1a9dmFrWW3EniLpkhRpo6Ruzfv/9LL7308MMPJ1PC6Oa8efNGjx795JNP3nLLLeXl5Wecccb//u//Rt+gqHP55ZcnFztH36OxY8eWlpZG+Z//+Z//7//+L1pw0...
[WD Proxy] Replacing sessionId 76AE1E23-5E4B-4432-A086-2BF544A1B901 with ba674a0f-5f24-422b-8015-25afa1557c96
[HTTP] <-- GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/screenshot 200 199 ms - 58519
[HTTP]
[HTTP] --> GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/window/rect
[HTTP] {}
[W3C (ba674a0f)] Driver proxy active, passing request on via HTTP proxy
[WD Proxy] Matched '/wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/window/rect' to command name 'getWindowRect'
[WD Proxy] Proxying [GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/window/rect] to [GET http://127.0.0.1:4724/wd/hub/session/76AE1E23-5E4B-4432-A086-2BF544A1B901/window/rect] with no body
[WinAppDriver] ==========================================
[WinAppDriver] GET /wd/hub/session/76AE1E23-5E4B-4432-A086-2BF544A1B901/window/rect HTTP/1.1
[WinAppDriver] Accept: application/json, /
[WinAppDriver] Connection: keep-alive
[WinAppDriver] Content-Type: application/json; charset=utf-8
[WinAppDriver] Host: 127.0.0.1:4724
[WinAppDriver] User-Agent: appium
[WD Proxy] Got response with status 404: {"status":9,"value":{"error":"unknown command","message":"Command not recognized: GET: /session/76AE1E23-5E4B-4432-A086-2BF544A1B901/window/rect"}}
[WinAppDriver] ### WinAppDriver::CommandHandler::Window::HandleCommandAsMidPoint - Command is not recognized
[WinAppDriver] HTTP/1.1 404 Not Found
[WinAppDriver] Content-Length: 147
[WinAppDriver] Content-Type: application/json
[W3C] Matched W3C error code 'unknown command' to UnknownCommandError
[HTTP] <-- GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/window/rect 404 49 ms - 863
[HTTP]
[HTTP] --> GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/source
[HTTP] {}
[W3C (ba674a0f)] Driver proxy active, passing request on via HTTP proxy
[WD Proxy] Matched '/wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/source' to command name 'getPageSource'
[WD Proxy] Proxying [GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/source] to [GET http://127.0.0.1:4724/wd/hub/session/76AE1E23-5E4B-4432-A086-2BF544A1B901/source] with no body
[WinAppDriver] ==========================================
[WinAppDriver] GET /wd/hub/session/76AE1E23-5E4B-4432-A086-2BF544A1B901/source HTTP/1.1
[WinAppDriver] Accept: application/json, /
[WinAppDriver] Connection: keep-alive
[WinAppDriver] Content-Type: application/json; charset=utf-8
[WinAppDriver] Host: 127.0.0.1:4724
[WinAppDriver] User-Agent: appium
[WD Proxy] Got response with status 200: {"sessionId":"76AE1E23-5E4B-4432-A086-2BF544A1B901","status":0,"value":"
[WD Proxy] Replacing sessionId 76AE1E23-5E4B-4432-A086-2BF544A1B901 with ba674a0f-5f24-422b-8015-25afa1557c96
[HTTP] <-- GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/source 200 2421 ms - 100750
[HTTP]
[WinAppDriver] HTTP/1.1 200 OK
[WinAppDriver] Content-Length: 100761
[WinAppDriver] Content-Type: application/json
[WinAppDriver]
[WinAppDriver] {"sessionId":"76AE1E23-5E4B-4432-A086-2BF544A1B901","status":0,"value":"
[HTTP] --> GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/timeouts
[HTTP] {}
[W3C (ba674a0f)] Driver proxy active, passing request on via HTTP proxy
[WD Proxy] Matched '/wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/timeouts' to command name 'getTimeouts'
[WD Proxy] Proxying [GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/timeouts] to [GET http://127.0.0.1:4724/wd/hub/session/76AE1E23-5E4B-4432-A086-2BF544A1B901/timeouts] with no body
[WinAppDriver] ==========================================
[WinAppDriver] GET /wd/hub/session/76AE1E23-5E4B-4432-A086-2BF544A1B901/timeouts HTTP/1.1
[WinAppDriver] Accept: application/json, /
[WinAppDriver] Connection: keep-alive
[WinAppDriver] Content-Type: application/json; charset=utf-8
[WinAppDriver] Host: 127.0.0.1:4724
[WinAppDriver] User-Agent: appium
[WD Proxy] Got response with status 405: {"status":103,"value":{"error":"unknown method","message":"The requested command matched a known URL but did not match an method for that URL."}}
[WinAppDriver] HTTP/1.1 405 Method Not Allowed
[WinAppDriver] Content-Length: 145
[WinAppDriver] Content-Type: application/json
[WinAppDriver]
[WinAppDriver] {"status":103,"value":{"error":"unknown method","message":"The requested command matched a known URL but did not match an method for that URL."}}
[W3C] Matched W3C error code 'unknown method' to UnknownMethodError
[HTTP] <-- GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/timeouts 405 6 ms - 855
[HTTP]
[HTTP] --> GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/timeouts
[HTTP] {}
[W3C (ba674a0f)] Driver proxy active, passing request on via HTTP proxy
[WD Proxy] Matched '/wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/timeouts' to command name 'getTimeouts'
[WD Proxy] Proxying [GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/timeouts] to [GET http://127.0.0.1:4724/wd/hub/session/76AE1E23-5E4B-4432-A086-2BF544A1B901/timeouts] with no body
[WinAppDriver] ==========================================
[WinAppDriver] GET /wd/hub/session/76AE1E23-5E4B-4432-A086-2BF544A1B901/timeouts HTTP/1.1
[WinAppDriver] Accept: application/json, /
[WinAppDriver] Connection: keep-alive
[WinAppDriver] Content-Type: application/json; charset=utf-8
[WinAppDriver] Host: 127.0.0.1:4724
[WinAppDriver] User-Agent: appium
[WD Proxy] Got response with status 405: {"status":103,"value":{"error":"unknown method","message":"The requested command matched a known URL but did not match an method for that URL."}}
[WinAppDriver] HTTP/1.1 405 Method Not Allowed
[WinAppDriver] Content-Length: 145
[WinAppDriver] Content-Type: application/json
[WinAppDriver]
[WinAppDriver] {"status":103,"value":{"error":"unknown method","message":"The requested command matched a known URL but did not match an method for that URL."}}
[W3C] Matched W3C error code 'unknown method' to UnknownMethodError
[HTTP] <-- GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/timeouts 405 5 ms - 855
[HTTP]
[HTTP] --> POST /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/elements
[HTTP] {"using":"xpath","value":"//[@name=‘CHECK OUT’]"}
[W3C (ba674a0f)] Calling AppiumDriver.findElements() with args: ["xpath","//[@name=‘CHECK OUT’]","ba674a0f-5f24-422b-8015-25afa1557c96"]
[BaseDriver] Valid locator strategies for this request: xpath, id, name, class name, accessibility id
[WD Proxy] Matched '/elements' to command name 'findElements'
[WD Proxy] Proxying [POST /elements] to [POST http://127.0.0.1:4724/wd/hub/session/76AE1E23-5E4B-4432-A086-2BF544A1B901/elements] with body: {"using":"xpath","value":"//*[@name=‘CHECK OUT’]"}
[WinAppDriver] ==========================================
[WinAppDriver] POST /wd/hub/session/76AE1E23-5E4B-4432-A086-2BF544A1B901/elements HTTP/1.1
[WinAppDriver] Accept: application/json, /
[WinAppDriver] Connection: keep-alive
[WinAppDriver] Content-Length: 54
[WinAppDriver] Content-Type: application/json; charset=utf-8
[WinAppDriver] Host: 127.0.0.1:4724
[WinAppDriver] User-Agent: appium
[WinAppDriver] HTTP/1.1 200 OK
[WinAppDriver] Content-Length: 74
[WinAppDriver] Content-Type: application/json
[WinAppDriver]
[WinAppDriver] {"sessionId":"76AE1E23-5E4B-4432-A086-2BF544A1B901","status":0,"value":[]}
[WD Proxy] Got response with status 200: {"sessionId":"76AE1E23-5E4B-4432-A086-2BF544A1B901","status":0,"value":[]}
[W3C (ba674a0f)] Responding to client with driver.findElements() result: []
[HTTP] <-- POST /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/elements 200 1437 ms - 12
[HTTP]
[HTTP] --> GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/timeouts
[HTTP] {}
[W3C (ba674a0f)] Driver proxy active, passing request on via HTTP proxy
[WD Proxy] Matched '/wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/timeouts' to command name 'getTimeouts'
[WD Proxy] Proxying [GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/timeouts] to [GET http://127.0.0.1:4724/wd/hub/session/76AE1E23-5E4B-4432-A086-2BF544A1B901/timeouts] with no body
[WinAppDriver] ==========================================
[WinAppDriver] GET /wd/hub/session/76AE1E23-5E4B-4432-A086-2BF544A1B901/timeouts HTTP/1.1
[WinAppDriver] Accept: application/json, /
[WinAppDriver] Connection: keep-alive
[WinAppDriver] Content-Type: application/json; charset=utf-8
[WinAppDriver] Host: 127.0.0.1:4724
[WinAppDriver] User-Agent: appium
[WD Proxy] Got response with status 405: {"status":103,"value":{"error":"unknown method","message":"The requested command matched a known URL but did not match an method for that URL."}}
[WinAppDriver] HTTP/1.1 405 Method Not Allowed
[WinAppDriver] Content-Length: 145
[WinAppDriver] Content-Type: application/json
[WinAppDriver]
[WinAppDriver] {"status":103,"value":{"error":"unknown method","message":"The requested command matched a known URL but did not match an method for that URL."}}
[W3C] Matched W3C error code 'unknown method' to UnknownMethodError
[HTTP] <-- GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/timeouts 405 7 ms - 855
[HTTP]
[HTTP] --> GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/timeouts
[HTTP] {}
[W3C (ba674a0f)] Driver proxy active, passing request on via HTTP proxy
[WD Proxy] Matched '/wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/timeouts' to command name 'getTimeouts'
[WD Proxy] Proxying [GET /wd/hub/session/ba674a0f-5f24-422b-8015-25afa1557c96/timeouts] to [GET http://127.0.0.1:4724/wd/hub/session/76AE1E23-5E4B-4432-A086-2BF544A1B901/timeouts] with

jlipps commented

The log indicates that WinAppDriver could not find the requested element. There's nothing the inspector can do about that. The inspector looks at the source provided by the driver, and suggests locators based on that. If the driver can't actually find elements using the xpath locator provided, then that is a bug with the driver and should be reported to the driver repo (in this case the WinAppDriver repo, but good luck, because Microsoft doesn't maintain it anymore).