Addons: Add Update Addons functionality by mrcanelas · Pull Request #1188 · Stremio/stremio-web

mrcanelas · 2026-04-03T17:31:02Z

Summary

This PR updates installed addons in place using core UpgradeAddon, so addon order is preserved (no uninstall/reinstall flow).

The UX was changed from per-addon update actions to a single “Update all” action in the Addons header (installed view), including a mobile-specific icon button layout.

Related issues

Closes #196

What changed

Added bulk update flow for installed addons:
- Fetch fresh manifest from transportUrl
- Dispatch Ctx -> UpgradeAddon sequentially per addon
- Correlate core events (AddonUpgraded / Error with source AddonUpgraded) per addon
Added batch toast muting during "Update all" to avoid per-addon toast spam
Added protected addon handling:
- Skip addons flagged as protected in list filtering
- Treat core Other / code 5 (Addon is protected) as skipped (not failed)
Improved result reporting:
- Success: {count} addons updated
- Success: All addons up to date when nothing changed and no real failures
- Partial error: simplified per-addon lines (e.g. IMDB Catalogs erro: 404)
Updated mobile UI:
- "Update all" appears between search and filter
- Icon-only button (same shape as filter button), preserving desktop color scheme

Why

Refreshing addon manifests previously required reinstalling addons, which could change addon order and impact result prioritization.
Using UpgradeAddon in place keeps order stable and makes updates safer and faster for users.

How to test

Open Addons (installed tab) with multiple installed addons.
Click Update all on desktop and mobile layouts.
Verify:
- addon order is unchanged after update;
- protected addons are not reported as failures;
- when errors happen, toast shows per-addon simplified lines (e.g. Name erro: 404);
- when all are unchanged/skipped-protected, success message is shown.

…nctionality

…h and dispatch addon manifests

…on container

… addon already update

…optional

tymmesyde · 2026-04-03T17:58:42Z

Hi, can you revert your change where you rewrote the whole component to typescript?
When opening a PR it's best to stay in scope and modify the least amount of stuff

mrcanelas · 2026-04-03T18:02:07Z

I was told that all the code would be migrated to TS in the future, and I thought I would be helping.

tymmesyde · 2026-04-03T18:05:25Z

The components are rewritten when necessary, if we think they need refactoring or if it's easier for type definitions
But newly added components and other files should be written in typescript

… props optional

mrcanelas · 2026-04-03T20:05:15Z

Hi, can you revert your change where you rewrote the whole component to typescript? When opening a PR it's best to stay in scope and modify the least amount of stuff

Done!

kKaskak · 2026-04-05T10:09:14Z

what if we could instead just have one update button on header on the addons page? which would update all addons? wouldnt this be better? I guess some could error out if they are old but we could just show a toast {number} Addons updated or All addons up to date if none changed

mrcanelas · 2026-04-05T12:45:09Z

what if we could instead just have one update button on header on the addons page? which would update all addons? wouldnt this be better? I guess some could error out if they are old but we could just show a toast {number} Addons updated or All addons up to date if none changed

We can do it this way too, just adding one more button instead of one for each add-on. I'll make the changes.

…andling

…andling for addon updates

…ates

mrcanelas · 2026-04-06T12:47:19Z

what if we could instead just have one update button on header on the addons page? which would update all addons? wouldnt this be better? I guess some could error out if they are old but we could just show a toast {number} Addons updated or All addons up to date if none changed

Done!

this means we have the shared logic in core and can be implemented to other apps as well Co-Authored-By: Silas Alves <sialsan@hotmail.com>

Co-Authored-By: Silas Alves <sialsan@hotmail.com>

tymmesyde · 2026-04-08T09:59:14Z

What is the point of this btw? Shouldn't we automatically update the manifests anyway since the server hosting the addon is always running the latest version?

kKaskak · 2026-04-08T10:16:34Z

What is the point of this btw? Shouldn't we automatically update the manifests anyway since the server hosting the addon is always running the latest version?

auto updating is expensive for our intra, this is a better approach IMO; user takes the action himself if necessary; you can update all or per add-on (during testing, setupping your account etc.)

kKaskak · 2026-04-08T10:43:55Z

@mrcanelas i made the core side implementation and wired the dev package please test it 🙏🏼

kKaskak · 2026-04-08T10:44:44Z

update translations
remove default value usage

tymmesyde · 2026-04-08T10:51:39Z

auto updating is expensive for our intra, this is a better approach IMO; user takes the action himself if necessary; you can update all or per add-on (during testing, setupping your account etc.)

is it that different from synchronizing the library? in core we just need to make a request to all the addons and update the old manifests locally, we then synchronize with our API if needed
i don't think the common user know that it could be necessary to update addons and what it does

kKaskak · 2026-04-08T10:59:03Z

auto updating is expensive for our intra, this is a better approach IMO; user takes the action himself if necessary; you can update all or per add-on (during testing, setupping your account etc.)

is it that different from synchronizing the library? in core we just need to make a request to all the addons and update the old manifests locally, we then synchronize with our API if needed i don't think the common user know that it could be necessary to update addons and what it does

ig its a preference to include / exclude manual button

technically it will be only a req to the addons, if all up to date we dont have req to api so its cool

i did the core part so its easy to rewire and do it automatic instead of exposing an action

if @mrcanelas has any reason why he want it to be a Ui button instead of auto update please feel free to share with us

i'm open to discussion on this

only thing im concerned about is that if a dev publishes a new version of the addon which has a bug (removal of a catalog or something similar which does not break the actual manifest; update would fail if it would) and we auto update all users manifests, add-on breaks for everyone. if its manual if a bad release is done users will use the old manifest which will work perfectly fine. and if somebody updates manually only for him the addon breaks and he needs to wait for a fix.

edit: most users wont reconfigure their addons if everything already works, they arent even visiting the addons page, if something breaks for them without reconfiguring this would lead to online consequences, thats why IMO its better to be manual; they dont even know if a new version is released and what it includes, they are happy with their setup. (excluding users who are active to following addon updates that currently need to uninstall / install addon to update which breaks their addon order)

mrcanelas · 2026-04-08T11:25:47Z

if @mrcanelas has any reason why he want it to be a Ui button instead of auto update please feel free to share with us

I believe this button is a great addition. Today, with several custom list add-ons thanks to mdblist, every time a new list is added, the manifest changes, requiring reinstallation or the use of tools like Syncio, Stremio Addon Manager, and others. I think we should have native tools so users don't have to resort to other alternatives, especially simple things like an add-on update button. I don't know how automatic updates work today, if it's a cron job, but it's not instantaneous; when the add-on's manifest changes, it doesn't pass that information to Stremio in real time.

kKaskak · 2026-04-08T11:28:01Z

if @mrcanelas has any reason why he want it to be a Ui button instead of auto update please feel free to share with us

I believe this button is a great addition. Today, with several custom list add-ons thanks to mdblist, every time a new list is added, the manifest changes, requiring reinstallation or the use of tools like Syncio, Stremio Addon Manager, and others. I think we should have native tools so users don't have to resort to other alternatives, especially simple things like an add-on update button. I don't know how automatic updates work today, if it's a cron job, but it's not instantaneous; when the add-on's manifest changes, it doesn't pass that information to Stremio in real time.

Currently we don't have auto addon update of manifests functionality for users. FYI

mrcanelas · 2026-04-08T11:43:12Z

Currently we don't have auto addon update of manifests functionality for users. FYI

That's exactly why I believe this manual 'Update All' feature is so relevant right now. Since there is no automated sync for manifests, users are often stuck with outdated catalogs or broken resource links unless they go through the hassle of reinstalling.

This implementation provides a reliable way for users to fetch the latest manifest.json on demand, solving the prioritization issue (maintaining the addon order) without adding the complexity or the overhead of a full background auto-update system at this stage.

Botsy

@kKaskak @mrcanelas I tested and I honestly think it's a bit confusing why we have the update button if there is no update to an addon. I would suggest we rephrase it a bit into "Check for updates" or something like this. Which will then check if there is an update (and install it ?) and show success message, or show a message that the addon is up-to-date. Is it doable? Otherwise we're showing success messages but doing nothing.

Botsy · 2026-04-08T13:54:37Z

+    const hasUpdatableInstalledAddons = React.useMemo(() => {
+        if (installedAddons.selected === null) {
+            return false;
+        }
+        return installedAddons.catalog.some((addon) =>
+            !addon.manifest?.behaviorHints?.configurationRequired && !addon.flags?.protected
+        );
+    }, [installedAddons.selected, installedAddons.catalog]);


Is there a way we return true only if any of the addons needs to be updated to newer version? Right now we will have this as true for any unprotected addon that doesn't need configuration, even if there is no newer version?

kKaskak · 2026-04-08T14:24:25Z

show success message, or show a message that the addon is up-to-date. Is it doable? Otherwise we're showing success messages but doing nothing.

we are already doing this, no? :D

kKaskak · 2026-04-08T14:25:32Z

I agree we could only show the button when we have an update available; we would check against existing manifest vs the one fetched from the addon @Botsy

megaslav · 2026-04-08T23:01:30Z

I think this should be a "Reinstall" button, instead of an "Update" button.

Sometimes there's no new version of an addon, but it still needs to be reinstalled to reflect changes to catalogs.

AIOMetadata and AIOStreams even include a message after saving the configuration to tell the user if the changes require the addon to be reinstalled in Stremio in order to be able to see those changes.

It's normal to tinker with the configuration during the setup process, and even every now and then when tastes change, a better idea to organize catalogs pop into your mind, a new addon appears and you want to try it out, etc

Many users rely on Cinebye, Stremio Addon Manager, AIOManager and similar tools just to reinstall the addon.

