Version 1.6.0 of Jellyfin for iOS has been published to the App Store! π
Jellyfin for iOS 1.6.0 | Jellyfin
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.
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.
I'm sure a lot of people are curious why it has been so long since the last app release. There are a few reasons for this. First, we have not released any breaking changes to Jellyfin that required an app update. Perhaps most significantly the toolkit we use to build the app made some changes that essentially prevented my continued development of the app without access to a modern Mac. However, thanks to the generosity of contributors to Jellyfin's open collective, I was able to expense the majority of the cost to purchase a new Mac Mini for development. Finally, the build system provided by the toolkit we were using had been discontinued. We have now replaced that build system with a fully automated GitHub Action workflow that builds and publishes the app to TestFlight on demand.
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!
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 π
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
