Komic
Bugs

Read progress update issues (ePub)

Vincent R...
1y agoClosed

I noticed some issues still in the latest 1.13.0: - when I reach the end of a book (epub), it never reaches 100% progress. It seems like the progress indicator is based on the previous page and not the latest one (or at least the top of the page and not the bottom). It would be nice to reach 100% and have the book marked « completed » when it happens. - There are still some issues with API calls. Example when reading a book to the end, the last update is:

Request Body (274 octets) { "device": { "id": "unused", "name": "Komga-webui" }, "locator": { "href": "OEBPS/file0001.xhtml", "locations": { "position": 8, "progression": 0.9545454545454546, "totalProgression": 0.875 }, "title": "my book", "type": "application/xhtml+xml" }, "modified": "2025-09-29T06:41:06.782Z" }

Response Headers (9) Cache-Control: max-age=0, must-revalidate, no-transform, private Content-Type: application/json Date: Mon, 29 Sep 2025 06:41:06 GMT Server: nginx Strict-Transport-Security: max-age=31536000 ; includeSubDomains Vary: Origin, Access-Control-Request-Method, Access-Control-Request-Headers x-content-type-options: nosniff x-frame-options: SAMEORIGIN x-xss-protection: 0

Response Body (161 octets) { "error": "Bad Request", "message": "Invalid progression", "path": "/api/v1/books/0N34Y40R2TTK1/progression", "status": 400, "timestamp": "2025-09-29T06:41:06.846+00:00" }

3 comments

  1. Vincent R...1y ago

    Thanks for aiming for the extra mile above Komga’s features! You have a great app, very clean and well designed ! For « reaching the end » detection, of it’s too complex, don’t bother. It is a nice to have at best. I was thinking it to be easy: no next page anymore or nothing more to scroll…

    1. Pablo Ruiz1y ago

      I've tested this quite a bit, and unfortunately, there's nothing I can do from the app side, this behavior comes from Komga itself. Komic just reports your reading progress to the server, but Komga is the one that validates and saves it.

      The "invalid progression" error and the fact that EPUBs never quite reach 100% are both handled internally by Komga. Even if Komic sends a full 100% value, Komga will reject it if it doesn't match its own internal logic.

      So in short, this is a Komga-side issue, not something that can be fixed directly in Komic.

  2. Pablo Ruiz1y ago

    You're right. With EPUBs the progress never reaches 100%. I can reproduce the same behavior in Komga's web UI, so it's not just Komic. I'll work on a more reliable way to detect when a book is actually finished, but it's tricky because EPUB layouts vary and we only have percentages and locators to rely on.

    About the "Invalid progression" error: the value looks correct in the logs, so I'll dig deeper to find the root cause.