AIOStreams:

AIOMetadata:

mrcanelas · 2026-04-24T01:23:41Z

Updated the wording to better reflect the actual behavior.

"Update all" → "Check for updates"
Per-addon action renamed to better represent that it may refresh even when there is no new version
Adjusted toast messages to distinguish between updated addons and already up-to-date cases

This should avoid the confusion around showing a successful "update" when nothing has actually changed, while keeping the current behavior intact.

mrcanelas added 6 commits April 3, 2026 14:13

refactor(Addon): migrate Addon component to TypeScript and enhance fu…

c3f7ee1

…nctionality

feat(Addons): add update functionality for addons with fresh manifest

ca406e6

feat(Addons): implement updateAddonWithFreshManifest function to fetc…

ba362f3

…h and dispatch addon manifests

style(Addons): update button styles for configure and add update butt…

b501eb0

…on container

feat(ServicesToaster): add success notifications for addon update and…

9ab06a9

… addon already update

refactor(Image): make fallbackSrc, renderFallback, and onError props …

cba7dc6

…optional

mrcanelas added 3 commits April 3, 2026 16:58

refactor(Addon): revert migration Addon component to TypeScript

f28066a

refactor(Addons): change import statement for Addon

db22314

refactor(Image): revert make fallbackSrc, renderFallback, and onError…

1dd60fd

… props optional

kKaskak assigned mrcanelas Apr 5, 2026

kKaskak added this to the v5.0.0-beta.33 milestone Apr 5, 2026

kKaskak added the feature New feature implementation label Apr 5, 2026

mrcanelas added 5 commits April 5, 2026 18:47

refactor(Addon): revert changes in addon component and styles

e1b4152

feat(Addons): implement batch addon update functionality with event h…

16676db

…andling

feat(Addons): enhance bulk update functionality and integrate event h…

68e6517

…andling for addon updates

feat(Addons): improve error handling and messaging for bulk addon upd…

32b0111

…ates

feat(Addons): add mobile update all button for installed addons

0b3be63

kKaskak and others added 2 commits April 8, 2026 12:38

refactor: support logic in core

2673237

this means we have the shared logic in core and can be implemented to other apps as well Co-Authored-By: Silas Alves <sialsan@hotmail.com>

refactor: simplify handing

85198dd

Co-Authored-By: Silas Alves <sialsan@hotmail.com>

chore: use dev package for testing

1a25745

kKaskak changed the title ~~feat(addons): update installed addons without changing order~~ Addons: Add Update Addons functionality Apr 8, 2026

refactor: remove defaultValue from translation keys

4f995ec

mrcanelas mentioned this pull request Apr 8, 2026

Feat: Add localization keys for addon update functionality Stremio/stremio-translations#1027

Open

Botsy reviewed Apr 8, 2026

View reviewed changes

kKaskak removed this from the v5.0.0-beta.33 milestone Apr 13, 2026

kKaskak added refactor Code refactoring or cleanup and removed refactor Code refactoring or cleanup feature New feature implementation labels Apr 22, 2026

refactor: update translation keys for addon update notifications

fa0d000

kKaskak marked this pull request as draft May 6, 2026 19:11

Conversation

mrcanelas commented Apr 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Related issues

What changed

Why

How to test

Uh oh!

tymmesyde commented Apr 3, 2026

Uh oh!

mrcanelas commented Apr 3, 2026

Uh oh!

tymmesyde commented Apr 3, 2026

Uh oh!

mrcanelas commented Apr 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

kKaskak commented Apr 5, 2026

Uh oh!

mrcanelas commented Apr 5, 2026

Uh oh!

mrcanelas commented Apr 6, 2026

Uh oh!

tymmesyde commented Apr 8, 2026

Uh oh!

kKaskak commented Apr 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

kKaskak commented Apr 8, 2026

Uh oh!

kKaskak commented Apr 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

tymmesyde commented Apr 8, 2026

Uh oh!

kKaskak commented Apr 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

mrcanelas commented Apr 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

kKaskak commented Apr 8, 2026

Uh oh!

mrcanelas commented Apr 8, 2026

Uh oh!

Botsy left a comment

Choose a reason for hiding this comment

Uh oh!

Botsy Apr 8, 2026

Choose a reason for hiding this comment

Uh oh!

kKaskak commented Apr 8, 2026

Uh oh!

kKaskak commented Apr 8, 2026

Uh oh!

megaslav commented Apr 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

mrcanelas commented Apr 24, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

mrcanelas commented Apr 3, 2026 •

edited

Loading

mrcanelas commented Apr 3, 2026 •

edited

Loading

kKaskak commented Apr 8, 2026 •

edited

Loading

kKaskak commented Apr 8, 2026 •

edited

Loading

kKaskak commented Apr 8, 2026 •

edited

Loading

mrcanelas commented Apr 8, 2026 •

edited

Loading

megaslav commented Apr 8, 2026 •

edited

Loading