V2026.03.1199 crashes when updating from FreshRSS

[RonnyB74]

After updating to V2026.03.1199, updating feeds from FreshRSS (1.28.2-dev) no longer works. The update arrow spins for a few seconds, then the app simply closes. Could this be due to the change “Improve FreshRSS updates by checking last refresh time”? I am using the German localization.

[jocmp]

Hey @RonnyB74 can you send me your crash logs here or to support@jocmp.com? You can find them under Settings > General > Share crash logs.

This may be fixed in the latest version 2026.03.1200, but any details from your current issue will be helpful for future debugging.

[RonnyB74]

Hey jocmp,

the problem seems to have been fixed with version 226.03.1200, thank you!

I have tested all three versions, starting with V226.02.1198. I have sent you the crash log by email. In order, I reloaded the messages with versions 2026.02.1198, 2026.03.1199, and 2026.03.1200. With 2026.03.1199, the crash occurred again, but the other two versions ran without crashing. I only noticed one message: “ContextImpl: Failed to ensure /storage/8ff87de4-0b37-4799-b09a-82773e869e07/Android/data/com.capyreader.app/cache: android.os.ServiceSpecificException: (code -22)”. What does this error mean?

It seems that only the currently installed version is logged as the program version? At least, the log starts with “App version: 2026.03.1200 (free, 1200)”.

[jocmp]

Glad it's fixed in the latest version. Thanks for the logs @RonnyB74, I finally got around to looking at them.

• Let me address your questions first. The logs begin with the current version installed, but may span previous versions.
• The ServiceSpecificException is new to me. It seems to be an OS-level issue around cache verification and unrelated the in-app crash. The crash is most likely caused by the out-of-memory error that is logged with the following stack trace. This would correlate with the fact that the crash happened on refresh.

85888 free bytes and 83KB until OOM, target footprint 134217728, growth limit 134217728; giving up on allocation because <1% of heap free after GC.
// *snip*
03-11 17:48:55.649 47079 47187 E AndroidRuntime: 	at Y6.b.fromJson(Unknown Source:15)
03-11 17:48:55.649 47079 47187 E AndroidRuntime: 	at com.jocmp.readerclient.ItemJsonAdapter.fromJson(SourceFile:10)

All told, I believe you're right that this is related to the "last update" changes. I had undone those changes in 2026.03.1200. I'm tracking similar bugs relating to that change in #1858. This shouldn't be a bug going forward, and I'll spend a lot more time testing it before reintroducing that change.

Let me know if I can clarify anything, again, thanks for bearing with me!