I stay mostly in the Unread view. Reading some items does not clear their read mark in the Unread view. It’s only for some of them some of the time. I have not identified any commonality for when this happens.
All my feeds are from Newsblur. Now on 7014, but i think it happened with the privies beta too.
iOS NNW is in an inconsitent state re read status.
Here’s a screen capture when reading a post. The round icon is clear showing that the post is in the read state:
Now swiping to the right to go back to the Unread page, this post appears with the round icon blue showing it as unread:
This post seems rather sticky, as trying to mark it read in that view it failed several times until I took this screen capture:
I was wondering if it may a timing issue and that I styed longer on the post, while taking a screen capture, to change its status. However if that’s the case it affects only the first changing to read status as trying to change the read status fast of any of these four items now is working fine.
I’m now trying to change the read status of this same item in the item view (same as first screen capture). It does turn to blue, however when I return to the All Unread page, it shows as unread so it hasn’t stuck.
I believe this was fixed since. Would you re-test with 7018?
That’s the build I’m running. My post with the screenshots was written when running build 7018.
Added to bug tracker: https://github.com/Ranchero-Software/NetNewsWire/issues/5033
I thought from the tracker and release notes that this had been fixed however it’s still happening in 7020. A read item still shows as unread when moving back to the All Unread page.
I thought it was fixed. It’s remarkably hard to reproduce.
I’m wondering if there’s not an underlying issue with the syncing with Newsblur showing up in this bug and the other one I mentioned (syncing not happening in background and much slower than it used to be). Could there be some timing issues with the Newsblur syncing that would affect the marking as read of items?
From discussions a year or so ago I get the impression I’m in a minority using Newsblur with NNW. If these issues are related to the syncing, and mostly or only affecting the syncing with Newsblur, it would explain why they’re more common for me than for others and hard(er) to reproduce when syncing with other sources.
Could be a NewsBlur issue — or, rather, our implementation of NewsBlur syncing. (Not blaming NewsBlur.)
The next major NetNewsWire release will be 7.1, and in 7.1 we will be concentrating almost entirely on syncing bug fixes.
