Unread Articles list not showing on launch about vienna-rss

[josh64x2]

I was unable to reproduce on macOS 12.6.1, hopefully one of the other devs can try on macOS 13.

[jazzace]

I just tested on macOS 13.0.1 Beta 1 and the problem does not occur reliably. My original thesis said that you had to read all the unread items, then have something come in, after which the problem would show up on launch. It does appear that there is a relationship between reading all the Unread Articles, then receiving new items, then launching.

[josh64x2]

I did install Ventura 13.0 and couldn't reproduce there either sorry 😞 .
If you experience this issue again please re-open the issue and I'll try digging a bit deeper.

[jazzace]

Happened when I launched this morning.

If there are logs or other details that would help, let me know. In the meantime, I will see if I can come up with steps that are more reproducible.

[jazzace]

My best bet (which is, admittedly, hard to reproduce) is that the original circumstance I found (prior to editing my initial post) is the primary problem and other, seemingly random occurrences are related to the underlying bug that causes the issue. Those repro steps were:

1. Read (or Mark as Read) all the articles in your feeds.
2. In the left sidebar, select Unread Articles.
3. Quit Vienna.
4. Wait until you know one of your feeds has a new article.
5. Open Vienna

That is, if there were no unread items in the list when you quit Vienna, the Unread Articles list does not update when the feeds are refreshed upon launch. Moving to any other item and returning to Unread Articles shows the list correctly.

[jazzace]

Of course, I then had it succeed in that instance, but only when a single feed had an update. I was able to reproduce it when there were two feeds with updates. That's actually what the two screenshots I supplied have in common. You might be able to force this behaviour by having one feed with an unread article and one that you then mark as unread before quitting, but I could not get that to reproduce every time. (I think it may have something to do with when Vienna chooses to update its feeds, since some of my testing involves quitting and then immediately reopening (my current feed refresh is set for 15 minutes).

[barijaona]

I have seen something similar while I was working on pull request #1625 and put breakpoints in initialization code.

Might be caused by notifications being sent early, while the app is not yet ready to handle them.

[Eitot]

Has this been resolved?

[jazzace]

Yes.