Ashinch
[Bug] Inflated unread count with Miniflux (Google Reader API)
Checklist
- [x] I've already searched in existing issues and haven't found a similar problem reported.
- [x] I'm using the latest version of the app
- [ ] This error caused the app to crash
- [ ] This error is reproducible
Which category best fits this error?
Feed Sync
App version
0.15.1
Reproduction steps
Describe the bug After a successful initial sync with a Miniflux instance via the Google Reader API, the unread count in ReadYou becomes significantly inflated over time and does not match the actual count on the server.
Environment:
ReadYou Version: 0.15.1
Service: Miniflux (self-hosted)
Connection Method: Google Reader API
Steps to Reproduce:
Add a Miniflux account to ReadYou using the Google Reader API endpoint.
Log in and perform the initial synchronization. At this stage, the unread count is correct. (In my case, it was ~1000).
Use the app normally for about a day, allowing it to sync in the background.
Observe the unread count on the main screen of ReadYou.
Expected behavior The unread count displayed in ReadYou should accurately reflect the unread count on the Miniflux server. If the server shows 1000 unread items, ReadYou should also show ~1000.
Actual behavior On the second day of use, the unread count in ReadYou incorrectly jumped from ~1000 to ~6000. Performing a manual pull-to-refresh does not fix the issue; the count remains at ~6000.
Verification and Troubleshooting: To isolate the problem, I have verified the unread count on other platforms:
Miniflux Web Interface: The unread count is still the correct ~1000.
Reeder Classic (iOS client): This app also syncs with the same Miniflux server and correctly shows an unread count of ~1000.
This strongly suggests the issue is client-side within ReadYou and is not a problem with the Miniflux server itself.
Additional context The initial login and sync experience is now smooth, and the problems mentioned in issue #1142 appear to be resolved. This new issue seems to be related to how the app updates or calculates the unread count after the initial sync.
Thank you for your excellent work on this app!
Crash report
I believe my issue is related: unread articles on the Miniflux server do not get marked as unread locally which makes it difficult to use this app in conjunction with the frontend for desktop
In the latest version 0.15.2, this issue persists.
The number of unread items in the ReadYou app exceeds the count on the Miniflux server.
No such issues occur when using the Google Reader API in Capyreader or Reeder Classic.