Posts: 12,706
Joined: Nov 2003
Reputation:
129
spiff
Team-Kodi Member
Posts: 12,706
it's pretty easy to explain what happens.
we drop the repo info. we then go on to fetch the new. if there's a time out, repo ends up empty. i did it like this since if there is a repo update, and you stick to the old info, you get weird errors (zips not found and such), while with a blank repo is obvious to everybody that they need to retry.
Posts: 77
Joined: Nov 2012
Reputation:
3
2013-03-04, 23:09
(This post was last modified: 2013-03-04, 23:25 by BartOtten.)
Yeah, it's obvious for people who know how such system works. However, users tend to think the repo is broken/not working instead of a 'local problem'. So the current solution is working developer wise, but user wise I think we have to come up with a better solution. Possible solutions I can think of:
- As far as I know, XBMC checks the current MD5 with the online MD5 to know if the addons.xml is outdated. Maybe it's a good thing to replace the current md5 only if the update was successful and check after each update if the MD5 are the same. If not, try to update addons.xml again (maybe with interfal and a max).
- Show "Something went wrong. Please click here to force refresh" if the users opens the addonlist of a repo in XBMC
Posts: 12,706
Joined: Nov 2003
Reputation:
129
spiff
Team-Kodi Member
Posts: 12,706
sure, it will have to be the latter.
it's not that we update the checksum (if it does, there's a bug). but the thing is, any old listing is known outdated once we know there's an update and repo's won't keep old versions of add-ons around. so you get cryptic failed to install messages instead if you try to grab an outdated add-on. for this reason, i chose to drop the old listing as soon as i know it's outdated. repos ARE checked, on a (by default) 6h interval, if a timeout occurs, it should be rechecked on the short cycle interval (10 mins iirc).
Posts: 1
Joined: Dec 2012
Reputation:
0
The way it seems to me and others over at cord cutters is that this repo made a big splash announcing itself, and to our disappointment we can't retrieve content. It may be user error but your instructions are limited and we have very little resources to figure it out.
Posts: 77
Joined: Nov 2012
Reputation:
3
Yeah, plus a 'button' in the empty addonlist if possible as users might not see the notice (as the update happens automatically). Would be very sweet usability
Posts: 12,706
Joined: Nov 2003
Reputation:
129
spiff
Team-Kodi Member
Posts: 12,706
you'll get the busy dialog. i can easily spam users with even more useless info if you want that. i don't see the point though, it's not like we toss a dialog apart from the busy every time you list a directory elsewhere. it's pretty damn obvious that the box is doing something.
it will get faster as well. the other part of the bug i discovered is that *all* repos are updated whenever one is outdated...
Posts: 77
Joined: Nov 2012
Reputation:
3
Please tag this for 12.1 @Git as many users experience this problem.