No Unread and Starred

[M1ckB]

Steps to Reproduce

No articles categorized as Unread or Starred in Capy Reader.

Expected behavior

I expect that articles end up in Unread, Starred, or All depending on their status in Feedbin.

All articles are being fetched upon refresh but they end up (unnoticed) in All.

Screenshots or screen recording

No response

Device, Operating system, and app version

Fairphone 5, Android 13, Capy Reader 2025.02.1108

[jocmp]

Hey @M1ckB, thanks for the bug report. If possible, can you share your crash logs for this? You can find them under General > Advanced > Share crash logs. Feel free to email it to me at [email protected].

Given you're on Android 13, I suspect this is related to the following issue which affects devices below Android 14.

• Sync of marked as read items no longer working reliably with FreshRSS #909 (comment)

If that is the bug, I'm planning to release a version for Google Play and F-Droid later today which should fix it.

[M1ckB]

Thank you for your quick response - and for the lovely app!

It could be the same bug as the one referenced. Everything ends up in All and nowhere else it seems.

The app has been working flawlessly for me until sometime last week, I believe.

Let me know if you need anything else from me to troubleshoot the issue.

capy_crash_logs.txt

[jocmp]

Will do. It looks like the same database error based on your crash logs:

02-26 21:32:27.139 17516 17545 E cr.db_error: handled_exception
02-26 21:32:27.139 17516 17545 E cr.db_error: android.database.sqlite.SQLiteException: near "UPDATE": syntax error (code 1 SQLITE_ERROR): , while compiling: INSERT INTO article_statuses(
02-26 21:32:27.139 17516 17545 E cr.db_error:   article_id,
02-26 21:32:27.139 17516 17545 E cr.db_error:   updated_at,
02-26 21:32:27.139 17516 17545 E cr.db_error:   starred
02-26 21:32:27.139 17516 17545 E cr.db_error: )
02-26 21:32:27.139 17516 17545 E cr.db_error: VALUES (
02-26 21:32:27.139 17516 17545 E cr.db_error:   ?,
02-26 21:32:27.139 17516 17545 E cr.db_error:   ?,
02-26 21:32:27.139 17516 17545 E cr.db_error:   1
02-26 21:32:27.139 17516 17545 E cr.db_error: )
02-26 21:32:27.139 17516 17545 E cr.db_error: ON CONFLICT DO UPDATE
02-26 21:32:27.139 17516 17545 E cr.db_error: SET
02-26 21:32:27.139 17516 17545 E cr.db_error: starred = excluded.starred

Basically I had added some database code that is unsupported in Android 13 and below. v2025.02.1110-dev fixes it if you want to try that. I'll also post here when v2025.02.1111 for the GPlay/F-Droid goes live.