![]() It's just a little too demanding on android. I also have Eunique and dependencies installed, but not in use. I should probably mention that I didn't actually install the skin with SPMC, I copied my entire configuration across from Kodi so the original install has gone through several updates since it was first installed and I already had all dependencies. I was just meaning to say that despite warnings and such it is working great and always has, after a restart I have had no more warnings about incompatibilities. I don't own an Android device so I can never predict how the skin will react on Android. However, since that's a big update it will need to be throughly vetted. The next major release (3.2.10) should remove all of those missing dependencies for the legacy code. If you are still getting the issue a closer look will need to be taken but there is no known installation issues with this - I hope you have it up and running smoothly on SPMC with the dependencies that were required but can't be found in the repositories. Nevertheless, for you I would first tell you to update Kodi to the latest version, install all the prerequisites, and then install the the skin again. However, until they produce their debug logs, I can't replicate the issue but know it's solved by pulling the latest Skin Helper Service from Emby's Beta Repo. Your issue may be related to an issue brought to my attention on the Kodi forums: which I need to bring to attention as I have never heard of a plugin causing Kodi to delete the theme files. The error you are receiving is related to the fact your version of Kodi seems to be unable to parse the addon.xml file which tells Kodi what the skin requires (and it does require the legacy plugins to support the legacy code until the next major update). First, update Kodi Jarvis from Beta 4 to Kodi Jarvis 16 Release or Kodi Jarvis 16.1 Release Candidate 1. Please let me know if you need anything else. ![]() I am running Jarvis 16 Beta 4.ġ2:17:21 T:139899920529152 ERROR: CAddonInstallJob: could not read addon description of special://home/addons/ I referred to the first post and installed the two dependencies, but it still doesn't work. ![]() Installation fails when I try to re install from the Beta Repo. When I loaded it up today, it had reverted to confluence. Perhaps there's something wrong with my system config. I downloaded the skin zip from the first page manually, and installed the skin from that. The release schedule should be: 3.2.03 (tonight/tomorrow) -> 3.2.04 (this upcoming week) -> 3.2.10 (this is the big update that should remove most if not all legacy code).Įdit: It works now. Apparently, it runs perfectly fine under Jarvis too. I'm going to tag to see if it's okay to copy over a copy of the legacy to Jarvis' repository for Emby until I can get through all the legacy code that needs to be replaced and supplemented. is still currently deeply embedded into the skin and when I removed it's requirement as I thought I had moved it far enough a long to not need it anymore that's when all of this started.Īn update will be released later tonight (I just got my new Western Digital Re drives to replace failing Seagates) with a corrected addons.xml file and color picker fixes. Well, we figured out why some could always install AZ:FA and others could not. ![]() ![]() Version 3.0.02 introduced the removal of "script.duration" - I wonder if that's causing the install to fail? I am open to suggestions from everyone in trying to track this down as I can't move forward until we get install working again without sideloading the skin. I know minus0 is taking a look into making sure it works on Android, perhaps he'll stumble upon something I am missing because I look at a lot of code all day whether it's for state-of-the-art technology or a skin for Kodi so sometimes you get "code-blind" as I like to call it and when you think you see something but it's actually not there or you type something for the wrong application. However, the debug logs only ever show that it can't reach From Ashes' addon's xml file and I am honestly running out of ideas. Perhaps that's why the final version of AZ:E went back to the other view menu selector rather than the one implemented in 2.0.8 which is what AZ:FA uses as it seems the problem was introduced with that. When I spoke to about this a while ago it used to drive him crazy and he couldn't figure out what caused it. so im good at this point, but i agree there must be something in the dependencies thats not right or relies on another skin to already be there that i didnt also concur that something is either incorrectly listed in the dependencies or something is missing. i did manage to get the skin installed by extracting the zip contents and moving to the addons folder. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |