2016-10-21, 09:03
Could you guys please try this windows build?
http://mirrors.kodi.tv/test-builds/win32...nstall.exe
http://mirrors.kodi.tv/test-builds/win32...nstall.exe
2016-10-21, 15:05
(2016-10-21, 09:03)Martijn Wrote: Could you guys please try this windows build?
http://mirrors.kodi.tv/test-builds/win32...nstall.exe
Thanks I will give it a try today and let you know the results
2016-10-21, 17:09
(2016-10-21, 09:03)Martijn Wrote: Could you guys please try this windows build?
http://mirrors.kodi.tv/test-builds/win32...nstall.exe
Sorry to say but I am still getting "Update Failed" when trying to install update for Metropolis skin
2016-10-21, 17:16
2016-10-21, 17:31
(2016-10-21, 17:26)Martijn Wrote: Same happens for me. Asked to the dev to look at it
Had the same issue for weeks now with estuary MOD
I even try switching back to stock estuary before updating but it give the same result
2016-10-21, 17:34
(2016-10-21, 17:31)Gracus Wrote:(2016-10-21, 17:26)Martijn Wrote: Same happens for me. Asked to the dev to look at it
Had the same issue for weeks now with estuary MOD
I even try switching back to stock estuary before updating but it give the same result
Same here. After it fails I have to exit Kodi and restart Kodi (which is then running regular Estuary), and then I can successfully install Estuary MOD updates from zip files.
2016-10-23, 10:17
Just to clarify: is it only installing updates of the currently in-use skin that fails, or on any add-on installs? The purpose of this build was not to fix the issue, but just to see if it produced any different error message..
2016-10-23, 10:48
For me at least, it's just the current in-use skin. I have no problems installing other add-ons.
2016-10-23, 10:55
Also for me it's just the in-use skin.
Gesendet von meinem LG-H815 mit Tapatalk
Gesendet von meinem LG-H815 mit Tapatalk
2016-10-23, 11:12
Thanks guys. Unfortunately the log didn't reveal anything new other than that windows refuse to move the in-use skin files, so to be continued..
2016-10-23, 12:20
Am i right that kodi leaves open file handles to skin files?
Can you make a debug version and put in any open and close related to skin an debug message with the file name and handle number?
Maybe we can find out on which handle/file does not get closed correctly.
Can you make a debug version and put in any open and close related to skin an debug message with the file name and handle number?
Maybe we can find out on which handle/file does not get closed correctly.
2016-10-24, 16:36
(2016-10-23, 10:17)takoi Wrote: Just to clarify: is it only installing updates of the currently in-use skin that fails, or on any add-on installs? The purpose of this build was not to fix the issue, but just to see if it produced any different error message..
I can also confirm I only get the update failed message when updating the currently skin in use.
2016-10-31, 23:21
(2016-10-31, 23:09)Martijn Wrote: New test build
http://mirrors.kodi.tv/test-builds/win32...exture.exe
Cool about to test be back with results
