Articles come back up after about a month.

[shortwavesurfer2009]

1. Environment

• Device: [Pixel 6] Oneplus Nord N200 5G
• OS: [Android 13] LineageOS 21 (Android 14)
• APP: [0.9.6] 0.11.1

2. Describe the bug

I have notifications enabled for articles, and I find that with sites that notify for fewer things, articles often come back up after a month as if they were new. You have to look at the date to see if they are new or not.

(I may not respond in a timely manner, but you will be notified when this issue is resolved or refused to be resolved.)

[doubleddav]

I have been having this exact issue for a couple of years, with every version and over different phones and Android versions

[Maximus1996]

I started having the issue after update 0.11.0 (or 0.10, not sure. It was the update with some redesign updates).

[twizzlebizzle]

Noticed this issue too recently. When I open unread articles i've started just marking anything older than 3 days as read to hide the countless articles that are older. Not sure if it's the app or my feeds.

[jsstaedtler]

I'll join in as well, I've also experienced this phenomenon for a few months with v0.11.1 on a Pixel 7 Pro.

It only seems to pertain to the Android notifications. Recently I thought it was notifying me about old posts that I never marked as read, so I marked every single post in the app as read—but I continue to get occasional blasts from the past.

It feels like perhaps the app is losing track of which posts have already generated a notification? I have zero knowledge of how that works on Android though.

[wasu-code]

Will changing Settings » Accounts » Local » Keep archived articles = Always help you guys in any way?

I think that's how I solved it when it was happening to me.
However, that would increase storage usage in the long run...

[shortwavesurfer2009]

Honestly, I'm not sure as I have not tried that, but a way to test that would be to set it lower to like one day or something like that and see if that starts showing up articles more often. And from a shorter time ago, in which case, that would pretty much confirm this was the problem.