I have a Selenium Java automation framework that includes support for Appium, and I’m able to perform a simple set of tasks on a sample application in my unit test suite. I’m now attempting to implement an automated web application test on Android Chrome via Appium and have been unable to start a new session. The current issue appears to be caused by a mismatch between the version of the browser (Google Chrome 133.0.6943.137) and available versions of the driver which are all targeted at Chrome for Testing releases.
Here’s the error I end up with when I execute a test:
org.openqa.selenium.SessionNotCreatedException: Could not start a new session. Response code 500. Message: Could not start a new session. Could not start a new session. Error while creating session with the service http://172.24.144.1:40327. Could not start a new session. Response code 500. Message: An unknown server-side error occurred while processing the command. Original error: No Chromedriver found that can automate Chrome ‘133.0.6943’. You could also try to enable automated chromedrivers download as a possible workaround.
The closest match between the installed browser and available driver releases is 133.0.6943.141. I strongly suspect that this browser/driver combination would work just fine, and ChromeDriver includes an option to disable the version check (disable-build-check), but I don’t know if there’s any way for me to specify this in the configuration I’m attempting to create.
Is this configuration supposed to work in Appium from Java?