[Bug]: Continue Listening no longer updating (v2.24.0) #2820

adam commented

@maodun96 commented on GitHub (Jun 4, 2025):

I seem to be experiencing a similar issue.
My use case: I frequently switch between listening to audiobooks on my iPad and iPhone（plappa）. Therefore, the progress synchronization feature is extremely important to me.
After updating the version, it seems the progress is no longer perfectly syncing with the ABS server, though it occasionally works. Initially, I thought it might be an issue caused by my reverse proxy. Now I've discovered the problem appears to have started two or three days ago, which coincides with the release of v2.24.0. (I'm more inclined to think it's version-related, as I'm experiencing the same issue even when accessing via http+IP)

I've now rolled back the ABS server (unraid docker) to v2.23.0 and the sync function seems to be back to normal. If there are any exceptions, I will report them here again.

@maodun96 commented on GitHub (Jun 4, 2025): I seem to be experiencing a similar issue. My use case: I frequently switch between listening to audiobooks on my iPad and iPhone（plappa）. Therefore, the progress synchronization feature is extremely important to me. After updating the version, it seems the progress is no longer perfectly syncing with the ABS server, though it occasionally works. Initially, I thought it might be an issue caused by my reverse proxy. Now I've discovered the problem appears to have started two or three days ago, which coincides with the release of v2.24.0. (I'm more inclined to think it's version-related, as I'm experiencing the same issue even when accessing via http+IP) I've now rolled back the ABS server (unraid docker) to v2.23.0 and the sync function seems to be back to normal. If there are any exceptions, I will report them here again.

adam commented

@WillGunn commented on GitHub (Jun 4, 2025):

@maodun96 that looks like a different issue. The progress syncing is working, but the order of the Continue Listening section of the homepage is not updating to reflect the most recent book that is listened to.

@WillGunn commented on GitHub (Jun 4, 2025): @maodun96 that looks like a different issue. The progress syncing is working, but the order of the Continue Listening section of the homepage is not updating to reflect the most recent book that is listened to.

adam commented

@maodun96 commented on GitHub (Jun 4, 2025):

@maodun96 that looks like a different issue. The progress syncing is working, but the order of the Continue Listening section of the homepage is not updating to reflect the most recent book that is listened to.

I think this is a different bug caused by the same reason.

