Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Progression sync between Komga (webui) and Cantook by Aldiko broken #1477

Closed
5 tasks done
DJScias opened this issue Apr 19, 2024 · 1 comment
Closed
5 tasks done

Progression sync between Komga (webui) and Cantook by Aldiko broken #1477

DJScias opened this issue Apr 19, 2024 · 1 comment

Comments

@DJScias
Copy link
Contributor

DJScias commented Apr 19, 2024

Steps to reproduce

  1. Read your epub to any part, doesn't matter if you use Komga or Cantook. Then close it.
  2. Try to open it on Komga WebUI if you read on Cantook, or vica versa.
  3. Notice the book starts at page 1 again.

Expected behavior

The book should resume progress as normal, so you can switch seamlessly.

Actual behavior

You start back at page 1.

Every time I read on Cantook and then switch to Komga WebUI it does mention "xxx pages left" but once I open the book it starts back on page 1 and overwrites Cantook.

Note: Cantook does make a mention of "Your webui had a different position, do you want to resume at this position?" but once you press OK on it nothing happens at all.. So that doesn't work either in the Cantook app.

Logs

I can't find anything log-related for this info within the docker logs..

Komga version

1.11.0

Operating system

Ubuntu 22.04.3 LTS

Installation method

Docker

Other details

No response

Acknowledgements

  • I have searched the existing issues (open AND closed) and this is a new ticket, NOT a duplicate or related to another open issue.
  • I have written a short but informative title.
  • I have checked the FAQ.
  • I have updated the app to the latest version.
  • I will fill out all of the requested information in this form.
Copy link
Contributor

🎉 This issue has been resolved in 1.11.1 (Release Notes)

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 26, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant