Action failed using following locators (unexpected command response)


For a login page, the Sign-in button being used for the application I’m logging into is set up as the following:

For the test, when the Sign-in button is selected, the Sign-in is successful but I’m getting the following failure for the test:

Click Login button Button
Action failed using following locators:

  1. XPATH=//div[5]//input
    WebDriverException: unknown error: unexpected command response
    (Session info: chrome=103.0.5060.114)
    Build info: version: ‘4.1.1’, revision: ‘e8fcc2cecf’
    System info: ‘Windows 10’, os.arch: ‘amd64’, os.version: ‘10.0’, java.version: ‘13.0.1’
    Driver info:
    Command: [2aa8a1f61d2d3e4ba35ab13ee08d9e96, clickElement {id=0ddf01b2-a2f0-402b-a876-6f3f3251f31e}]
    Capabilities {acceptInsecureCerts: false, browserName: chrome, browserVersion: 103.0.5060.114, chrome: {chromedriverVersion: 102.0.5005.61 (0e59bcc00cc4…, goog:chromeOptions: {debuggerAddress: localhost:51321}, javascriptEnabled: true, networkConnectionEnabled: false, pageLoadStrategy: normal, platform: WINDOWS, platformName: WINDOWS, proxy: Proxy(), se:cdp: ws://localhost:51321/devtoo…, se:cdpVersion: 103.0.5060.114, setWindowRect: true, strictFileInteractability: false, timeouts: {implicit: 0, pageLoad: 300000, script: 30000}, unhandledPromptBehavior: dismiss and notify, webauthn:extension:credBlob: true, webauthn:extension:largeBlob: true, webauthn:virtualAuthenticators: true}
    Element: [[ChromeDriver: chrome on WINDOWS (2aa8a1f61d2d3e4ba35ab13ee08d9e96)] → xpath: //div[5]//input]
    Session ID: 2aa8a1f61d2d3e4ba35ab13ee08d9e96

  2. XPATH=/html/body/section/form/div/div[1]/div[2]/div/div/fieldset/div[5]/div/input
    TimeoutException: Timeout occurred while trying to perform the action. Element was not found

Login button Button
Searched by XPATH://div[5]//input

Could this be an issue with the version of ChromeDriver being used?

Have temporarily sorted this by downgrading to Chrome version 102.0.5005.63.
Have had to stop Automatic updates for Chrome too.

Chromedriver supplied with the Agent kept the same (91.0.4472.101)

Started facing the same issue after updating to the latest Chromedriver. (103.0.5060.5300). Hoping that the next release would fix the issue.
Downgrading Chrome would solve the issue for now.

1 Like