Skip to content
This repository has been archived by the owner on Jun 28, 2023. It is now read-only.

element/click did not match a known command #174

Open
gouyang opened this issue Nov 1, 2018 · 1 comment
Open

element/click did not match a known command #174

gouyang opened this issue Nov 1, 2018 · 1 comment

Comments

@gouyang
Copy link

gouyang commented Nov 1, 2018

I have a test like below failed with the error element/click did not match a known command. It's using the geckodriver-0.23.0.
It seems the endpoint is not correct, it's supposing to be something like /session/9016e42e-3373-43f3-b9e0-9d667b51b953/element/{element id}/click, the {element id} is not there.

Expect(page.FindByXPath("//*[@id='content']/div[1]/div/div[1]/div/div/span[1]").Click()).To(Succeed())

Error part:

 Expected success, but got an error:
      <*errors.errorString | 0xc000339f70>: {
          s: "failed to click on selection 'XPath: //*[@id='content']/div[1]/div/div[1]/div/div/span[1] [single]': request unsuccessful: POST /session/9016e42e-3373-43f3-b9e0-9d667b51b953/element/click did not match a known command",
      }
      failed to click on selection 'XPath: //*[@id='content']/div[1]/div/div[1]/div/div/span[1] [single]': request unsuccessful: POST /session/9016e42e-3373-43f3-b9e0-9d667b51b953/element/click did not match a known command
@Bo0mer
Copy link

Bo0mer commented Jan 13, 2019

I’m having the same issue. If you’re aware of any workaround or what’s needed to fix the issue please share.

Edit: The problem is that geckodriver uses the Webdriver protocol while the agouti implementation uses the JSON wire protocol.

Thanks.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants