[🐛 Bug]: Selenium 4.22.0 breaks Appium

[agray]

What happened?

Upgrading to 4.22.0 gives this error on newing up an AndroidDriver object:

{"Method 'ExecuteAsync' in type 'OpenQA.Selenium.Appium.Service.AppiumCommandExecutor' from assembly 'Appium.Net, Version=5.0.0.0, Culture=neutral, PublicKeyToken=null' does not have an implementation.":"OpenQA.Selenium.Appium.Service.AppiumCommandExecutor"}

Downgrading to 4.21.0 and the issue does not occur.

How can we reproduce the issue?

Project with dependencies:

Appium.WebDriver Version 5.0.0-rc.8 and Selenium 4.22.0 do not play together.
Appium.WebDriver Version 5.0.0 and Selenium 4.22.0 do not play together.
Appium.WebDriver Version 5.0.0 and Selenium 4.21.0 work fine
Appium.WebDriver Version 5.0.0-rc.8 and Selenium 4.21.0 work fine.

Relevant log output

{"Method 'ExecuteAsync' in type 'OpenQA.Selenium.Appium.Service.AppiumCommandExecutor' from assembly 'Appium.Net, Version=5.0.0.0, Culture=neutral, PublicKeyToken=null' does not have an implementation.":"OpenQA.Selenium.Appium.Service.AppiumCommandExecutor"}```

Operating System

Windows 11

Selenium version

4.22.0

What are the browser(s) and version(s) where you see this issue?

Chrome Latest

What are the browser driver(s) and version(s) where you see this issue?

AndroidDriver

Are you using Selenium Grid?

SauceLabs

[github-actions[bot]]

@agray, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[titusfortner]

Yes, Selenium added methods to a couple interfaces that Appium does not implement. We'll work with Appium .NET devs to try to keep these in sync better, but the fix for this is in Appium not Selenium.