Catalogs can't be removed

[el-pandor]

I have this issue on the phone and the TV. (Pixel 10 Pro and on Google TV Streamer)

If you tap on the bin icon the catalog Removed message appears, but the catalog reappears again soon after. Rebooting doesn't remove the catalog either.

As an example here I'm trying to delete "New K-Dramas" but as you can see in the second screenshot, it's not deleted.

[ProdigyV21]

Fixed and will ship in v1.9.8.

What was wrong

The persistence layer was correct — deleting a catalog added it to a hidden set, and the real home load respected that set. But HomeViewModel.loadHomeData() builds an "early skeleton" of loading rows before calling the real load, and that skeleton was using the unfiltered default catalog list. So on every cold load (and every time the home screen re-entered from another screen with categories.isEmpty()), deleted catalogs reappeared as loading skeletons for 1-3 seconds until the real filtered list replaced them. On slow networks the flash lasted long enough that users thought the delete never took effect — exactly what you reported, screenshots included.

The fix

Landed in #125 (merged to main). The early skeleton now reads the hidden-preinstalled set via the existing CatalogRepository.getHiddenPreinstalledCatalogIdsForActiveProfile() and filters the default catalog list before building the skeleton. Same filter logic that was already applied at every other call site — this was just the one layer that bypassed it.

Wrapped in runCatching so a DataStore read failure falls back to the old behavior rather than breaking the home load.

Testing

Please verify on v1.9.8:

1. Delete a preinstalled catalog (e.g. "Trending in Anime" or "New K-Dramas" as in your screenshots).
2. Kill the app.
3. Relaunch and go to Home.
4. Verify the deleted catalog does not flash into the loading skeleton at any point.
5. Navigate away from Home and back → verify no flash.

If it still reappears after 1.9.8, please open a new issue with which catalog you deleted and whether it reappears on cold start, hot return, or both.

Closing as resolved. Thanks for the detailed report with screenshots — that made this much easier to diagnose.