Skip to content

Jellyfin builds: compare on the catalog's web_version (#124) - #125

Merged
PatrickSt1991 merged 2 commits into
mainfrom
jellyfin-web-version-124
Nov 16, 2026
Merged

PatrickSt1991 merged 2 commits into
mainfrom
jellyfin-web-version-124

Conversation

@PatrickSt1991

Copy link
Copy Markdown
Contributor

Closes #124.

Every build in the Jellyfin family declares version 0.1.0, so TV-Store never offered an update for one. The catalog now carries the jellyfin-web version of each build as web_version (Apps2Samsung/Apps2Samsung#1117, already in the live snapshot), and TV-Store shows and compares that.

What changes

  1. Carry the field. web_version goes onto the variant next to version. Anything that is not a plain version is ignored.
  2. Write it down at install. A new record per package id in localStorage (a2s.tvstore.webversions): the app, the file and its web_version.
  3. Compare on it. state() and the pinned card compare the catalog's web_version with the one written down. Higher in the catalog is an update and joins Update all. Only the version counts, not the build date.
  4. Not known. A Jellyfin with nothing written down reads as "version not known" with the catalog's version next to it. No update, not in Update all, not in the update count. The sheet and the On the TV panel say why, and that an install from here replaces a copy built on a PC with a server, sign-in or plugins.
  5. Show it. Cards, the sheet, the variant list, the install screens and the store in a browser show the web_version where they showed v0.1.0.

Two things beyond the five points

  • Which app claims the package. The Jellyfin apps (Jellyfin, legacy builds, AVPlay) share AprZAARz4r and all say 0.1.0, so the first one in the catalog claimed the package whichever was installed. The app whose build was written down claims it now; without that, a legacy or AVPlay build installed from TV-Store would be compared as a build of "Jellyfin".
  • A record leaves with its package. When the TV no longer lists the package, its record is dropped, so a Jellyfin that comes back under that id from a phone or PC is not taken for the build TV-Store installed.

Behaviour to know

  • A build without a web_version (the 10.8.z legacy builds have none) and a catalog from before the field compare as before.
  • Jellyfin-master says 13.0.0 until 13 is released, so it shows no update until then.
  • TV-Store cannot see a phone or PC installing over a Jellyfin that TV-Store installed without removing it first. The record then still names the older version, and an update is offered. The same holds for the remembered variant today.
  • The README says "before 0.3.33" for installs that have nothing written down; adjust if the release gets another number.

Tested

  • test/web-version.test.js (new) runs the real app.js in a vm with a stand-in for the DOM, the platform and the service: not installed, not known, update and Update all, same version, the claim, the record written at install and dropped with its package, a catalog without the field. It draws the On the TV page and the sheet and reads what they say. It fails on main.
  • scripts/run-tests.sh: all tests pass.
  • Not tested on a TV.

Every build in the Jellyfin family declares version 0.1.0 in its config.xml,
the wrapper's own. The TV reports 0.1.0, the catalog says 0.1.0, and TV-Store
never offered an update. The catalog now gives the jellyfin-web version inside
each build as web_version (Apps2Samsung#1117), and TV-Store uses it.

- The variant carries web_version next to version; cards, the sheet, the
  install screens and the store in a browser show it instead of 0.1.0.
- An install from TV-Store writes it down per package id, with the app and the
  file it belongs to (localStorage, a2s.tvstore.webversions).
- state() and the pinned card compare the catalog's web_version with the one
  written down. Higher in the catalog is an update, and it joins Update all.
- Nothing written down (installed from a phone or PC, or before this): the
  version reads as not known with the catalog's next to it, no update is
  offered and it stays out of Update all. The sheet and the On the TV panel
  say why, and that an install from here replaces a copy built on a PC.
- The Jellyfin apps share one package id and one version, so the first in the
  catalog claimed the package whichever was installed. The app whose build
  was written down claims it now.
- A record leaves with its package, so what comes back under that id from a
  phone or PC is not taken for the build TV-Store installed.

A build without a web_version, and a catalog from before the field, compare
as before.

test/web-version.test.js runs the real page script in a vm with a stand-in
for the DOM, the platform and the service.
@PatrickSt1991
PatrickSt1991 merged commit 2adf77e into main Nov 16, 2026
1 check passed
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.

Jellyfin builds: compare on the catalog's web_version, they all declare 0.1.0

1 participant