Notes on Tizen commands that might work

tizen.sh

sdb connect <ip>:<port> # connect to TV
sdb -s <deviceName> capability # get <installationPath>

# build
tizen cli-config "default.profiles.path=<profile_path>"
tizen build-web -out .buildResult -- <source-dir>
tizen package --type wgt --sign profileName -- <source-dir>/.buildResult # extract <package-file>
mv <package-file> .
rm -rf <source-dir>/.buildResult

# install
sdb -s <deviceName> push tizen/build/<0000.name>.wgt <installationPath>
sdb -s <deviceName> shell 0 vd_appinstall <0000.name> <installationPath>/<0000.name>.wgt

# uninstall
sdb -s <deviceName> shell 0 vd_appuninstall <0000.name>

# launch app (debug)
sdb -s <deviceName> shell 0 debug <0000.name> # get <port>
sdb -s <deviceName> forward --remove tcp:<port>
sdb -s <deviceName> forward tcp:<port> tcp:<port>
# then open Chrome on http://localhost:<port>

# launch app
sdb -s shell 0 was_execute <0000.name>

/sdb shell 0 debug

I think you need to add a last argument for the application id you want to debug.

<tizen:application id="your.id" ...>

sdb shell 0 debug your.id

Thanks for the reply!

I think i reverse engineered wits to find the commands

Ok, that's also what I ended up doing. Also asked Samsung about the commands but they had no good answer.

I think you need to add a last argument for the application id you want to debug.

To debug an app you need to include the ID, yes. I intentionally left it out generate the error message displaying what command it's translated to on the client (the TV) 🙂.

sdb shell 0 debug packageId.appId runs /usr/bin/app_launcher --start packageId.appId --web-debug on the client. Where the translation from the former command to the latter happens is a mystery to me. I suspect it's by sdb, either on the client or on the host (your computer).