ReadYouApp / ReadYouApp/ReadYou
Stale data, refreshing doesn't help
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 7.5k
- Forks
- 330
- PR merge metrics
- No merged PRs in 30d
Description
1. Environment
- Device: Samsung Galaxy S22
- OS: Android 14
- APP: 0.12.1
2. Describe the bug
I'm using ReadYou with a FreshRSS instance. I'm noticing stale data in ReadYou when comparing to the FreshRSS source of truth, such as:
- all articles marked as read in FreshRSS, some articles marked as unread in ReadYou
- some articles unfavorited in FreshRSS, still marked as favorite in ReadYou
- wrong article date in ReadYou, correct in FreshRSS—"correct" meaning the one I found on the live RSS feed (maybe the date was updated after publishing and ReadYou keeps the old date in cache?)
I don't know how to provide specific reproduction steps here. What surprises me most is that when I try a manual pull-to-refresh, the issues persist—I'd expect ReadYou to pull everything from FreshRSS instead and end up with a clean list that matches the one from the FreshRSS instance.
The only way I found to "fix" it is to clear the state in ReadYou somehow. For example, when the stale "unread" articles (actually already read per FreshRSS) are marked as read in ReadYou, they won't appear again as unread after a pull-to-refresh. This is of course not a solution.
This seems similar to other reports, but none of them have had any follow-up. For example: #973, #958.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the FreshRSS comparison and the manual pull-to-refresh flow described in the report. Use the read status, favorite status, and article-date mismatches as cases to investigate; done means refreshed ReadYou data consistently matches the FreshRSS source of truth without requiring local state to be cleared.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100