Open mlopezuno opened 3 weeks ago
Could you share the full appim server log?
Also, could the app run with sdb -s <my-ip>\:26101 shell 0 debug my-app
without this driver?
I observed the debug mode run could fail to start for some reason. (TV internal) If the error is kind of random failure, https://github.com/headspinio/appium-tizen-tv-driver/pull/676 will help to improve with retry logic. If your app was not debggable one, appium:rcMode
as remote
and appium:rcOnly
will also help. They will not run chromedriver but it does not require debuggable app. https://github.com/headspinio/appium-tizen-tv-driver/tree/main/packages/appium-tizen-tv-driver#press-key is available for the mode.
https://github.com/headspinio/appium-tizen-tv-driver/tree/main/packages/appium-tizen-tv-driver
@KazuCocoa Thanks for answering, appreciate it!
I am able to run the app with sdb -s <my-ip>\:26101 shell 0 debug my-app
The full logs are basically what I sent you, they are repeating that same part I sent earlier and after a time they timeout.
I see that adding appium:rcMode
as remote
and appium:rcOnly
as true
is giving me a new error which is expected because I don't have my tests written in a way that uses remote (I have js).
However I do want to use chromedriver, the reason is I already have tests written in for the webos-appium-driver that I want to re-use here.
Hi, I have started using the appium-tizen driver and I've been able to get unstuck on many issues I encountered, right now I am finally able to load my-app in the TV using the driver but my tests don't run, at the end I get a message like this:
Does someone know how can I fix this? It looks like I have to run my app in debug mode.