mirror of
https://github.com/advplyr/audiobookshelf.git
synced 2026-05-30 23:40:40 +02:00
[Bug]: Progress is lost or reset randomly #3301
Assignees
adam (Adam Melkus)
Clear assignees
adam (Adam Melkus)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/audiobookshelf#3301
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @kymahi on GitHub (Apr 14, 2026).
What happened?
This last instance was when I was using Android Auto. I was going through the different options on my car screen and accidentally started a new book while listening to one at the time. It started, and I went to my phone to start the other book again. However, when I started the book, even though it showed the correct progress on the book screen, it started the book over. Pausing it updated the progress on the book screen back to 0%.
What did you expect to happen?
When clicking on a book to play, to start the book at the current progress and not restart it
Steps to reproduce the issue
Audiobookshelf version
v2.33.1
How are you running audiobookshelf?
Docker
What OS is your Audiobookshelf server hosted from?
macOS
If the issue is being seen in the UI, what browsers are you seeing the problem on?
None
Logs
Additional Notes
Unknown why the book started accidentally is not shown in the logs as being started
@Vito0912 commented on GitHub (Apr 14, 2026):
Android Auto is bugged.
Progress is only synced if you have not an open session (so mini player). If you have a session from before, either listening to the phone, or starting via Auto, any new starting trough Android Auto will not sync at all
@seh-len commented on GitHub (Apr 17, 2026):
Audiobookshelf also contributes to the fact that the listening experience is, at best, suboptimal when listening on different devices. For example, if I start a session on the web and want to continue it in the Android app, the Android app initially shows the correct progress after I open it, but when I click play, the Android app jumps back to the last position I listened to in the app instead of continuing from the position of the web session, which it had correctly saved. For some reason, the Android app prioritizes its own progress over that from the web session. This can really only be a small bug with a big impact.