[Bug]: Continue Listening ignoring local plays after initial play #2861

Open
opened 2026-04-25 00:11:20 +02:00 by adam · 4 comments
Owner

Originally created by @Klaesy on GitHub (Jun 28, 2025).

What happened?

The android app is also needed to reproduce this issue (IOS probably as well, but I don't have a device to test it). I logged it under the server application, since I think it's the one where the fix is needed.

The Continue Listening section does not take local plays (except for the initial play of the audio book) into account. For example I started a local audiobook quite a while ago, but never finished it. Now I want to pick it up again but it's somewhere in the back of my continue listening section and thus hard to start playing immediately when opening the app.

When looking at my listening sessions (audiobookshelf/config/sessions/) I can confirm that the local sessions pushed to the server.

What did you expect to happen?

I expected local plays to also show up in at the front of the Continue Listening section.

Steps to reproduce the issue

  1. Have two audio books in your mobile app, one that has been downloaded via the app so it can be played directly, and one that is streamed.
  2. Play the streamed audio book (it's put at the front of the Continue Listening section)
  3. Play the local audio book for the first time (it's put at the front of the Continue Listening section)
  4. Play the streamed audio book again (it's put at the front of the Continue Listening section)
  5. Play the local audio book again (it remain in it's current place in the Continue Listening section)

Audiobookshelf version

v2.25.1

How are you running audiobookshelf?

Docker

What OS is your Audiobookshelf server hosted from?

Linux

If the issue is being seen in the UI, what browsers are you seeing the problem on?

None

Logs


Additional Notes

No response

Originally created by @Klaesy on GitHub (Jun 28, 2025). ### What happened? The android app is also needed to reproduce this issue (IOS probably as well, but I don't have a device to test it). I logged it under the server application, since I think it's the one where the fix is needed. The Continue Listening section does not take local plays (except for the initial play of the audio book) into account. For example I started a local audiobook quite a while ago, but never finished it. Now I want to pick it up again but it's somewhere in the back of my continue listening section and thus hard to start playing immediately when opening the app. When looking at my listening sessions (audiobookshelf/config/sessions/) I can confirm that the local sessions pushed to the server. ### What did you expect to happen? I expected local plays to also show up in at the front of the Continue Listening section. ### Steps to reproduce the issue 1. Have two audio books in your mobile app, one that has been downloaded via the app so it can be played directly, and one that is streamed. 2. Play the streamed audio book (it's put at the front of the Continue Listening section) 3. Play the local audio book for the first time (it's put at the front of the Continue Listening section) 4. Play the streamed audio book again (it's put at the front of the Continue Listening section) 5. Play the local audio book again (it remain in it's current place in the Continue Listening section) ### Audiobookshelf version v2.25.1 ### How are you running audiobookshelf? Docker ### What OS is your Audiobookshelf server hosted from? Linux ### If the issue is being seen in the UI, what browsers are you seeing the problem on? None ### Logs ```shell ``` ### Additional Notes _No response_
adam added the bug label 2026-04-25 00:11:20 +02:00
Author
Owner

@Vito0912 commented on GitHub (Jun 28, 2025):

Do you have an active progress for this book?

@Vito0912 commented on GitHub (Jun 28, 2025): Do you have an active progress for this book?
Author
Owner

@Klaesy commented on GitHub (Jun 29, 2025):

Yes both books have an active progress (viewed from web page).

@Klaesy commented on GitHub (Jun 29, 2025): Yes both books have an active progress (viewed from web page).
Author
Owner

@alexhk90 commented on GitHub (Sep 1, 2025):

I have the same issue with the Android app - I only just started using audiobookshelf recently so I first thought that there was no easy "continue listening" feature (the app is stated to be "beta" after all) but then I came across https://github.com/advplyr/audiobookshelf-app/pull/574 which suggests that it does. However I only have "Local books" which show up right at the bottom of the screen when opening the audiobookshelf Android app. Good to know that the intended behaviour is that it would show up at the top / auto-open the latest one to continue.

In my case though I see there is no "active progress" for the book when checking via the web UI, and it's not showing up in the "User Stats" or "Recent Sessions", so I wonder if it's not syncing somehow (even though I can clearly access the server as I'm able to see my library and download other books).

@alexhk90 commented on GitHub (Sep 1, 2025): I have the same issue with the Android app - I only just started using audiobookshelf recently so I first thought that there was no easy "continue listening" feature (the app is stated to be "beta" after all) but then I came across https://github.com/advplyr/audiobookshelf-app/pull/574 which suggests that it does. However I only have "Local books" which show up right at the bottom of the screen when opening the audiobookshelf Android app. Good to know that the intended behaviour is that it would show up at the top / auto-open the latest one to continue. In my case though I see there is no "active progress" for the book when checking via the web UI, and it's not showing up in the "User Stats" or "Recent Sessions", so I wonder if it's not syncing somehow (even though I can clearly access the server as I'm able to see my library and download other books).
Author
Owner

@Cabowski92 commented on GitHub (Sep 11, 2025):

I’m having the book completely erase progress of a book that is downloaded and I use the audiobook shelf app for iOS. This doesn’t happen with plappa

@Cabowski92 commented on GitHub (Sep 11, 2025): I’m having the book completely erase progress of a book that is downloaded and I use the audiobook shelf app for iOS. This doesn’t happen with plappa
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#2861