Version 1.6.0 of Jellyfin for iOS has been published to the App Store! 🚀
(jellyfin.org)
from 1hitsong@lemmy.ml to jellyfin@lemmy.ml on 28 Feb 2025 15:37
https://lemmy.ml/post/26568573
from 1hitsong@lemmy.ml to jellyfin@lemmy.ml on 28 Feb 2025 15:37
https://lemmy.ml/post/26568573
This marks the first release of the app since 2022! Read more about the update and obstacles we overcame to make this happen in the blog post.
threaded - newest
That’s great news. I know I’d get bitten by the black screen bug from time to time. It’s interesting to know the app hadn’t been updated in three years: I never noticed 😁
Out of curiosity, why do you use this instead of Swiftfin?
Mostly because I don’t know better? Should I use Swiftfin?
I don’t know either. Swiftfin seemed more actively developed based on releases, but now it’s great to have another active option. I haven’t compared them but I am curious if anyone had.
or Streamyfin 👀
Not being updated since 2022 is surprising. I would expect that an application that relies on network connectivity to do basically everything would break in that time.
It has not worked for me in over a year to the point I’ve had to use other apps like Swiftfin (is also broken, I compiled it myself to fix a few things but never could get my code upstreamed), or SenPlayer or Infuse. SenPlayer works well enough honestly, but I am glad to see active development of the Jellyfin iOS app!
.
You can run both. There might be issues with the metadata going back and forth. Not sure. Haven’t done it myself. There are definitely people doing this out there.
Jellyfin can read nfo files on disk and you can set it to never modify the files, or you could set Jellyfin to keep all of its metadata in its own DB and never put metadata in the same folder with the media files. Either way it’s entirely doable to prevent a metadata loop like you’re describing