A busy one. Four reported problems fixed, and three of them turned out to be
bigger than the report suggested.
BingeCat catalogs never appeared (#24)
Reproduced with the addon installed on a real account. The manifest was being
read fine — the problem was four separate things stacked on top of each other:
- One addon was taking every slot. The app has a shared budget for how many
catalogs it remembers across all addons, and it was handing them out
first-come-first-served. Xperience alone declares 605 catalogs and filled
the entire budget by itself, so every addon loaded after it got zero. On
the test TV, every catalog row on Home was Xperience — AIOStreams and Akashi
TV were invisible too, and nobody had noticed. Each addon now gets a fair
share, and unused slots pass along to the others. - Wrong name. The addon's name was read from the first
namefield found
anywhere in the manifest, which in a Stremio manifest can be inside
catalogs[]. BingeCat declares a catalog calledsearch, so the whole addon
showed up as "search". - The Settings catalog list was too small to hold everything, so the last
addon's entries fell off — meaning they couldn't even be switched on by hand. - A regression introduced in 1.0.27: with the new profile picker, confirming
the same profile you were already on never restarted the interrupted sync,
so the account never finished syncing that session and a freshly added addon
never arrived.
Measured after: BingeCat contributes 21 catalogs, 17 of them listed in Settings
under the right name. They still won't appear on Home by themselves — the Home
row limit and your saved order decide that — but now they can be chosen.
Collections split into separate Home rows (#18)
Third attempt at this one, and this time the rule was never the problem — the
timing was.
The check that decides "this catalog belongs to a collection, don't give it its
own row" only ran when the account's collections arrived. Measured on an LG:
collections arrive around 2 s, and the addon manifests are only read at
13 s. A collection source from the account arrives with an addon id and no
URL, and the URL only comes from the manifest — so at 2 s nothing can possibly
match, and nothing ever ran the check again afterwards. The v1.0.11 fix was
correct and simply never fired, which is why it reproduced with Ultra Max as
well as Xperience.
The check now also runs at the end of the discovery cycle, after the manifests
are read and before the home cache is written, so the next launch starts already
grouped.
Diagnostics stay in the build, because this issue has now been misdiagnosed
twice: one line reports how many rows were folded into collections, how many
collections exist, and how many collection sources still have no resolved URL.
Those three numbers separate the three different causes that produce this same
symptom. Addon URLs are redacted in that output.
Removing from Continue Watching only took effect after a restart (#22)
The removal itself was already working; the card was the problem. Clearing the
progress erased what the label draws — the bar, the episode, the minutes left —
but left the card sitting in the row until the catalog was rebuilt.
Rows are windows into one shared list of items, so the obvious fix (compacting
that list) would have been the wrong one: it would shift every following row.
The item is now dropped from its own row's window only. Verified on the TV with
the real gesture: the row counter went from 1/8 to 1/7 and the card disappeared
immediately.
Portuguese text in the English interface
Reported on an LG OLED48A2PUA: Home showing "Programa de TV" and "Filme" with
everything else in English. The cause wasn't a missing translation. The packaged
catalog stores that label already in Portuguese, and the genre translator that
processes it only knows English→Portuguese — so with English selected it passed
the label straight through untouched. Genres were right; only the type label was
never translated by anyone.
Also fixed: the disk cache stores text that is already composed, so a home
written in one language was read back in the other. The cache now records which
language it was written in.
Three genuinely missing translations were added: "Details", "Artwork" and the
"change the value" hint in Settings.
Packages
- LG webOS 4.x (ARM) —
space.nuvio.native.legacy_1.0.28_arm.ipk - Samsung Tizen —
NuvioTV-1.0.28-tizen.wgt(sign it with your own Samsung
certificate; seetools/tizen-wgt.sh)
Neither package carries personal credentials — the packaging script excludes the
key files and verifies the exclusion after building.
None of these issues are being closed on this release. A fix that works on my TV
isn't proof it works on yours, so they stay open until the people who reported
them can confirm.