Originally created by @tehniemer on GitHub (Oct 27, 2022).
Steps to reproduce
Download audiobook
Play for a while
Resume much later (>~12 hours?)
Expected behaviour
Progress resumes from most recent stopping point.
Actual behaviour
Progress resumes from stopping point prior to the most recent one, but only sometimes.
Environment data
I've noticed this behavior when using Android Auto to listen to audiobooks, it doesn't seem to happen 100% of the time and I'm not sure if it happens if the book is streamed from the server rather than downloaded and played.
Audiobookshelf Version:
[0.9.57-beta] Android App
Android Issue
Android version: 13
Device model: Pixel 6a
Stock or customized system: Stock
Originally created by @tehniemer on GitHub (Oct 27, 2022).
### Steps to reproduce
1. Download audiobook
2. Play for a while
3. Resume much later (>~12 hours?)
### Expected behaviour
- Progress resumes from most recent stopping point.
### Actual behaviour
- Progress resumes from stopping point prior to the most recent one, but only sometimes.
### Environment data
I've noticed this behavior when using Android Auto to listen to audiobooks, it doesn't seem to happen 100% of the time and I'm not sure if it happens if the book is streamed from the server rather than downloaded and played.
Audiobookshelf Version:
- [0.9.57-beta] Android App
#### Android Issue
Android version: 13
Device model: Pixel 6a
Stock or customized system: Stock
adam
added the bug label 2026-04-24 23:16:46 +02:00
This happens with downloaded books on iOS as well. I’m not sure about streaming since I always download. This happened frequently enough to me that I’ve stopped using ABS until it’s fixed.
@higbee4 commented on GitHub (Dec 4, 2022):
This happens with downloaded books on iOS as well. I’m not sure about streaming since I always download. This happened frequently enough to me that I’ve stopped using ABS until it’s fixed.
Connect phone to car bluetooth. Open app and press "play"
Before leaving the car, intentionally open the app, confirm that progress is up-to-date, and press pause.
Upon next time entering car, car automatically reconnects and resumes book, book resumes from the point at the beginning of the prior session (not the end).
@mikehoyle commented on GitHub (Dec 7, 2022):
I've repro'd this pretty consistently now, and have captured a bug-report containing two instances
Bug report is here: https://drive.google.com/file/d/1JELFM9DtqfuzI4bjOXe3MeYXQ3s7zBJj/view?usp=share_link
I haven't shared it broadly because it might contain sensitive data. Please request to view it or DM me an account to share it with and I will share.
Repro steps:
- Have book downloaded to device.
- Device is still network connected (mobile data)
- Connect phone to car bluetooth. Open app and press "play"
- Before leaving the car, intentionally open the app, confirm that progress is up-to-date, and press pause.
- Upon next time entering car, car automatically reconnects and resumes book, book resumes from the point at the beginning of the prior session (not the end).
I think I may have an idea of why this happens now. It is specific to downloaded books and would assume that the progress is not actually updated on the server.
@mikehoyle You are checking that the app is showing the correct progress but can you also verify that the server has the correct progress?
If you are keeping the app logged out of the server the whole time then that could explain it. Once you login it is going to sync that downloaded progress to the server.
@advplyr commented on GitHub (Dec 13, 2022):
I think I may have an idea of why this happens now. It is specific to downloaded books and would assume that the progress is not actually updated on the server.
@mikehoyle You are checking that the app is showing the correct progress but can you also verify that the server has the correct progress?
If you are keeping the app logged out of the server the whole time then that could explain it. Once you login it is going to sync that downloaded progress to the server.
Just in case this info helps. On iOS, I have cellular data turned off for ABS. And I listen to books I downloaded over Wi-Fi. If I listen to a book when I’m not on Wi-Fi there is no way for the client to communicate my position back to the server until I’m back on Wi-Fi. So it would have to know to send that data the next time I connect with the server and not depend solely on a real-time connection.
@higbee4 commented on GitHub (Dec 13, 2022):
Just in case this info helps. On iOS, I have cellular data turned off for ABS. And I listen to books I downloaded over Wi-Fi. If I listen to a book when I’m not on Wi-Fi there is no way for the client to communicate my position back to the server until I’m back on Wi-Fi. So it would have to know to send that data the next time I connect with the server and not depend solely on a real-time connection.
That’s good to know. I think I have run into this problem with downloaded books without ever leaving a Wi-Fi connection. So the fact I may be offline for extended periods of time may not be a relevant factor to the issue. I just thought I’d mention it in case it was. Thanks.
@higbee4 commented on GitHub (Dec 13, 2022):
That’s good to know. I think I have run into this problem with downloaded books without ever leaving a Wi-Fi connection. So the fact I may be offline for extended periods of time may not be a relevant factor to the issue. I just thought I’d mention it in case it was. Thanks.
I just ran into this again after updating to 0.9.61,
@tehniemer commented on GitHub (Feb 2, 2023):
I just ran into this again after updating to 0.9.61,


I've also run into this with 0.9.61 over the past couple days. It's almost as if the app forgets that the downloaded book is associated with the book on the server. The progress is tracked locally for the downloaded file, but the book is not added to the Continue Listening shelf and the progress is not set on the server.
I tried to download some new books to try to further determine the specific details of the bug, (start playing the first time from the downloaded file. download, exit app then play, etc.) but the new downloads all work as expected. So maybe it was just with books I downloaded before the 0.9.61 app update?
I'll keep poking at it to see if I can spot any patterns.
@RobinD42 commented on GitHub (Feb 2, 2023):
I've also run into this with 0.9.61 over the past couple days. It's almost as if the app forgets that the downloaded book is associated with the book on the server. The progress is tracked locally for the downloaded file, but the book is not added to the Continue Listening shelf and the progress is not set on the server.
I tried to download some new books to try to further determine the specific details of the bug, (start playing the first time from the downloaded file. download, exit app then play, etc.) but the new downloads all work as expected. So maybe it was just with books I downloaded before the 0.9.61 app update?
I'll keep poking at it to see if I can spot any patterns.
I've not seen it in 0.9.62. However, I wasn't able to reliably reproduce the issue before, so I can't say for sure that it's fixed.
@RobinD42 commented on GitHub (Feb 27, 2023):
I've not seen it in 0.9.62. However, I wasn't able to reliably reproduce the issue before, so I can't say for sure that it's fixed.
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 @tehniemer on GitHub (Oct 27, 2022).
Steps to reproduce
Expected behaviour
Actual behaviour
Environment data
I've noticed this behavior when using Android Auto to listen to audiobooks, it doesn't seem to happen 100% of the time and I'm not sure if it happens if the book is streamed from the server rather than downloaded and played.
Audiobookshelf Version:
Android Issue
Android version: 13
Device model: Pixel 6a
Stock or customized system: Stock
@higbee4 commented on GitHub (Dec 4, 2022):
This happens with downloaded books on iOS as well. I’m not sure about streaming since I always download. This happened frequently enough to me that I’ve stopped using ABS until it’s fixed.
@mikehoyle commented on GitHub (Dec 7, 2022):
I've repro'd this pretty consistently now, and have captured a bug-report containing two instances
Bug report is here: https://drive.google.com/file/d/1JELFM9DtqfuzI4bjOXe3MeYXQ3s7zBJj/view?usp=share_link
I haven't shared it broadly because it might contain sensitive data. Please request to view it or DM me an account to share it with and I will share.
Repro steps:
@advplyr commented on GitHub (Dec 13, 2022):
I think I may have an idea of why this happens now. It is specific to downloaded books and would assume that the progress is not actually updated on the server.
@mikehoyle You are checking that the app is showing the correct progress but can you also verify that the server has the correct progress?
If you are keeping the app logged out of the server the whole time then that could explain it. Once you login it is going to sync that downloaded progress to the server.
@higbee4 commented on GitHub (Dec 13, 2022):
Just in case this info helps. On iOS, I have cellular data turned off for ABS. And I listen to books I downloaded over Wi-Fi. If I listen to a book when I’m not on Wi-Fi there is no way for the client to communicate my position back to the server until I’m back on Wi-Fi. So it would have to know to send that data the next time I connect with the server and not depend solely on a real-time connection.
@advplyr commented on GitHub (Dec 13, 2022):
@higbee4 It should attempt to sync your offline progress whenever you connect back to the server
@higbee4 commented on GitHub (Dec 13, 2022):
That’s good to know. I think I have run into this problem with downloaded books without ever leaving a Wi-Fi connection. So the fact I may be offline for extended periods of time may not be a relevant factor to the issue. I just thought I’d mention it in case it was. Thanks.
@tehniemer commented on GitHub (Feb 2, 2023):
I just ran into this again after updating to 0.9.61,
@RobinD42 commented on GitHub (Feb 2, 2023):
I've also run into this with 0.9.61 over the past couple days. It's almost as if the app forgets that the downloaded book is associated with the book on the server. The progress is tracked locally for the downloaded file, but the book is not added to the Continue Listening shelf and the progress is not set on the server.
I tried to download some new books to try to further determine the specific details of the bug, (start playing the first time from the downloaded file. download, exit app then play, etc.) but the new downloads all work as expected. So maybe it was just with books I downloaded before the 0.9.61 app update?
I'll keep poking at it to see if I can spot any patterns.
@advplyr commented on GitHub (Feb 26, 2023):
Is this still happening in
0.9.62-beta? Possibly related to #462 and #464@RobinD42 commented on GitHub (Feb 27, 2023):
I've not seen it in 0.9.62. However, I wasn't able to reliably reproduce the issue before, so I can't say for sure that it's fixed.