v0.21.14 - watched items not removed from feed unless "hide watched" toggle cycled

[perseusbiscuitsakira]

• I am using the latest version - x.xx.x
• I checked, but didn't find any duplicates (open OR closed) of this issue in the repo.
• I have read the contribution guidelines given at https://github.com/TeamNewPipe/NewPipe/blob/HEAD/.github/CONTRIBUTING.md.
• This issue contains only one bug. I will open one issue for every bug report I want to file.

Steps to reproduce the bug

1. Go to 'What's New' i.e. Feeds
2. Watch a video or 'Mark as watched' while the having 'Show watched items' set to off (slashed eye)

Actual behavior

Videos will not be removed from feed unless you refresh feed or toggle 'Show watched items' (from 'slashed eye' to 'normal eye' and back to 'slashed eye')

Expected behavior

In v0.21.13 and previous releases, Videos would be removed as soon as watched or 'Marked as watched' while the 'Show watched items' setting was set to off (slashed eye), without the need to cycle the setting

Device info

• Device model: Amazon Fire HD 10 Plus tablet

[litetex]

Videos will not be removed from feed unless Watched(Eye Icon) is cycled

Correction: Videos will not be removed until the feed is refreshed.

[muuusso]

Experiencing the same here. Definitely not a deal breaker, but an annoying behavior. Hopeful you will restore it quickly.

[Stypox]

@litetex commit 676bc02 contained in #7050 broke updates in the feed. Now marking an item as watched (or actually watching it) does not update its visual state until the feed items are reloaded in some way (e.g. by pressing the eye two times, or by reloading the feed, or ...).

[litetex]

@Stypox
Keep in mind that this was a fix for #6686 (comment) / #6686 (comment).

Fun Fact: It also doesn't work in any other list → This is a new feature in my opinion
I think something like broadcasting an event (and not using the database as a notification platform because a database is a database and not a message broker) when a video is watched and reacting to it would be good solution (maybe something like notifyDataChanged).