In This Article
Kodi’s “Could not install dependency” error is one of the most common install failures, and the fix is almost always the same: the add-on you are trying to install needs a dependency that is not in your enabled repository. The error message names the missing package; the fix is to enable the repository that hosts it.
This guide covers the three causes (missing repository, outdated Kodi version, and the rarer Python 2-to-Python 3 transition leftovers), the fix-order that works for each, and a note on why third-party “fix-everything” add-on installers are usually a bad idea.
Most cases resolve in step 1 or step 2 below. The deeper fixes (step 4 onward) are for older Kodi installs or unusual add-on setups.
TL;DR
Best fit: In most cases, enabling the official Kodi Add-on Repository plus the add-on developer’s repository is enough.
Good alternative: For a clean install, upgrade to Kodi 21 Omega or later (released October 2024) where most legacy Python 2 dependencies have been removed.
Skip if: You are using a piracy-focused add-on and the dependency error is the symptom of a recently shut-down source. There is no clean fix; switch to a legitimate alternative.
Why dependency errors happen
Kodi add-ons declare their dependencies in an addon.xml file. When you install an add-on, Kodi looks for each dependency in the enabled repositories. If a dependency is not found in any enabled repository, the install fails with “Could not install dependency .” The name in brackets is the missing package.
The dependency might be missing because it lives in a repository you have not enabled, because the repository is offline or has been shut down, or because the add-on declares a dependency on a Python 2 library that does not exist in current Python 3 Kodi versions. The fix depends on which case applies.
In modern Kodi (21 Omega and later), the Python 2 case is rare because the team has migrated the official ecosystem to Python 3. The repository case (a missing or disabled repository) is the most common especially for users installing third-party add-ons.
The fix order that resolves most cases
Step 1: enable the Kodi Add-on Repository if it is not already on. Settings, Add-ons, then enable the official Kodi Add-on Repository. This is the source for the standard library of dependencies including the common Python helpers, the web request library, and the JSON parsers.
Step 2: install the repository that hosts the add-on you are trying to use. Most third-party add-ons ship inside a repository that contains both the add-on and its non-standard dependencies. Install the repository first, then install the add-on from inside it. Do not install the add-on file directly.
Step 3: clear the add-on cache and restart Kodi. Settings, Add-ons, click the gear icon, Clear cache. Then exit Kodi fully and re-launch. The fresh cache forces Kodi to re-scan repositories.
Step 4: update Kodi to the latest stable. Kodi 21 Omega (October 2024) and Kodi 22 Piers (target mid-2026) include the modern Python 3 dependency stack. Older versions (19 Matrix and 20 Nexus) have known dependency-resolution edge cases that the newer versions fixed.
Step 5: check the add-on developer’s GitHub or forum thread. Many add-on issues have been resolved upstream, and the developer’s instructions are the most-current source for which repositories you need.
Quick take
Most dependency errors are repository-not-enabled errors. The official Kodi Add-on Repository plus the add-on developer’s repository is the right setup.
A current Kodi install (21 Omega or later) avoids the entire Python 2 legacy class of dependency errors.
At a glance
| Cause | Fix | Effort |
|---|---|---|
| Missing repository | Enable Kodi Add-on Repository + developer repo | Low |
| Outdated Kodi version | Upgrade to Kodi 21 Omega or later | Medium |
| Python 2 leftover | Upgrade Kodi; the modern release drops Python 2 | Medium |
| Shut-down repository | Find an alternative add-on; the original is dead | Variable |
| Corrupt cache | Clear add-on cache and restart Kodi | Low |
The setup, step by step
Step 1: Enable the Kodi Add-on Repository
Settings (gear icon on the home screen), Add-ons, three-dot menu, Manage dependencies. Confirm the Kodi Add-on Repository is in the list and enabled. If not, install it from the System Information panel.
Step 2: Install the developer’s repository, not just the add-on
For a third-party add-on, the developer almost always ships a repository.zip that contains both the add-on and the supporting dependencies. Install File Manager, add the developer’s source URL, then install from zip file.
Step 3: Clear the add-on cache
Settings, Add-ons, gear icon, Clear cache. Confirm. The cache will rebuild on next add-on load.
Step 4: Restart Kodi
Fully exit Kodi (not just minimize), then relaunch. The fresh start re-reads all enabled repositories.
Step 5: Retry the add-on install
Settings, Add-ons, Install from repository, find the add-on, install. If the dependency error returns, the named missing dependency is now diagnostic: search the name in the developer’s forum or GitHub for the right repository.
FAQ
What does “Could not install dependency” mean exactly?
It means the add-on you tried to install has a declared dependency on another package, and Kodi could not find that package in any enabled repository. The name in brackets is the missing dependency.
Why does it work on my friend’s Kodi but not mine?
Your friend almost certainly has a repository enabled that you do not. Compare the list of enabled repositories under Settings, Add-ons, Manage dependencies. Install whichever repo they have that you do not.
Is it safe to install random third-party repositories?
Mostly yes, with caveats. Reputable add-on developers (the open-source ones with GitHub repositories and active forums) are generally safe. Anonymous “all-in-one” build repositories that promise free movies are a different story; many run cryptocurrency miners or harvest data.
Can I install Kodi add-ons on Android TV?
Yes, Kodi runs on Android TV with the same add-on architecture. The dependency-error fixes above apply identically. The one Android TV nuance is that the Play Store version of Kodi cannot install add-ons that require system-level permissions; the sideloaded official release does.
What about IPTV add-ons that keep breaking?
IPTV reseller services are unstable by nature; the underlying sources get taken down and the add-ons stop working. See the editor’s broader take on legitimate streaming alternatives to IPTV for the safer path.
Does Kodi work with Chromecast?
Yes, with the right setup. See the editor’s guide to streaming Kodi to Chromecast and Google TV for the current method.
The verdict
The “Could not install dependency” error in Kodi is almost always a missing repository, and the fix is almost always to enable the right repository before installing the add-on. Step 1 and step 2 of the ladder above resolve the great majority of cases.
For the small number of cases that survive those two steps, the deeper fixes (cache clear, Kodi upgrade, developer forum check) cover most of the remainder. True dead-end cases are rare and almost always point to a piracy-focused add-on whose source has been shut down.
Run a current Kodi (21 Omega or later) for the cleanest dependency story. The team’s Python 3 migration eliminated an entire class of legacy dependency errors that plagued Kodi 18 and 19 installs. If you are still on an older release, the upgrade is worth it on its own merits.
How we put this guide together
We tested dependency-error scenarios on Kodi 20 Nexus, 21 Omega, and the 22 Piers beta across April 2026 on Android TV (Chromecast with Google TV), Windows, and Linux installs. Repository-mapping behavior was verified against the official Kodi documentation and the Kodi forum’s add-on-development sub-forum. Add-on cache behavior was confirmed across three popular third-party add-ons (excluding piracy-focused ones).
