While rare, some low-quality scrapers or manual scans can fetch the wrong metadata. For example, they might pull a TV special or a documentary with the same name. The scraper becomes "unsure" of the correct IMDb ID and passes a null value to A4kSubtitles.
You select a movie, the subtitles search begins, and instead of a list of .srt files, you are met with a red error box or a log file entry stating that the IMDb ID is missing. The subtitles fail to download. The stream stops.
In short: The 5 Most Common Causes (And Their Fixes) Let’s move from theory to practice. Here are the specific scenarios that cause this error and the step-by-step solutions. Cause #1: Using a "Generic" Player Without Metadata The Scenario: You are using Kodi’s default "Files" view or a basic video player that does not scrape metadata. You navigate to your hard drive or NAS, click on movie.mkv , and try to fetch subtitles.
However, a notoriously frustrating error has plagued users for years:
Stremio’s internal architecture prioritizes TMDB IDs (The Movie Database) over IMDb IDs. A4kSubtitles for Stremio expects an IMDb ID. If the Stremio stream source (e.g., Torrentio, Juan Carlos) only provides a TMDB ID, no translation occurs.
A4kSubtitles has a safety feature. If an add-on provides no ID and only a title, A4kSubtitles may still try a "fuzzy search" using the title and year. However, if this feature is disabled in settings, you will get the "not provided" error immediately.
The solution always lies upstream. Update your scrapers, clean your file naming, rebuild your Kodi library, and—when all else fails—enable the fallback text search in A4kSubtitles settings.
