[axlt2002]

hi @axlt2002 

Running 4.0.2

update.log & kodi.log
wokakarute.kodi (paste)

Stuck on Jumanji: Welcome to the Jungle this time.

thanks for investigating!                     

Hi @zerocool_ie, thanks for your further logs.

It seems there is an issue in the code I use to generate the log file. Anyway, what sounds strange to me, is that you wrote "Stuck on Jumanji: Welcome to the Jungle this time.". Does this mean that the issue is not always happening at the same time (i.e. same movie)? If it is the case, I think it could be related to a network connection issue...if the error is not systematic (i.e. can not be replayed), maybe is related to some conditions that have changed since the last time. Slow network come to my mind...

Can you please try to update Jumanji from the context menu and report me back if it works? Please also run another library update and check where it does go stuck...

Thanks,

Alex

P.S.: I will anyway fix the bug in the log file in the next version.                   

hi @axlt2002 

 

Does this mean that the issue is not always happening at the same time (i.e. same movie)?

Yes, seems random.


Context update on Jumanji: Welcome to the Jungle
Looked to go well, at least no errors.
https://paste.kodi.tv/ferericupi.kodi

Full update

• 376 successful
  
• errors
  interesting:
  Code:

  Error Contents: HTTPSConnectionPool(host='www.imdb.com', port=443): Max retries exceeded with url: /title/tt5941796/awards (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x5369cc70>: Failed to establish a new connection: [Errno 113] No route to host',))
• 2 more successful
  
• some errors
  
• 2 more successful
  

https://paste.kodi.tv/cixayucure.kodi

hope this helps and thanks again 

Hi @zerocool_ie, thanks for the update. Well, it looks really like is related to some issue accessing the site...and its not related to the add-on itself, so I fear that there is nothing I can do...

I'm going to release a new version by today in which I have fix (hopefully) the bug in the log file...may be it will help to understand better which could be the issue.

Cheers!