Add workaround for "Row too big to fit into CursorWindow" bug #523
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Mark Bestavros <markbest@bu.edu>
Ashinch
approved these changes
Jan 12, 2024
|
I agree. Hopefully, Google can fully fix it, so we won't have to resort to workarounds. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The bug described in #312 is longstanding, and quite annoying - the only workaround is for users to delete all articles in the affected source and move on, but that's not ideal (articles may be missed).
From recent research into the topic, it seems like this is a broader Android problem and not unique to Read You. Fortunately, that also means people have found fixes!
With the help of @kermes in the Read You issue, I was able to consistently reproduce the bug using the source
https://www.newtral.es/feed/. After applying the fix suggested in the thread above, the bug no longer happens on that feed! 🎉@Ashinch said in the Read You bug thread that it may also be a paging issue, so we probably shouldn't consider this a permanent fix. But it does appear to be an effective workaround for a pretty common bug.