(2022-12-19, 20:47)Orski Wrote: After tinkering around a little and after a number of restores, I think this is happening because the actual shortcuts and customizations aren't stored in the userdata folder but in the main addon folder for arctic horizon in .kodi/addons/skin.arctic.horizon.2 with links or maybe identifiers that tell it to which user to go to. Which renders what I want to do rather impossible or very hard to accomplish, if anyone has any idea how to fix this or make it possible it's most appreciated.

Thank you.

(2022-12-19, 22:02)taiseer999 Wrote:

(2022-12-19, 20:47)Orski Wrote: After tinkering around a little and after a number of restores, I think this is happening because the actual shortcuts and customizations aren't stored in the userdata folder but in the main addon folder for arctic horizon in .kodi/addons/skin.arctic.horizon.2 with links or maybe identifiers that tell it to which user to go to. Which renders what I want to do rather impossible or very hard to accomplish, if anyone has any idea how to fix this or make it possible it's most appreciated.

Thank you.

Customisation is in userdata/addon_data/script.skinshortcuts

I normally copy that folder and paste it among my devices

• plugin.video.themoviedb.helper
  
• script.skinvariables
  
• script.texturemaker
  
• script.skinshortcuts (optional: If you want to have the same shortcuts as the masteruser)
  

(2022-12-19, 23:01)Orski Wrote: @taiseer999 Thank you, after looking at the logs a bit more, I was apparently missing dependencies and when you pointed out scripts.skinshortcuts it clicked.

So for anyone trying to make different profiles using this skin, you should start a fresh profile (no copying from default), then enabling the skin (don't use it yet) and copying:

• plugin.video.themoviedb.helper
  
• script.skinvariables
  
• script.texturemaker
  
• script.skinshortcuts (optional: If you want to have the same shortcuts as the masteruser)
  

Then reboot and log in the profile and choose AH2 as your skin, and it should work.

(2022-12-20, 03:52)he4vyg Wrote: This is an amazing skin!! I have it working on my main HTPC on Windows with Matrix, and on an Android box with Nexus. I can't get over how quick everything is to load, as I've been persevering with Titan Bingie Mod V2 for the modern 'Netflix' feel, but it runs so slow on my (admittedly older) HTPC, and forget about putting it on an Android box Kudos to @jurialmunkey on such a gorgeous and quick running skin.

One feature request, if I may, is to add a 'previous channel' button to the PVR, which I have found really handy with the Estuary mod V2.

Cheers, and Merry Christmas to all!

(2022-12-19, 10:00)jurialmunkey Wrote:

(2022-12-18, 10:13)oo_void Wrote: Somewhere, you probably have a fatal race condition compounded by the Python version change ... If you were someone I was working more closely with, I'd give you the "defensive" programming speech . It typically involves watching your typing, catching your API parsing errors, and failing verbosely. I know you'll figure out the root cause eventually, but it shouldn't be written off as a doesn't happen with my computer-type situation.

This is nonsense and displays significant misunderstanding of basic aspects of how Python works as a programming language. You would immediately lose any credibility if you gave that "speech" in a professional capacity.

Quote:It typically involves watching your typing

Python is not statically typed.

Quote:catching your API parsing errors

Python's default behaviour is to log exceptions with tracebacks. A "parsing error" not "caught" in a try/except block will simply cause the Python interpreter to exit with a traceback log message. Kodi will continue.

Quote:and failing verbosely

Logging verbose information in anticipation of an unexpected crash is not (sanely) possible in any language.

Any error that can "fail verbosely" must be, by nature, one we can define and catch. Logging is a waste if we already know the cause. We either fix the underlying error or catch it as an exception to handle before it causes a crash.

This is not the same type of failure as an application crashing unexpectedly from undefined behaviour. We only know about that type of crash after it is too late. "Failing verbosely" in this case is either the figurative insanity of logging everything constantly "just in case" or the true insanity of attempting to invent time travel.

Quote:Somewhere, you probably have a fatal race condition compounded by the Python version change

No. Python does not have true multithreading. The type of race condition you are alluding to is practically impossible in Python. In Python, the GIL prevents two threads from working on the same object simulatenously.

Moreover, Python is a high level programming language. Pitfalls such as null pointer dereferencing, buffer overflows, and divide by zero errors aren't really concerns. At worst, a "race condition" in Python means we get an unexpected value returned or the interpreter exits raising an error. These are not fatal.

Quote:it shouldn't be written off as a doesn't happen with my computer-type situation.

I'm not writing it off. I don't doubt TMDbHelper is agitating an underlying bug introduced on these platforms. What I am doubting is that TMDbHelper is doing something wrong.

Sure, if I introduced a *new* feature and I got reports of crashes on other platforms, THEN I'm not going to forge ahead saying "screw you, works fine for me sucker!". I'd look for an alternative in that case, but that's not what is happening here. Here we have something that WAS working fine on both Matrix and Nexus. Then some platforms introduced a breaking bug.

If this breaking change is not a documented deprecation of a method then it is unintentional and needs to be fixed at the root. It's a fools errand for me to look to "fix" an issue on a platform I don't have access to, for a bug I cannot recreate, for something that works correctly in all previous versions, using correct code, and has now only broken on account of a change made in an "unstable prerelease" version of Kodi rather than any change I made.

(2022-12-20, 17:17)hyzor Wrote: Ok so I've been trying to track down the issue with Kodi crashing on Android TV (Nvidia Shield) when using this skin and others that use TheMovieDB Helper.

As others in this thread already mentioned the build kodi-20221015-4b558c86-master-24580-arm64-v8a.apk does seem stable without any crashes, so I started with this build and worked my way forward, testing every build since, I found that the build kodi-20221101-1f61ce44-master-24775-arm64-v8a.apk is the culprit. kodi-20221031-d37c91b7-master-24767-arm64-v8a.apk is the last build that seems stable for me.

So then I began to dig into the commits between these two builds, and what I notice is that Python's been upgraded from 3.9 to 3.11, along with some modules being upgraded. Could it be that 3.11 is causing the crash? Here is the last commit that made it into the build that crashes: https://github.com/xbmc/xbmc/commit/1f61ce445abaaeaa5c27bb48413d2c5c40671354, I don't know much about Kodi but seems to be a lot of changes involved by upgrading to 3.11.

I've enabled logging but it doesn't seem to give me any evidence on what's causing the crash...

(2022-12-20, 17:17)hyzor Wrote: Ok so I've been trying to track down the issue with Kodi crashing on Android TV (Nvidia Shield) when using this skin and others that use TheMovieDB Helper.

As others in this thread already mentioned the build kodi-20221015-4b558c86-master-24580-arm64-v8a.apk does seem stable without any crashes, so I started with this build and worked my way forward, testing every build since, I found that the build kodi-20221101-1f61ce44-master-24775-arm64-v8a.apk is the culprit. kodi-20221031-d37c91b7-master-24767-arm64-v8a.apk is the last build that seems stable for me.

So then I began to dig into the commits between these two builds, and what I notice is that Python's been upgraded from 3.9 to 3.11, along with some modules being upgraded. Could it be that 3.11 is causing the crash? Here is the last commit that made it into the build that crashes: https://github.com/xbmc/xbmc/commit/1f61ce445abaaeaa5c27bb48413d2c5c40671354, I don't know much about Kodi but seems to be a lot of changes involved by upgrading to 3.11.

I've enabled logging but it doesn't seem to give me any evidence on what's causing the crash...