Feb 27
Komic displays stale cached content after files are updated on server
When a file is updated on the Komga server (e.g., replacing a wrong CBZ with the correct one), Komic continues to display the old version even after the server has been updated and re-analyzed. There's no way to manually force Komic to fetch the updated content from the server.
Steps to reproduce:
1. Read a book/chapter in Komic
2. Replace the file on the Komga server with an updated version
3. Re-analyze the file in the Komga web interface to confirm the changes
4. Try to read the same book/chapter in Komic
5. Komic displays the old version instead of fetching the updated file
Current behavior:
- Komic continues to show the old version of the file
- Clearing all downloads doesn't resolve the issue
- Restarting the app doesn't resolve the issue
- Logs show no re-fetch attempts from the server
- The content eventually updates after approximately 12 hours
Expected behavior:
- Komic should detect when content has been updated on the server
- There should be a manual option to force a refresh of content from the server
- Or at minimum, provide a "Force Refresh" option on individual books/series
Workaround:
The only current workaround is to use the Komga web app until Komic updates the content (appears to take ~12 hours).
Suggested solutions:
1. Add a "Clear Cache" or "Refresh from Server" option in the app settings (assuming this is a caching issue)
2. Add a "Refresh from Server" option in the book/series context menu
3. Implement detection of server-side content changes
4. Provide a way to manually force content re-fetch
Impact:
This prevents users from accessing corrected or updated content immediately, forcing them to either wait or use the web interface. This is particularly problematic when fixing corrupted files or replacing incorrect chapters.
Completed