Skip to content

fix addon-browser updater delay#8

Open
axbmcuser wants to merge 1 commit into
avdvplus:aml-4.9-21.3-cpmfrom
axbmcuser:aml-4.9-21.3-cpm-R9-addonbrowser-updater
Open

fix addon-browser updater delay#8
axbmcuser wants to merge 1 commit into
avdvplus:aml-4.9-21.3-cpmfrom
axbmcuser:aml-4.9-21.3-cpm-R9-addonbrowser-updater

Conversation

@axbmcuser

@axbmcuser axbmcuser commented May 16, 2026

Copy link
Copy Markdown

Hi :-)

compared to the other PRs, this one is not that important, but still an imho highly recommended mini-workaround for any enthusiast build or any build in general:

Issue:

  • The Kodi add-on updater seemingly has some sort of mechanism which delayes the point in time when clearly available new versions are shown, in a from my pov/testing inconsistant/weird way, which feels random and unpredictable to the end user. I think it's possible that there is a bug involved.
  • Even when pressing "check for updates", new versions, which are definitely long available in the repo(s), are just not presented to the user until some hour(s)? later
  • This leads to users wondering about an expected new version and them "trying again" a few hours later or even waiting overnight, because it's not communicated to them in any way why an available version would not be shown despite intentionally pressing the "Check for updates" button manually multiple times

This workaround fixes the issue.
New updates are always instantly shown under "Available updates" when the user presses "check for updates".

Maybe have some thoughts yourself if you think this is useful.
I personally think it is and use this workaround for almost a decade or so on all my personal builds and never noticed any downsides.

I mean, all the coding & testing is already time consuming as is.
Having any artificial delay until you can see some Kodi add-on updates seems to be avoidable lost time which could be better spent on other topics in the realm of our project(s). just my 2 cents, of course
:-)

Cheers

@avdvplus

Copy link
Copy Markdown
Owner

This one has not been tackled by CoreELEC or xbmc even though there was some noise about this issue, so not sure there is some background reason why it was not addressed previously?

@axbmcuser

axbmcuser commented May 20, 2026

Copy link
Copy Markdown
Author

Wasn't aware that there has been talk about this issue. Do you remember where i can read about it?

My best guess would be that most ppl (including many devs) just have auto-updates enabled and rarely ever care about super-quick-instant update availability. Some might even never have noticed that this delay exists or at least they might have not attributed the delay to a potential bug within Kodi.
Just some pragmatic guesses.

Besides the additional usual topic of open source:

Having endless evolving lists of often long-standing more crucial topics & bugs & too few developers having the time & interest to tackle an exact particular issue someone else might view as more urgent than another one.
Which all is well understandable in the realm of open source. :-)

In the end, my pov bottom-line:

Since there seemingly are no downsides to the easily revertible workaround which is only a two line //comment, i saw no reason to miss out on the benefits until it may or may not will be adressed officially some day (or years) in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants