Originally created by @lkiesow on GitHub (Jan 29, 2023).
I have seen several times that I finished an audiobook, the playback will stop, but the progress in the book details will not have marked it as finished. It will usually still say that a few seconds are remaining:
My guess would be that one of the following things happens:
The book is finished and the final (regular) progress update is not somehow cancelled.
The media file container metadata are a few seconds off. This is not uncommon, especially for files with a variable bit rate. ABS thinks the playtime is a few seconds longer and therefor never marks it as finished.
An indicator for the latter theory is that this seems to happen more often with books contained in one large file, which are usually more likely to suffer from inaccurate duration metadata.
In the end, ABS should just always mark a book as finished as soon as the playback of the last chapter stops.
Originally created by @lkiesow on GitHub (Jan 29, 2023).
I have seen several times that I finished an audiobook, the playback will stop, but the progress in the book details will not have marked it as finished. It will usually still say that a few seconds are remaining:
<img width="300px" src="https://user-images.githubusercontent.com/1008395/215295436-8e20b225-ee6a-402a-97c7-efce638795a7.jpg" />
My guess would be that one of the following things happens:
- The book is finished and the final (regular) progress update is not somehow cancelled.
- The media file container metadata are a few seconds off. This is not uncommon, especially for files with a variable bit rate. ABS thinks the playtime is a few seconds longer and therefor never marks it as finished.
An indicator for the latter theory is that this seems to happen more often with books contained in one large file, which are usually more likely to suffer from inaccurate duration metadata.
In the end, ABS should just always mark a book as finished as soon as the playback of the last chapter stops.
#### Android Issue
App version: 0.9.60-beta
Android version: 12
Device model: OnePlus Nord 2
adam
added the bug label 2026-04-24 23:20:27 +02:00
I have the exact same issue on the latest iOS app and server 2.9.0. All finished books remain in Continue Listening with random remaining time (7 sec, 3 sec, etc). It's extremely annoying as you have to manually mark each book as finished every time. It happens for both single file audio as well as multiple files regardless of file format (mp3, m4b, etc.).
It's disheartening that this issue has remained unadressed for over 1 year without even an acknowledgement, this is a core functionality which is not working properly.
@orosoiu commented on GitHub (Apr 25, 2024):
I have the exact same issue on the latest iOS app and server 2.9.0. All finished books remain in Continue Listening with random remaining time (7 sec, 3 sec, etc). It's extremely annoying as you have to manually mark each book as finished every time. It happens for both single file audio as well as multiple files regardless of file format (mp3, m4b, etc.).

It's disheartening that this issue has remained unadressed for over 1 year without even an acknowledgement, this is a core functionality which is not working properly.
The best way to show support for a feature request is a "thumbs up" on the top comment. When looking for features to implement, issues are sorted by the number of reactions.
@nichwall commented on GitHub (Apr 26, 2024):
The best way to show support for a feature request is a "thumbs up" on the top comment. When looking for features to implement, issues are sorted by the number of reactions.
Related: https://github.com/advplyr/audiobookshelf/issues/837
This isn't a feature request though, it's a bug. Books finished on a mobile device (iOS in my case) don't get marked as finished on the server and remain in Continue Playing with a random number of seconds remaining.
@orosoiu commented on GitHub (Apr 30, 2024):
This isn't a feature request though, it's a bug. Books finished on a mobile device (iOS in my case) don't get marked as finished on the server and remain in Continue Playing with a random number of seconds remaining.
@DavidPesticcio commented on GitHub (Jul 14, 2025):
@lkiesow @orosoiu Is this still the case?
I am not seeing this with ABS v2.26.0 (docker) / 0.9.81-beta (Android 12)
@DavidPesticcio commented on GitHub (Jul 14, 2025):
@lkiesow @orosoiu Is this still the case?
I am not seeing this with ABS v2.26.0 (docker) / 0.9.81-beta (Android 12)
I see this normally, most books I finish, go back to main page, and then find it only mostly finished but no longer at the top of the page (like it recognized the finish, but then lost the last play session - although I can't confirm it actually lost that).
@wtanksleyjr commented on GitHub (Sep 5, 2025):
I see this normally, most books I finish, go back to main page, and then find it only mostly finished but no longer at the top of the page (like it recognized the finish, but then lost the last play session - although I can't confirm it actually lost that).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @lkiesow on GitHub (Jan 29, 2023).
I have seen several times that I finished an audiobook, the playback will stop, but the progress in the book details will not have marked it as finished. It will usually still say that a few seconds are remaining:
My guess would be that one of the following things happens:
An indicator for the latter theory is that this seems to happen more often with books contained in one large file, which are usually more likely to suffer from inaccurate duration metadata.
In the end, ABS should just always mark a book as finished as soon as the playback of the last chapter stops.
Android Issue
App version: 0.9.60-beta
Android version: 12
Device model: OnePlus Nord 2
@orosoiu commented on GitHub (Apr 25, 2024):
I have the exact same issue on the latest iOS app and server 2.9.0. All finished books remain in Continue Listening with random remaining time (7 sec, 3 sec, etc). It's extremely annoying as you have to manually mark each book as finished every time. It happens for both single file audio as well as multiple files regardless of file format (mp3, m4b, etc.).
It's disheartening that this issue has remained unadressed for over 1 year without even an acknowledgement, this is a core functionality which is not working properly.
@nichwall commented on GitHub (Apr 26, 2024):
The best way to show support for a feature request is a "thumbs up" on the top comment. When looking for features to implement, issues are sorted by the number of reactions.
Related: https://github.com/advplyr/audiobookshelf/issues/837
@orosoiu commented on GitHub (Apr 30, 2024):
This isn't a feature request though, it's a bug. Books finished on a mobile device (iOS in my case) don't get marked as finished on the server and remain in Continue Playing with a random number of seconds remaining.
@DavidPesticcio commented on GitHub (Jul 14, 2025):
@lkiesow @orosoiu Is this still the case?
I am not seeing this with ABS v2.26.0 (docker) / 0.9.81-beta (Android 12)
@orosoiu commented on GitHub (Jul 14, 2025):
I haven't used the app since, so can't confirm one way or the other. Will post here if it happens again.
@wtanksleyjr commented on GitHub (Sep 5, 2025):
I see this normally, most books I finish, go back to main page, and then find it only mostly finished but no longer at the top of the page (like it recognized the finish, but then lost the last play session - although I can't confirm it actually lost that).