Not able to start session

[pauliusguzas]

Hello, I have setup this driver using WebdriverIO, but I am not able to start session always getting error below

[0-0] 2023-09-20T13:08:27.637Z ERROR @wdio/runner: Error: Failed to create session.
[0-0] An unknown server-side error occurred while processing the command. Original error: Command '/Users/pauliusguzas/tizen-studio/tools/sdb -s 192.168.1.29\:26101 shell 0 debug my.cool.app.id' exited with code 1. Stdout was: ''. Stderr was: 'closed '

These are my capabilities:

      {
            platformName: 'TizenTV',
            'appium:options': {
                automationName: 'TizenTV',
                deviceName: '192.168.1.29:26101',
                chromedriverExecutable: '/Users/pauliusguzas/Downloads/chromedriver',
                appPackage: 'my.cool.app.id',
                app: 'path/to/my/app.wgt',
                fullReset: true,
            },
        },

Versions used:

        "@wdio/allure-reporter": "7.19.5",
        "@wdio/appium-service": "7.19.5",
        "@wdio/cli": "7.19.5",
        "@wdio/local-runner": "7.19.5",
        "@wdio/mocha-framework": "7.19.5",
        "@wdio/selenium-standalone-service": "7.19.5",
        "@wdio/spec-reporter": "7.19.5",
        "allure-commandline": "2.17.2",
        "appium": "2.0.0",
        "appium-mac2-driver": "1.7.2",
        "appium-uiautomator2-driver": "2.29.5",
        "appium-xcuitest-driver": "4.32.11",
        "appium-tizen-tv-driver": "0.8.1",
        "appium-lg-webos-driver": "0.0.6",
        "chromedriver": "102.0.0",
        "wdio-chromedriver-service": "7.2.2",
        "wdio-image-comparison-service": "5.0.3",
        "wdio-native-app-compare-service": "2.1.0"

[pauliusguzas]

cc @jlipps

[jlipps]

What happens if you try to run that command on your own? If it doesn't work then the driver won't be able to do its thing

[pauliusguzas]

command simply returns closed whatever that means

[jlipps]

Yep that means it didn't work. You'll need to go through whatever troubleshooting you need to do with your app or the device to make that command work. Maybe the app is not built in debug mode?