Identify what is missing
When a Jellyfin collection appears elsewhere but not in Swiftfin, name the actual library type and user. Movies, music, photos and a playlist are different kinds of server content. A client supporting one does not establish that it presents all the others through the same interface.
Keep one known item as the comparison and inspect it through the server’s ordinary interface with the same viewer account. An administrator seeing the collection is a different permission test. Record whether the item is absent from the server, hidden for the user or simply unavailable in the chosen client.
Use the project’s current library-support table
Swiftfin maintains a dedicated support table. It lists supported video-library types and distinguishes unsupported music, photo, book and playlist cases, with video-only limits for collections. Check the current table against the installed build before treating the absence as a scan failure.
Do not change a music or photo library’s content type simply to make it resemble a movie library. A classification change affects metadata and presentation without implementing a missing client viewer. Keep the server’s accurate organization intact while deciding which supported client fits the actual task.
Compare a known supported video item
Open an ordinary authorized movie or episode that the same account can access. Confirm it appears and plays in Swiftfin. This gives a controlled client connection result while preserving the missing-type question. A supported video working is not evidence that a different media type should also appear.
If even the known supported item is absent, inspect account access and the connected server identity next. Keep the application build and server version in the notes. Reinstalling the server or deleting the media database before checking those facts is a much broader change than the evidence supports.
Choose the appropriate client without mislabelling the source
If the content type is outside the client’s documented support, use a client that actually supports that library and source. Keep the same authorized account and verify its access there. Do not promise that a future feature or a development branch is available in the current App Store build.
The expected outcome is a known support boundary or a narrower access problem. It does not create missing media, migrate a library or claim that the server’s collection has been independently audited. Retain the type, account and tested client together so later advice addresses the real distinction.
Questions answered
Should I change a music library into Movies to make it appear?
No. Preserve the accurate server content type and choose a client that supports the actual task.
What comparison is useful before blaming the server scan?
Check the same user and item through the server interface, then test a known supported video in Swiftfin.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.