Closed Jiyvn closed 2 months ago
appium:rcOnly
caps would help. Then it skips https://github.com/headspinio/appium-tizen-tv-driver/blob/8abdede79baab1a1382b8e7c91c385bc23a99066/packages/appium-tizen-tv-driver/lib/driver.js#L326
thank you @KazuCocoa. I am able to connect to the tv after setting appium:rcOnly
to true, but unfortunately, our app is web-based.
Then, so far, it looks like the debug command is used to get debug port by the test target to attach to a chromedriver session. Perhaps... if we have a way to detect a method to get the app's debug port somehow, it will be able to skip.
For example useOpenDebugPort
capability is it. If you already know the debug port on the tv device, it will let you skip the debug command
If no, this driver would not work in such environment unfortunately
Problem
command
sdb shell 0 debug
works on Tizen 5.5 (TizenTV 2020) but fails for Tizen 3.0 (TizenTV 2017) with same wgt 20202017
sdb capability
the install/uninstall command is fine. Is it possible to skip debug command
appium server log
the app should be debuggable as using the same wgt https://github.com/headspinio/appium-tizen-tv-driver/blob/main/packages/appium-tizen-tv-driver/README.md#troubleshooting
A similar issue was reported before in repo Samsung/appium-tizen-driver, so that's why I report here https://github.com/Samsung/appium-tizen-driver/issues/10