[X] I use the most recent available driver/plugin and server versions
Is the component officially supported by the Appium team?
[X] I have verified the component repository is present under the Appium organization in GitHub
Is there an existing issue for this?
[X] I have searched the existing issues
Current Behavior
org.openqa.selenium.SessionNotCreatedException: Could not start a new session. Response code 500. Message: An unknown server-side error occurred while processing the command. Original error: Cannot connect to the Dart Observatory URL ws://127.0.0.1:36045/c4aAUZwVOjg=/ws. Check the server log for more details
Host info: host: 'DESKTOP-DO44MD4', ip: '192.168.68.139'
Build info: version: '4.17.0', revision: 'e52b1be057*'
System info: os.name: 'Windows 11', os.arch: 'amd64', os.version: '10.0', java.version: '17.0.10'
Driver info: io.appium.java_client.android.AndroidDriver
at org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:139)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at io.appium.java_client.remote.AppiumProtocolHandshake.createSession(AppiumProtocolHandshake.java:133)
at io.appium.java_client.remote.AppiumProtocolHandshake.createSession(AppiumProtocolHandshake.java:102)
at io.appium.java_client.remote.AppiumCommandExecutor.createSession(AppiumCommandExecutor.java:176)
at io.appium.java_client.remote.AppiumCommandExecutor.execute(AppiumCommandExecutor.java:237)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:519)
at io.appium.java_client.AppiumDriver.startSession(AppiumDriver.java:268)
at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:162)
at io.appium.java_client.AppiumDriver.<init>(AppiumDriver.java:90)
at io.appium.java_client.AppiumDriver.<init>(AppiumDriver.java:102)
at io.appium.java_client.android.AndroidDriver.<init>(AndroidDriver.java:109)
at fanfare.dev.timellne.a_setup.launchApp(a_setup.java:82)
at fanfare.dev.timellne.HomeModule.setUp(HomeModule.java:70)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at org.testng.internal.invokers.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:139)
at org.testng.internal.invokers.MethodInvocationHelper.invokeMethodConsideringTimeout(MethodInvocationHelper.java:69)
at org.testng.internal.invokers.ConfigInvoker.invokeConfigurationMethod(ConfigInvoker.java:393)
at org.testng.internal.invokers.ConfigInvoker.invokeConfigurations(ConfigInvoker.java:326)
at org.testng.TestRunner.invokeTestConfigurations(TestRunner.java:661)
at org.testng.TestRunner.beforeRun(TestRunner.java:650)
at org.testng.TestRunner.run(TestRunner.java:612)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:443)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:437)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:397)
at org.testng.SuiteRunner.run(SuiteRunner.java:336)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:95)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1301)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1228)
at org.testng.TestNG.runSuites(TestNG.java:1134)
at org.testng.TestNG.run(TestNG.java:1101)
at com.intellij.rt.testng.IDEARemoteTestNG.run(IDEARemoteTestNG.java:65)
at com.intellij.rt.testng.RemoteTestNGStarter.main(RemoteTestNGStarter.java:105)
Expected Behavior
everything was working yesterday. no they are showing unknown server side error.
Minimal Reproducible Example
trying running any testNG suites
Environment
Operating system:
Appium server version (output of appium --2.11.3):
Appium driver(s) and their version(s) (appium driver list):
driver uiautomator2 updated: 3.5.2 => 3.7.9
driver flutter updated: 2.6.0 => 2.9.2
Appium plugin(s) and their version(s) (appium plugin list):
appium-reporter-plugin@1.1.0-beta.06
Node.js version (output of node --v20.17.0):
npm version (output of npm --10.8.2):
Last component(s) version which did not exhibit the problem: - same pc same specs same versions
Platform and version under test: Windows 11
Real device or emulator/simulator: Xiaomi Note 10 (2gb)
Do I have the most recent component updates?
Is the component officially supported by the Appium team?
Is there an existing issue for this?
Current Behavior
org.openqa.selenium.SessionNotCreatedException: Could not start a new session. Response code 500. Message: An unknown server-side error occurred while processing the command. Original error: Cannot connect to the Dart Observatory URL ws://127.0.0.1:36045/c4aAUZwVOjg=/ws. Check the server log for more details Host info: host: 'DESKTOP-DO44MD4', ip: '192.168.68.139' Build info: version: '4.17.0', revision: 'e52b1be057*' System info: os.name: 'Windows 11', os.arch: 'amd64', os.version: '10.0', java.version: '17.0.10' Driver info: io.appium.java_client.android.AndroidDriver
Expected Behavior
everything was working yesterday. no they are showing unknown server side error.
Minimal Reproducible Example
trying running any testNG suites
Environment
Operating system:
Appium server version (output of
appium --2.11.3
):Appium driver(s) and their version(s) (
appium driver list
):Appium plugin(s) and their version(s) (
appium plugin list
):Node.js version (output of
node --v20.17.0
):npm
version (output ofnpm --10.8.2
):Last component(s) version which did not exhibit the problem: - same pc same specs same versions
Platform and version under test: Windows 11
Real device or emulator/simulator: Xiaomi Note 10 (2gb)
Link to Appium Logs
https://github.com/appium
Further Information
No response