@maodun96 commented on GitHub (Jun 4, 2025): > [@maodun96](https://github.com/maodun96) that looks like a different issue. The progress syncing is working, but the order of the Continue Listening section of the homepage is not updating to reflect the most recent book that is listened to. I think this is a different bug caused by the same reason.

adam commented

@advplyr commented on GitHub (Jun 6, 2025):

Are you using plappa? There is a known bug with the way plappa is making API requests that is creating 2 media progress records for the same book.

@advplyr commented on GitHub (Jun 6, 2025): Are you using plappa? There is a known bug with the way plappa is making API requests that is creating 2 media progress records for the same book.

adam commented

@WillGunn commented on GitHub (Jun 8, 2025):

@advplyr i do not. I see the same issue playing books via the Audiobookshelf apps as I do through the Audiobookshelf web browser interface.

Are there debug logs I can turn on and upload?

@WillGunn commented on GitHub (Jun 8, 2025): @advplyr i do not. I see the same issue playing books via the Audiobookshelf apps as I do through the Audiobookshelf web browser interface. Are there debug logs I can turn on and upload?

adam commented

@advplyr commented on GitHub (Jun 8, 2025):

The update that was made in v2.24.0 was to set the updatedAt time of the media progress to the timestamp that is sent in from the device. If you are saying it doesn't matter if you listen in the web app or the mobile app then I don't see how the update would have something to do with it.

In this case it would probably be more helpful to look at the database directly if you are comfortable with that.

It is a sqlite database that is in the /config folder.

Sort the mediaProgresses table by updatedAt descending and filter by isFinished=0 AND currentTime>0

This is basically what that shelf is pulling by library.

@advplyr commented on GitHub (Jun 8, 2025): The update that was made in v2.24.0 was to set the `updatedAt` time of the media progress to the timestamp that is sent in from the device. If you are saying it doesn't matter if you listen in the web app or the mobile app then I don't see how the update would have something to do with it. In this case it would probably be more helpful to look at the database directly if you are comfortable with that. It is a sqlite database that is in the `/config` folder. Sort the `mediaProgresses` table by `updatedAt` descending and filter by `isFinished=0 AND currentTime>0` This is basically what that shelf is pulling by library. ![Image](https://github.com/user-attachments/assets/31d73cf1-4c85-4a0e-8bd0-e10892507f10)

adam commented

@WillGunn commented on GitHub (Jun 8, 2025):

Attempting to open the db file locally with DB Browser for SQLite which I've used in the past for other projects I get

No errors about that in the startup logs of the service fwiw:

[2025-06-08 12:27:32.557] INFO: [Database] Initializing db at "/config/absdatabase.sqlite"
[2025-06-08 12:27:32.598] INFO: [Database] Loading extension /usr/local/lib/nusqlite3/libnusqlite3.so
[2025-06-08 12:27:32.603] INFO: [Database] Successfully loaded extension /usr/local/lib/nusqlite3/libnusqlite3.so
[2025-06-08 12:27:32.604] INFO: [Database] Db supports unaccent and unicode foldings
[2025-06-08 12:27:32.604] INFO: [Database] Db connection was successful
[2025-06-08 12:27:32.619] INFO: [MigrationManager] Database is already up to date.
[2025-06-08 12:27:32.820] INFO: [Database] Db initialized with models: user, library, libraryFolder, book, podcast, podcastEpisode, libraryItem, mediaProgress, series, bookSeries, author, bookAuthor, collection, collectionBook, playlist, playlistMediaItem, device, playbackSession, feed, feedEpisode, setting, customMetadataProvider, mediaItemShare
[2025-06-08 12:27:33.239] INFO: [Database] running ANALYZE
[2025-06-08 12:27:33.317] INFO: [Database] ANALYZE completed

@WillGunn commented on GitHub (Jun 8, 2025): Attempting to open the db file locally with DB Browser for SQLite which I've used in the past for other projects I get ![Image](https://github.com/user-attachments/assets/7763831f-5d99-4c99-af9a-207bb9ac1b01) No errors about that in the startup logs of the service fwiw: ``` [2025-06-08 12:27:32.557] INFO: [Database] Initializing db at "/config/absdatabase.sqlite" [2025-06-08 12:27:32.598] INFO: [Database] Loading extension /usr/local/lib/nusqlite3/libnusqlite3.so [2025-06-08 12:27:32.603] INFO: [Database] Successfully loaded extension /usr/local/lib/nusqlite3/libnusqlite3.so [2025-06-08 12:27:32.604] INFO: [Database] Db supports unaccent and unicode foldings [2025-06-08 12:27:32.604] INFO: [Database] Db connection was successful [2025-06-08 12:27:32.619] INFO: [MigrationManager] Database is already up to date. [2025-06-08 12:27:32.820] INFO: [Database] Db initialized with models: user, library, libraryFolder, book, podcast, podcastEpisode, libraryItem, mediaProgress, series, bookSeries, author, bookAuthor, collection, collectionBook, playlist, playlistMediaItem, device, playbackSession, feed, feedEpisode, setting, customMetadataProvider, mediaItemShare [2025-06-08 12:27:33.239] INFO: [Database] running ANALYZE [2025-06-08 12:27:33.317] INFO: [Database] ANALYZE completed ```

adam commented

@nichwall commented on GitHub (Jun 8, 2025):

Attempting to open the db file locally with DB Browser for SQLite which I've used in the past for other projects I get

No errors about that in the startup logs of the service fwiw:

[2025-06-08 12:27:32.557] INFO: [Database] Initializing db at "/config/absdatabase.sqlite"
[2025-06-08 12:27:32.598] INFO: [Database] Loading extension /usr/local/lib/nusqlite3/libnusqlite3.so
[2025-06-08 12:27:32.603] INFO: [Database] Successfully loaded extension /usr/local/lib/nusqlite3/libnusqlite3.so
[2025-06-08 12:27:32.604] INFO: [Database] Db supports unaccent and unicode foldings
[2025-06-08 12:27:32.604] INFO: [Database] Db connection was successful
[2025-06-08 12:27:32.619] INFO: [MigrationManager] Database is already up to date.
[2025-06-08 12:27:32.820] INFO: [Database] Db initialized with models: user, library, libraryFolder, book, podcast, podcastEpisode, libraryItem, mediaProgress, series, bookSeries, author, bookAuthor, collection, collectionBook, playlist, playlistMediaItem, device, playbackSession, feed, feedEpisode, setting, customMetadataProvider, mediaItemShare
[2025-06-08 12:27:33.239] INFO: [Database] running ANALYZE
[2025-06-08 12:27:33.317] INFO: [Database] ANALYZE completed

DB browser uses an old version of SQLite which is not compatible with updates to ABS.
https://github.com/advplyr/audiobookshelf/issues/4134

@nichwall commented on GitHub (Jun 8, 2025): > Attempting to open the db file locally with DB Browser for SQLite which I've used in the past for other projects I get > > ![Image](https://github.com/user-attachments/assets/7763831f-5d99-4c99-af9a-207bb9ac1b01) > > No errors about that in the startup logs of the service fwiw: > ``` > [2025-06-08 12:27:32.557] INFO: [Database] Initializing db at "/config/absdatabase.sqlite" > [2025-06-08 12:27:32.598] INFO: [Database] Loading extension /usr/local/lib/nusqlite3/libnusqlite3.so > [2025-06-08 12:27:32.603] INFO: [Database] Successfully loaded extension /usr/local/lib/nusqlite3/libnusqlite3.so > [2025-06-08 12:27:32.604] INFO: [Database] Db supports unaccent and unicode foldings > [2025-06-08 12:27:32.604] INFO: [Database] Db connection was successful > [2025-06-08 12:27:32.619] INFO: [MigrationManager] Database is already up to date. > [2025-06-08 12:27:32.820] INFO: [Database] Db initialized with models: user, library, libraryFolder, book, podcast, podcastEpisode, libraryItem, mediaProgress, series, bookSeries, author, bookAuthor, collection, collectionBook, playlist, playlistMediaItem, device, playbackSession, feed, feedEpisode, setting, customMetadataProvider, mediaItemShare > [2025-06-08 12:27:33.239] INFO: [Database] running ANALYZE > [2025-06-08 12:27:33.317] INFO: [Database] ANALYZE completed > ``` DB browser uses an old version of SQLite which is not compatible with updates to ABS. https://github.com/advplyr/audiobookshelf/issues/4134

adam commented

@WillGunn commented on GitHub (Jun 8, 2025):

Attempting to open the db file locally with DB Browser for SQLite which I've used in the past for other projects I get

No errors about that in the startup logs of the service fwiw:

[2025-06-08 12:27:32.557] INFO: [Database] Initializing db at "/config/absdatabase.sqlite"
[2025-06-08 12:27:32.598] INFO: [Database] Loading extension /usr/local/lib/nusqlite3/libnusqlite3.so
[2025-06-08 12:27:32.603] INFO: [Database] Successfully loaded extension /usr/local/lib/nusqlite3/libnusqlite3.so
[2025-06-08 12:27:32.604] INFO: [Database] Db supports unaccent and unicode foldings
[2025-06-08 12:27:32.604] INFO: [Database] Db connection was successful
[2025-06-08 12:27:32.619] INFO: [MigrationManager] Database is already up to date.
[2025-06-08 12:27:32.820] INFO: [Database] Db initialized with models: user, library, libraryFolder, book, podcast, podcastEpisode, libraryItem, mediaProgress, series, bookSeries, author, bookAuthor, collection, collectionBook, playlist, playlistMediaItem, device, playbackSession, feed, feedEpisode, setting, customMetadataProvider, mediaItemShare
[2025-06-08 12:27:33.239] INFO: [Database] running ANALYZE
[2025-06-08 12:27:33.317] INFO: [Database] ANALYZE completed

DB browser uses an old version of SQLite which is not compatible with updates to ABS. #4134

Gotcha, what program are you using in your screenshot above then?

@WillGunn commented on GitHub (Jun 8, 2025): > > Attempting to open the db file locally with DB Browser for SQLite which I've used in the past for other projects I get > > ![Image](https://github.com/user-attachments/assets/7763831f-5d99-4c99-af9a-207bb9ac1b01) > > No errors about that in the startup logs of the service fwiw: > > ``` > > [2025-06-08 12:27:32.557] INFO: [Database] Initializing db at "/config/absdatabase.sqlite" > > [2025-06-08 12:27:32.598] INFO: [Database] Loading extension /usr/local/lib/nusqlite3/libnusqlite3.so > > [2025-06-08 12:27:32.603] INFO: [Database] Successfully loaded extension /usr/local/lib/nusqlite3/libnusqlite3.so > > [2025-06-08 12:27:32.604] INFO: [Database] Db supports unaccent and unicode foldings > > [2025-06-08 12:27:32.604] INFO: [Database] Db connection was successful > > [2025-06-08 12:27:32.619] INFO: [MigrationManager] Database is already up to date. > > [2025-06-08 12:27:32.820] INFO: [Database] Db initialized with models: user, library, libraryFolder, book, podcast, podcastEpisode, libraryItem, mediaProgress, series, bookSeries, author, bookAuthor, collection, collectionBook, playlist, playlistMediaItem, device, playbackSession, feed, feedEpisode, setting, customMetadataProvider, mediaItemShare > > [2025-06-08 12:27:33.239] INFO: [Database] running ANALYZE > > [2025-06-08 12:27:33.317] INFO: [Database] ANALYZE completed > > ``` > > DB browser uses an old version of SQLite which is not compatible with updates to ABS. [#4134](https://github.com/advplyr/audiobookshelf/issues/4134) Gotcha, what program are you using in your screenshot above then?

adam commented

@advplyr commented on GitHub (Jun 8, 2025):

I'm using DBeaver on Windows

@advplyr commented on GitHub (Jun 8, 2025): I'm using DBeaver on Windows

adam commented

@WillGunn commented on GitHub (Jun 8, 2025):

I'm using DBeaver on Windows

That works, it appears that the date there isn't being updated:

compared to my user's listening sessions:

@WillGunn commented on GitHub (Jun 8, 2025): > I'm using DBeaver on Windows That works, it appears that the date there isn't being updated: ![Image](https://github.com/user-attachments/assets/807b96e1-889d-4272-b672-e00b7d4f1b77) compared to my user's listening sessions: ![Image](https://github.com/user-attachments/assets/a4125190-29ec-4079-93db-ccfc60f5ae76)

adam commented

@advplyr commented on GitHub (Jun 8, 2025):

What about the playbackSessions table? In that table you will see the mediaItemId column and you can take the UUID in that column and search for it in the mediaProgresses table. Then you can make sure the playback session you are seeing in the web client is linked to a media progress item in the database.

@advplyr commented on GitHub (Jun 8, 2025): What about the `playbackSessions` table? In that table you will see the `mediaItemId` column and you can take the UUID in that column and search for it in the `mediaProgresses` table. Then you can make sure the playback session you are seeing in the web client is linked to a media progress item in the database.

adam commented

@WillGunn commented on GitHub (Jun 8, 2025):

What about the playbackSessions table? In that table you will see the mediaItemId column and you can take the UUID in that column and search for it in the mediaProgresses table. Then you can make sure the playback session you are seeing in the web client is linked to a media progress item in the database.

the mediaItemId in playbackSessions does indeed match the id in mediaProgresses

This is my first time using dbeaver so I'm not sure if its just showing foreign key to primary key matches, but in the Diagram tab for the tables, they aren't connected.

@WillGunn commented on GitHub (Jun 8, 2025): > What about the `playbackSessions` table? In that table you will see the `mediaItemId` column and you can take the UUID in that column and search for it in the `mediaProgresses` table. Then you can make sure the playback session you are seeing in the web client is linked to a media progress item in the database. the `mediaItemId` in `playbackSessions` does indeed match the id in `mediaProgresses` This is my first time using dbeaver so I'm not sure if its just showing foreign key to primary key matches, but in the Diagram tab for the tables, they aren't connected. ![Image](https://github.com/user-attachments/assets/4ef524a9-b38a-4a7e-b845-937d13ae9cad) ![Image](https://github.com/user-attachments/assets/0940a70c-7887-4f4b-bdbb-7a1ec9a86e79)

adam commented

@WillGunn commented on GitHub (Jun 8, 2025):

playback sessions filtered to a book showing a couple dozen since the updatedAt timestamp in media progresses:

@WillGunn commented on GitHub (Jun 8, 2025): playback sessions filtered to a book showing a couple dozen since the updatedAt timestamp in media progresses: ![Image](https://github.com/user-attachments/assets/045a7d17-b5cc-4411-ae37-72ef5738bde0) ![Image](https://github.com/user-attachments/assets/f4d05eaf-02ac-4943-90d2-3bdc2e944d01)

adam commented

@advplyr commented on GitHub (Jun 8, 2025):

The diagram is normal because that column is a polymorphic association to books and podcastEpisodes.

I was doing some testing with DBeaver on my production server database and it looks like the sqlite driver in DBeaver isn't updating the records after the initial connection when I'm connecting over a network drive.

I got SQlite studio and tested with that and can see that the updatedAt time is updating every 10 seconds (first sync is after 30 seconds) while listening in the browser.

Are you accessing the database over a network drive with DBeaver?

@advplyr commented on GitHub (Jun 8, 2025): The diagram is normal because that column is a polymorphic association to `books` and `podcastEpisodes`. I was doing some testing with DBeaver on my production server database and it looks like the sqlite driver in DBeaver isn't updating the records after the initial connection when I'm connecting over a network drive. I got SQlite studio and tested with that and can see that the `updatedAt` time is updating every 10 seconds (first sync is after 30 seconds) while listening in the browser. Are you accessing the database over a network drive with DBeaver?

adam commented

@WillGunn commented on GitHub (Jun 9, 2025):

The diagram is normal because that column is a polymorphic association to books and podcastEpisodes.

I was doing some testing with DBeaver on my production server database and it looks like the sqlite driver in DBeaver isn't updating the records after the initial connection when I'm connecting over a network drive.

I got SQlite studio and tested with that and can see that the updatedAt time is updating every 10 seconds (first sync is after 30 seconds) while listening in the browser.

Are you accessing the database over a network drive with DBeaver?

No, I shut the container down, then copied the db file to my local windows machine to view.

@WillGunn commented on GitHub (Jun 9, 2025): > The diagram is normal because that column is a polymorphic association to `books` and `podcastEpisodes`. > > I was doing some testing with DBeaver on my production server database and it looks like the sqlite driver in DBeaver isn't updating the records after the initial connection when I'm connecting over a network drive. > > I got SQlite studio and tested with that and can see that the `updatedAt` time is updating every 10 seconds (first sync is after 30 seconds) while listening in the browser. > > Are you accessing the database over a network drive with DBeaver? No, I shut the container down, then copied the db file to my local windows machine to view.

adam commented

@WillGunn commented on GitHub (Jun 9, 2025):

Ok, I listened for more than 30 seconds in the browser and it moved that item to the top of the continue listening queue, so it does work from the browser. I believe it used to move it immediately with any amount of listening, but this is fine.

My main listening source is via the official ios app via testflight, and that does not appear to update the list anymore. I usually start a book then immediately put the app into the background, but for a test I left it open for more than 30 seconds and it did not update the continue listening list order.

@WillGunn commented on GitHub (Jun 9, 2025): Ok, I listened for more than 30 seconds in the browser and it moved that item to the top of the continue listening queue, so it does work from the browser. I believe it used to move it immediately with any amount of listening, but this is fine. My main listening source is via the official ios app via testflight, and that does not appear to update the list anymore. I usually start a book then immediately put the app into the background, but for a test I left it open for more than 30 seconds and it did not update the continue listening list order.

adam commented

@Xelis commented on GitHub (Jun 13, 2025):

Having the same issue, I use the android app and once it connects to the server it switches the order to whatever order it was set to after I updated. Something isn't syncing up right between the apps and the server.

@Xelis commented on GitHub (Jun 13, 2025): Having the same issue, I use the android app and once it connects to the server it switches the order to whatever order it was set to after I updated. Something isn't syncing up right between the apps and the server.

adam commented

@advplyr commented on GitHub (Jun 13, 2025):

Are these books you have downloaded to the device? That would be a separate issue than we have been investigating if that is the case

@advplyr commented on GitHub (Jun 13, 2025): Are these books you have downloaded to the device? That would be a separate issue than we have been investigating if that is the case

adam commented

@Xelis commented on GitHub (Jun 14, 2025):

Yeah, if I play downloaded books the server doesn't update the order, if I stream a book it goes to the front as you'd expect.

EDIT: Downgraded to 2.23.0 and its working as expected now.

@Xelis commented on GitHub (Jun 14, 2025): Yeah, if I play downloaded books the server doesn't update the order, if I stream a book it goes to the front as you'd expect. EDIT: Downgraded to 2.23.0 and its working as expected now.

adam commented

@WillGunn commented on GitHub (Jun 16, 2025):

I basically only listen to books that I have downloaded, but yes it looks like if I delete the local file, then stream it, it does update the Continue Listening order correctly.

@WillGunn commented on GitHub (Jun 16, 2025): I basically only listen to books that I have downloaded, but yes it looks like if I delete the local file, then stream it, it does update the Continue Listening order correctly.

adam commented

@lcharlick commented on GitHub (Jul 1, 2025):

@advplyr fairly sure this is caused by your change here. In cases where lastUpdate is provided (i.e. for local/offline sessions), updatedAt isn't being updated at all. I'm guessing sequelize skips updating that field altogether if silent: true is provided as an option.

I had a quick go at fixing it, but couldn't find a way to force sequelize to a) take the custom lastUpdate value and b) not clobber the value on save.

@lcharlick commented on GitHub (Jul 1, 2025): @advplyr fairly sure this is caused by your change [here](https://github.com/advplyr/audiobookshelf/commit/6d1f0b27df782b464de8cb3d04c51b02b34c91d5#diff-f0acc5224705f55de092f859d97f073b49c869c301634e135bc10ff1300a8ba5R252). In cases where `lastUpdate` is provided (i.e. for local/offline sessions), `updatedAt` isn't being updated at all. I'm guessing sequelize skips updating that field altogether if `silent: true` is provided as an option. I had a quick go at fixing it, but couldn't find a way to force sequelize to a) take the custom `lastUpdate` value and b) not clobber the value on save.

adam commented

@advplyr commented on GitHub (Jul 2, 2025):

Thanks @lcharlick, that is correct. I was able to reproduce the issue and fix it but it did require an additional query. Described in #4454

@advplyr commented on GitHub (Jul 2, 2025): Thanks @lcharlick, that is correct. I was able to reproduce the issue and fix it but it did require an additional query. Described in #4454

adam commented

@WillGunn commented on GitHub (Jul 2, 2025):

Thanks @advplyr for the fix and @lcharlick for digging deeper than I had time to. Once a release is ready I'll test with my iOS app to validate.

Edit: Actually it looks like :edge should include the fix if I'm reading the build action right, let me go test that.

@WillGunn commented on GitHub (Jul 2, 2025): Thanks @advplyr for the fix and @lcharlick for digging deeper than I had time to. Once a release is ready I'll test with my iOS app to validate. Edit: Actually it looks like :edge should include the fix if I'm reading the build action right, let me go test that.

adam commented

@WillGunn commented on GitHub (Jul 2, 2025):

@advplyr can confirm that running :edge, the status from downloaded items on iOS is correctly updating Continue Watching again!

@WillGunn commented on GitHub (Jul 2, 2025): @advplyr can confirm that running :edge, the status from downloaded items on iOS is correctly updating Continue Watching again!

adam commented

@advplyr commented on GitHub (Jul 2, 2025):

Thanks for testing!

@advplyr commented on GitHub (Jul 2, 2025): Thanks for testing!

adam commented