← Back to Blog

Stremio iOS Opens the First Duplicate Addon: Workarounds

On iOS and iPadOS, avoid using the addon tabs when two installed instances have exactly the same displayed name. Until the selector is fixed, manually scroll to the second instance’s stream group; for a cleaner temporary workaround, keep only the configuration you currently need installed.

There is no confirmed permanent user-side fix in the report. Updating Stremio when a newer build becomes available is safer than resetting the app or repeatedly reinstalling the same addon.

What is happening

The reported problem appears when the same addon is installed more than once with different configurations or filters, but both installations display the same name. Tapping the second identically named tab in the stream-selection screen jumps to the first instance’s results instead.

The report concerned Stremio 2.0.8 b23 on an iPad Air running iPadOS 26.6.1. It described the problem as specific to the iOS implementation and noted that the same duplicate-addon selection worked on Android and Windows. Those details come from one report and do not establish that every iPhone, iPad, or Stremio build is affected.

Although the issue was filed under the iOS, iPadOS, and macOS Native Beta platform category, the report specifically characterized it as an iOS-only issue. There is not enough evidence to say that the macOS native app has the same behavior.

Likely cause

The reporter’s observations suggest that the iOS stream selector may be identifying an addon tab by its displayed name rather than by a unique identifier for that particular installation. If both configured instances have the same name, selecting either tab can resolve to the first matching instance.

That explanation is plausible but has not been confirmed by a maintainer in the supplied report. The problem is more likely to be in Stremio’s iOS selection interface than in the addon itself if:

  • Both addon instances return their expected streams.
  • Their results appear as separate groups in the full list.
  • Only the shortcut tab selects the wrong group.
  • The duplicate instances work correctly on another supported platform.

Community addons are independently operated, so their availability, labels, and configuration options are controlled by their developers. However, an iOS tab that consistently jumps to the first same-name instance is a separate client-interface symptom.

Troubleshooting in the safest order

1. Confirm that this is the duplicate-name bug

Open the stream list for a movie or episode that should produce results from both configurations. Check whether:

  1. Two addon tabs have exactly the same visible name.
  2. The full stream list contains results associated with both configurations.
  3. Tapping the second tab moves to the first group.
  4. Manually scrolling still lets you reach the second group.

If the second configuration returns no streams anywhere in the list, this may instead be an addon configuration, availability, or connectivity problem. The duplicate-tab workaround will not restore results that the addon never returned.

2. Manually scroll to the second result group

This is the least disruptive workaround documented by the report. Ignore the duplicate tabs and scroll through the complete stream list until you reach the results produced by the second configuration.

Use details in the stream entries—such as the filters or qualities you intentionally configured—to verify that you reached the correct group. Do not assume the tab highlight is accurate after it has jumped to the first instance.

3. Reduce ambiguity if the addon supports distinct labels

Check the addon’s own configuration page for an option to assign a distinct display name, profile label, or configuration label. For example, labels indicating different filters would let Stremio distinguish the tabs visually and may avoid a name-based collision.

Not every addon offers renaming, and Stremio does not necessarily provide a separate control for renaming an installed community addon. Do not change unrelated filters simply to force a different name. If there is no supported label option, move to the next workaround.

4. Temporarily keep only one configured instance

If manual scrolling is impractical, remove one duplicate and retain the configuration needed most often. Before uninstalling anything, record the settings required to recreate both configurations, especially if the addon does not provide an export function.

Addon changes can affect other devices using the same Stremio account, so verify where each configuration is needed before removing it. When you need the other filter set, reconfigure or reinstall the addon through its normal setup flow. This is more cumbersome than scrolling, but it eliminates the ambiguous pair of same-name tabs.

Only configure community addons you trust, and use them with content and services you are authorized to access.

5. Use an unaffected device as a temporary fallback

The original reporter said duplicate instances could be selected correctly on Android and Windows. If you already use Stremio on one of those devices, selecting the desired instance there may be a practical temporary fallback.

This is user-reported behavior, not a guarantee for every app release or device. It also does not repair the iOS selector.

6. Install Stremio updates through the same release channel

Because the affected build was identified as a native beta, check the distribution channel through which you installed it for a newer build. Review its release notes where available, then test the two duplicate tabs again after updating.

Avoid deleting app data, resetting the device, or repeatedly reinstalling Stremio as an early step. The reported trigger is two identically named addon instances, so clearing unrelated playback data is unlikely to address the apparent selection collision and may remove useful local state.

What worked for affected users

The report documents one reliable way to reach the desired results: manually scrolling past the first addon’s streams to the second addon’s group. It also reports that direct selection behaved correctly on Android and Windows.

No maintainer-confirmed patch, hidden iOS setting, or verified cache-clearing fix was included in the available evidence. Temporarily removing one duplicate is therefore a practical fallback based on eliminating the trigger, not a confirmed software fix.

If you need to report or update the bug

Include precise diagnostic information so maintainers can distinguish this issue from an addon failing to return results:

  • Stremio app version and build number.
  • iPhone or iPad model.
  • iOS or iPadOS version.
  • Whether both tabs have exactly the same displayed name.
  • Whether both result groups appear when you scroll manually.
  • Whether tapping the second tab always jumps to the first group.
  • Whether the behavior remains after installing a newer build.
  • A short screen recording that avoids exposing account details or private configuration data.

If possible, reproduce the issue with two harmless configurations of the same addon. Do not publish credentials, access tokens, account identifiers, or private service details in screenshots or logs.

Quick answers

Will clearing the cache fix it? There is no evidence that cache clearing fixes this specific duplicate-name selection problem. Manual scrolling or avoiding simultaneous same-name instances is safer.

Is the second addon installation broken? Not necessarily. If its streams appear farther down the list, the installation is returning results and the problem is likely limited to tab navigation.

Can the tabs be renamed in Stremio? The available report does not identify a Stremio setting for this. Some addons may offer their own label option, but that depends on the independently operated addon.

Does this affect macOS too? The issue category mentions the macOS Native Beta, but the report calls the bug iOS-only. Treat macOS impact as unconfirmed unless you can reproduce it there.

What is the best temporary solution? Manually scroll to the second group if you need both configurations. If that is too inconvenient, record your settings and keep only one instance installed until an updated build resolves the selector behavior.

Last reviewed: September 19, 2026