sdb is broken (so potentially swapping sdb for the one from S1.3 may fix this problem - although the old sdb may have problems with talking to non-existent v4.0 TV devices), or 2. However, since it cannot do any shell commands, we have two options: 1. Since sdb can push the app to TV, at least the basic communication is working. Although, maybe there is a document somewhere that has those error codes (tried to google it, found zilch). Of course, seeing "app_id install failed" means really nothing to me, and I don't have Samsung person sitting next to me to translate that nonsense. It would be also nice, if tizen.bat had 'kill' and 'status' options (we are debugging over the network, so it would be much easier to use CLI tools than a remote for that particular TV). What is kind of painful is that Samsung put a page that nicely describes what can be done with tizen.bat, but there is no mention there about how to debug an app with CLI tools. So, my first question here is whether there is any way to see TV logs while working only with tizen.bat (CLI tools). Also, we can assume that building an app with 4.0 SDK, we should be able to target 3.0 devices (although, potentially some features would not work). One thing I noticed, that in Device Manager, I don't see file structure on my TV (as on many screenshots provided by Samsung), and also when I select 'Open shell' menu item, the cmd line window briefly opens and immediately closes (assuming sdb connection to the TV was killed). In such a case, sdb should also be able to depend on that cert being installed, but it isn't. We can for time being assume that the first case is true. So, this exercise tells that either cert is installed properly, and all should work, or Samsung has security issues with tizen.bat installing apps without properly installed cert. I added "console.log" to main.js, but am not sure whether it is possible to see that ouput somewhere. Once the package was installed, I can also run "tizen run -p 123.BasicUI -t UN40MU6290", and tizen.bat is happy reporting that app was launched (yes, it is running on my TV). As long as config.xml has 'Required Version' set to 3.0 (like my 2017 TV), tizen.bat installs the package. After that, once again used tizen.bat to install it. Again, created a BasicUI app, built it, and built a signed package. I did install S2.1 again with just TV-4.0 SDK. My next step was to see how can I see the logs after that tizen.bat push, but I saw Pamela's comment, and wiped out Studio 2.1 With your comments, I am kind of stuck right now which way to go :)Īctually, what got me really triggered to remove S2.1 was some Samsung note in S2.1 relase documents (cannot find it anymore) that installing certs on target devices is broken in S2.1, and will be fixed in the future releases (sounds like April 1st joke). Or to check whether S1.3 is setting any environ variables for things like sdb. What could be interesting to see is whether an older sdb (e.g., from Studio 1.3) could be used to replace the one from S2.1. Of course, few options are there, like sdb in Studio 2.1 is really broken, sdb cannot find some config files. So, if cert is installed, then sdb in theory should work. However, if Samsung knows what they are doing, if tizen.bat can push the file, it means that cert is installed (really, cannot say that I trust Device Manager, seeing it working). I didn't find any references to sdb, so those two may not have anything in common (although, I could miss that sdb trace in that output). Yes, I got that Hello app pushed, and running on a TV with tizen.bat I was hoping that tizen.bat is somehow using sdb.exe to do the push, and got stuck reading plenty of junk output.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |