Skip to content

Sign in to Jellyfin from Settings and onboarding - #35

Merged
XDanfr merged 2 commits into
feat/jellyfinfrom
feat/jellyfin-sign-in
Nov 16, 2026
Merged

XDanfr merged 2 commits into
feat/jellyfinfrom
feat/jellyfin-sign-in

Conversation

@XDanfr

@XDanfr XDanfr commented Nov 16, 2026

Copy link
Copy Markdown
Owner

Signing a profile in to Jellyfin, from Settings and from onboarding. Browsing the server's library comes next.

Settings › Jellyfin

  • Find a server: servers on the local network are listed as they answer, or you type an address. Jellyfin 12+ is required, with clear errors when a server is unreachable, isn't Jellyfin or is too old.
  • Sign in: Quick Connect shows a six-digit code to approve from another signed-in device. If Quick Connect is off, or you prefer, you can use a username and password.
  • Choose how the profile uses it: "Jellyfin only" or "Jellyfin and this device" (Hybrid).
  • Once signed in: the dialog shows the server and user, the library mode (Jellyfin only, both, or this device only), sync status with the title count, Sync now, and Sign out. Signing out ends the server session and returns the profile to local only.

Onboarding

  • New installs start with "Where's your media?": on this device, on a Jellyfin server, or both.
  • Jellyfin-only setups sign in and finish without ever being asked for video access. "Both" signs in and then continues to the local scan.
  • Installs that already have video access skip the question.

Fixes found by testing on a phone

  • Discovery: the SDK only broadcasts to 255.255.255.255, which many Android devices drop. A small discovery helper also sends to each interface's own broadcast address, so the server is found on the phone as well as on the Mac.
  • Android 17 local network access: ACCESS_LOCAL_NETWORK is needed to reach any LAN server. The dialog asks for it first and offers to enter an address instead. When the permission is granted, the phone companion server restarts too.
  • Cleartext HTTP: home servers are usually plain HTTP by IP, so the TV app now has a network security config permitting cleartext, like the phone companion. Aperture's own services are all HTTPS.
  • Crash on the first network call: the SDK logs through kotlin-logging, which picks its SLF4J backend on Android and crashed with NoClassDefFoundError: org/slf4j/LoggerFactory. slf4j-api is now bundled on Android; with no binding, it logs nowhere. The earlier R8 -dontwarn had hidden this warning instead of fixing it.

Also

  • TvTextField: a single-line text field a remote can leave with Down and Up, or with the keyboard's action key.
  • JellyfinLiveTest adds a Quick Connect test: it starts a code, approves it from a second signed-in client and waits for the sign-in. Like the other live test, it only runs with APERTURE_JELLYFIN_* set.

Testing

  • On a phone running the TV build, mostly with the D-pad:
    • Settings › Jellyfin: granted local network access, the server was discovered, Quick Connect was approved as a non-admin user, then "Jellyfin only" was chosen. The dialog then showed the server, the mode and "Up to date" with the indexed title count.
    • Fresh install: chose "On a Jellyfin server", signed in with Quick Connect approved as an admin user, and onboarding finished with no video-access prompt.
  • Live tests against a real Jellyfin 12 server pass: sync, and Quick Connect as a non-admin user, including discovery from the Mac.
  • All JVM tests (56, with the 2 live tests skipped without server settings) and the desktop tests pass.
  • Known gap: Home still shows only local media; Jellyfin browsing is the next PR.

Settings › Jellyfin finds servers on the local network or takes an
address, signs in with Quick Connect (or a password when Quick Connect is
off or preferred), then asks whether the profile uses Jellyfin only or
Jellyfin alongside local files. Once signed in it shows the library mode,
sync status and title count, with Sync now and Sign out.

- Discovery also sends to each interface's broadcast address; many Android
  devices drop the SDK's 255.255.255.255 broadcast.
- Android 17 needs ACCESS_LOCAL_NETWORK to reach a LAN server, so the
  dialog asks for it first (and restarts the phone companion when granted).
- The TV app allows cleartext HTTP, since home servers are usually
  reached by IP over plain HTTP.
- slf4j-api is bundled on Android: kotlin-logging, used by the SDK, picks
  its SLF4J backend and crashed on the first network call without it.
- TvTextField: a text field a remote can leave with Down/Up.
New installs start with "Where's your media?": on this device, on a
Jellyfin server, or both. Jellyfin-only setups sign in and finish without
ever being asked for video access; "Both" signs in and then continues to
the local scan. Installs that already have video access skip the question.
Copilot AI balanced review requested due to automatic review settings November 16, 2026 04:19
@XDanfr
XDanfr merged commit 12af3b8 into feat/jellyfin Nov 16, 2026
5 checks passed

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants