Steps to reproduce
- Use Suwayomi as the primary source/server for mangas, and connect Mihon using the Suwayomi extension.
- Ensure Suwayomi is also active as a tracker within Mihon to handle chapter sync.
- In the extension settings, enable both Tracker: Delete downloaded files from suwayomi when marking chapters as read and Fetch Data from Source.
- Let the Suwayomi server download a new chapter. (Important: The new chapter correctly shows as "unread" on the Suwayomi server side).
- Refresh the library or the specific manga in Mihon.
- Suwayomi chapter ist unread, in mihon the chapter is read
Expected behavior
The newly downloaded chapter should appear in Mihon and be marked as "unread", exactly matching the current unread status on the Suwayomi server.
Actual behavior
The new chapter appears in Mihon but is instantly and incorrectly marked as "read". I want to emphasize that on the Suwayomi server itself, the chapter is correctly listed as unread before and after the refresh. Because Suwayomi itself acts as the tracker in this setup to handle the deletion logic, this false local "read" state in Mihon directly disrupts the sync loop between the client and the server.
App version
0.19.4
Android version
16
Other details
As Suwayomi is my self-hosted source, I heavily rely on the automatic deletion feature via the Suwayomi tracker to manage my server storage efficiently. Turning it off isn't a viable workaround.
It seems there is a conflict between the "Fetch Data from Source" option and the Suwayomi tracker's deletion logic. When the old chapters are physically deleted from the server, it might cause an index shift in the API response, leading Mihon to mistakenly assign the "read" flag to the new, unread chapters upon refresh.
Of course, it is also entirely possible that my setup is flawed or that I am completely misunderstanding how these specific settings are supposed to interact with each other. Any clarification or help to point me in the right direction would be highly appreciated!
(Note: Suwayomi Server Version: v2.1.1867, Suwayomi Extension Version: 1.4.25)
Acknowledgements
Steps to reproduce
Expected behavior
The newly downloaded chapter should appear in Mihon and be marked as "unread", exactly matching the current unread status on the Suwayomi server.
Actual behavior
The new chapter appears in Mihon but is instantly and incorrectly marked as "read". I want to emphasize that on the Suwayomi server itself, the chapter is correctly listed as unread before and after the refresh. Because Suwayomi itself acts as the tracker in this setup to handle the deletion logic, this false local "read" state in Mihon directly disrupts the sync loop between the client and the server.
App version
0.19.4
Android version
16
Other details
As Suwayomi is my self-hosted source, I heavily rely on the automatic deletion feature via the Suwayomi tracker to manage my server storage efficiently. Turning it off isn't a viable workaround.
It seems there is a conflict between the "Fetch Data from Source" option and the Suwayomi tracker's deletion logic. When the old chapters are physically deleted from the server, it might cause an index shift in the API response, leading Mihon to mistakenly assign the "read" flag to the new, unread chapters upon refresh.
Of course, it is also entirely possible that my setup is flawed or that I am completely misunderstanding how these specific settings are supposed to interact with each other. Any clarification or help to point me in the right direction would be highly appreciated!
(Note: Suwayomi Server Version: v2.1.1867, Suwayomi Extension Version: 1.4.25)
Acknowledgements