[Guice/ErrorInCustomProvider]: SessionNotCreatedException: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.

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

I use
Appium server v2.11.2

io.appium
java-client
9.1.0

selenide
com.codeborne
7.1.0

I use options for android driver
public UiAutomator2Options getOptions() {
UiAutomator2Options options = new UiAutomator2Options();
File app = new File(“C:\Users\kristina.lapteva\Desktop\test\gostest.apk”);

options.setPlatformName("Android");
options.setDeviceName(config.get("deviceName"));
options.setPlatformVersion(config.get("platformVersion"));
options.setAutomationName("UiAutomator2");
options.setNewCommandTimeout(Duration.ofSeconds(120));
options.setAndroidInstallTimeout(Duration.ofSeconds(180));

options.setIgnoreHiddenApiPolicyError(true);
options.setApp(app.getPath());
options.setUdid("emulator-5554");
options.setAutoGrantPermissions(true);
options.setAppWaitDuration(Duration.ofSeconds(120));

return options;

}

I try
String url = "http://127.0.0.1:4723/wd/hub";
AndroidDriver androidDriver = new AndroidDriver(new URL(url),options);

and i have a problem
com.google.inject.ProvisionException: Unable to provision, see the following errors:

1. [Guice/ErrorInCustomProvider]: SessionNotCreatedException: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.
   Host info: host: '*', ip: '192.168.0.17'
   at AppiumModule.selenideDriver(AppiumModule.java:85)
   _ installed by: Elements$ElementsAsModule -> CoreModule -> DeviceModule -> AppiumModule
   at SelenideUiSteps.driver(SelenideUiSteps.java:72)
   _ for field driver
   at IntegrationCommonUiSteps.class(IntegrationCommonUiSteps.java:34)
   while locating IntegrationCommonUiSteps
   at BaseDynamicTest.commonUiSteps(BaseDynamicTest.java:57)
   _ for field commonUiSteps
   while locating ConvictionDynamicTest

Expected Behavior

Android driver is running successfully

Minimal Reproducible Example

public UiAutomator2Options getOptions() {
UiAutomator2Options options = new UiAutomator2Options();
File app = new File("C:\Users\kristina.lapteva\Desktop\госуслуги приложения\gostest.apk");

    options.setPlatformName("Android");
    options.setDeviceName(config.get("deviceName"));
    options.setPlatformVersion(config.get("platformVersion"));
    options.setAutomationName("UiAutomator2");
    options.setNewCommandTimeout(Duration.ofSeconds(120));
    options.setAndroidInstallTimeout(Duration.ofSeconds(180));
    //для игнорирования ошибок, связанных с политикой скрытого API
    options.setIgnoreHiddenApiPolicyError(true);
    options.setApp(app.getPath());
    options.setUdid("emulator-5554");
    options.setAutoGrantPermissions(true);
    options.setAppWaitDuration(Duration.ofSeconds(120));
    options.setLocale("RU");
    options.setLanguage("ru");

    return options;
}

String url = "http://127.0.0.1:4723/wd/hub";
AndroidDriver androidDriver = new AndroidDriver(new URL(url),options);

Environment

• Operating system:
• Appium server version (output of appium --version): v2.11.3
• Appium driver(s) and their version(s) (appium driver list):uiautomator2@3.7.6
• Appium plugin(s) and their version(s) (appium plugin list): not installed
• Node.js version (output of node --version):v20.15.1
• npm version (output of npm --version):10.8.2
• Last component(s) version which did not exhibit the problem:
• Platform and version under test:windows 10
• Real device or emulator/simulator:emulator

Link to Appium Logs

Further Information

no

Begin at AppiumModule.java:85 and SelenideUiSteps.java:72, then reproduce the AndroidDriver setup with the listed Appium, java-client, Selenide, and UiAutomator2 versions. Capture the missing Appium server logs and verify the endpoint, emulator, and APK inputs. Done means isolating a java-client defect from an environment or configuration failure; the issue provides no test or clear code location.