"Mark as read on scroll" sometimes doesn't work

[ih8ms]

Sometimes, "Mark as read on scroll" doesn't actually mark articles scrolled past when scrolling in "Unread". Unfortunately, I don't know how to reproduce the issue. It seems kind of random. If I know how to do so, I will add the information.

For me, it works again when exiting the app (forcfully) and starting it again.

Android 16
Capy Reader 2026.07.1212 F-Droid

[jocmp]

Hey @ih8ms - the force-quit detail is a useful since it points at in-memory state rather than anything saved. No need to reproduce it deliberately, just whatever you notice the next time it happens.

A few things that would help confirm next time it happens, before force-quitting:

1. Does pull-to-refresh make it start working again?
2. If not, does switching the filter (e.g. "All" and back to "Unread") fix it?
3. Does simply closing the app fix it, or does it take a full force-quit?
4. When it's stuck, roughly how many unread articles are left in the list? A handful, or hundreds?

[ih8ms]

I just observed the behaviour. I'm in the "Unread" section/folder and marked all items read by scrolling past, then pulled to refresh. Now scroll to read no longer works.

To answer your questions:

1. No, pull-to-refresh did nothing. Arguably, it started the issue (see above)
2. Switching the filter did nothing
3. I exited the app and removed it from recent apps (app switcher), then opened it again, which made it work again.
4. I virtually only use the "Unread" list, which when it fails contains only a handful of articles.

[sillikk]

I have the same issue, only force kill is fixing it. It seems only random items in the list reaming as unread. It happens in long list mainly I would say, with articles from multiple sources, in the "Unread" section.
However, I found two other workarounds: right-clicking an article and selecting "mark as read above" works correctly, all articles above which didn't toggle the read status are now read. And "Mark all as read" button, or by pulling up to mark all as read (selected in the settings) does mark all articles in the list as read correctly.
However, these two workaround don't prevent the issue from happening again, a force kill is still needed to restore a working behaviour.
I just wish the mark all as read action would also trigger a refresh, because there is no point staying on the same list when everything has been marked as read. I will probably create a feature request for that.