search

LeoKlaus / plappa

An Audiobook client for Jellyfin and AudioBookShelf, written in Swift/SwiftUI.
https://plappa.me
159 stars 0 forks source link

[BUG] Playback state get's mixed up #141

Closed eDimoon closed 2 days ago

eDimoon commented 3 days ago

Describe the bug Since updating the ABS-Server to 2.10.1 via Docker-image, the progress in books get's mixed up / wrongly set. The update to plappa version 1.2.0 also happened nearly at the same time. For the reason mentioned under Additional, i don't think this is on the ABS end. (But please correct me if i am wrong.)

To Reproduce Steps to reproduce the behavior:

  1. Play a book in your library
  2. Pause the book
  3. Check the progress either on ABS or plappa itself.

PS: As i am writing this bug report, the book is now marked completely played, but the app seems to still remember the local state. As shown in screenshot 3.

Expected behavior If a book get's played, at the moment of pause (or maybe a small delay) i expect the dashboard to represent the listening state. Either finished, or in the middle somewhere.

Screenshots grafik grafik

Player shows the book as finished, but on the bottom, the "real" status remains and still holds the correct listening status. grafik

Environment

Additional Info A rebuild of the container and going back to a version before, does not change this behaviour.

If this has been adressed already and i didn't see it in the issue tracker, please feel free to close the report.

LeoKlaus commented 2 days ago

Hi Jan, thank you for reporting this.

There's an issue causing plappa to store playback states with a duration of 1 seconds (the current time is correctly saved), which leads to the progress (current time/duration) to always be 100%. The time itself is saved correctly.

I've already fixed this in the latest TestFlight release, I'll release an update to the AppStore asap.

If you want to try the TestFlight release, you can do so here: https://testflight.apple.com/join/oSAekRD5

eDimoon commented 2 days ago

Hi Leo, thanks for the fast response and thanks for the fix. I'll mark it as closed, since the issue should vanish in the next release. Thanks again. :)