Using deep links to infuse library items doesn’t work when using a Jellyfin library in direct mode (client: Infuse 8.5.5, macOS 27.0; server: Jellyfin 12.1). However, it works when using the same library in library mode instead.
When opening an item using infuse://movie/{tmdb_id}, it currently brings up a placeholder page showing TMDB’s default metadata rather than the custom details from my Jellyfin library. The same issue occurs with the playback link infuse://movie/{tmdb_id}?play, which loops back to the same page and displays “failed to open input stream” when attempting to trigger playback by clicking the movie cover.
Here is a short demonstration featuring the movie “The Saint,” which appears properly in Infuse’s search, confirming that it is indeed in the library:
Note that I reproduced this with all movies and series in my library. I couldn’t find a single working one.
@james I ran a few more tests and was able to narrow this down to direct-mode versus library-mode. Happily, the issue mentioned above doesn’t happen at all in library-mode! Since direct-mode is the recommended setup and turned on by default, I would love it if you could confirm this bug and let us know if a fix might be planned for an upcoming release. Thanks so much!
These deep links are designed to work with the Infuse Library.
If you don’t have an item in the library or are using direct mode, you would see a placeholder page which includes a Search button instead of Play.
Since it’s fairly common to have more than one server connected to Infuse selecting the Search option would allow you to search on any of the direct mode sources you have added in Infuse.
Sorry, my bad, I guess I misunderstood what “infuse library item” meant in the documentation. That makes sense.
Wouldn’t it be great to support this for direct-mode as well, as long as the TMDB ID is unique across the connected servers? In those situations, having to open the placeholder page and click the search button feels a bit cumbersome, to be honest.
If a title isn’t unique across connected servers (i.e., the title is present on at least two connected servers), we can simply stick with the current, reliable approach: opening the search page.
We could also easily handle this with query parameters, something like:
This leaves the choice of the preferred server up to the user, which I believe would work great since deep links are likely only used by more advanced users anyway.