Swiftly is a Jellyfin client for iPhone. If something is not working, the answer is probably below — and if it isn't, write to me.
Swiftly needs your own Jellyfin server, version 10.8 or
newer, reachable over a secure https address. It brings no films
of its own.
Check the address without a scheme first — type tv.example.com,
not https://tv.example.com. Swiftly adds it.
If the server sits in your home network, use its local address while you are at home. From outside, it needs to be reachable from the internet.
iOS blocks unencrypted connections to servers outside your home network. A
server that is only reachable over http from the internet cannot be
used. Set up https on the server — Let's Encrypt is free, and most
reverse proxies do it in a few lines.
Jellyfin only publishes accounts that are not hidden from login screens. In Jellyfin go to Administration → Users → your account and allow it to be shown. Signing in by typing the name works either way.
Swiftly names the track that caused it, right under the title. Most often it is a subtitle format the server decided to burn into the picture.
Check that Always Direct Play is on under Profile → Playback, and that your account has no bitrate limit set in Jellyfin itself — a server-side limit overrides the app.
Tap the small icon at the top right while the controls are visible. If the button is dimmed, the film is still loading — give it a moment.
It shouldn't. Check under iOS Settings → Swiftly that background activity is allowed, and that Low Power Mode is off — it suspends background playback.
Profile → Sign out. Swiftly then asks for an address again and tells your old server to invalidate the session.
Write to kontakt@paulherter.de. It helps if you mention your Jellyfin version, your iOS version, and what you were doing when it went wrong.