Originally created by @YodaDaCoda on GitHub (Nov 19, 2023).
Steps to reproduce
Download an audiobook and start listening
Note that the page for the book says progress will not be synced
Login to the web application via browser and note that progress is still synced as the book continues playing
Expected behaviour
Progress should be synced, and there should not be a message saying progress will not be synced.
Actual behaviour
There is a message saying progress will not be synced, but progress is still synced.
Environment data
Audiobookshelf Version:
Android App?
iOS App?
Android Issue
Android version: 13
Device model: OnePlus 9 5G
Stock or customized system: Stock
iOS Issue
iOS Version:
iPhone model:
Originally created by @YodaDaCoda on GitHub (Nov 19, 2023).
### Steps to reproduce
1. Download an audiobook and start listening
3. Note that the page for the book says progress will not be synced
4. Login to the web application via browser and note that progress is still synced as the book continues playing
### Expected behaviour
- Progress should be synced, and there should not be a message saying progress will not be synced.
### Actual behaviour
- There is a message saying progress will not be synced, but progress is still synced.
### Environment data
Audiobookshelf Version:
- [x] Android App?
- [ ] iOS App?
#### Android Issue
Android version: 13
Device model: OnePlus 9 5G
Stock or customized system: Stock
#### iOS Issue
iOS Version:
iPhone model:

adam
added the bug label 2026-04-24 23:37:05 +02:00
This book was downloaded with v0.9.66 but the issue persists with a book freshly downloaded with v0.9.67
@YodaDaCoda commented on GitHub (Nov 19, 2023):
This book was downloaded with v0.9.66 but the issue persists with a book freshly downloaded with v0.9.67

I am on 0.9.6.7-beta (2.5.0 server) and I am getting that prompt on previously downloaded books and newly downloaded books. Progress appears to be retained.
Stock Android (motorola edge, android 11, security updates August 1 2022, Play System Updates October 1 2023), no root, app from Play Store.
@kucksdorfs commented on GitHub (Nov 19, 2023):
I am on 0.9.6.7-beta (2.5.0 server) and I am getting that prompt on previously downloaded books and newly downloaded books. Progress appears to be retained.
Stock Android (motorola edge, android 11, security updates August 1 2022, Play System Updates October 1 2023), no root, app from Play Store.
I just realized what this probably is. You setup your connection on server v2.2.23 or below before we switched to UUIDs. So the user id stored on your device is the old user id and no longer matches the new one on your server.
To fix this I suggest you logout on the device, delete your existing connection and create a new one. New downloads should show that they are correctly linked.
@advplyr commented on GitHub (Nov 19, 2023):
I just realized what this probably is. You setup your connection on server v2.2.23 or below before we switched to UUIDs. So the user id stored on your device is the old user id and no longer matches the new one on your server.
To fix this I suggest you logout on the device, delete your existing connection and create a new one. New downloads should show that they are correctly linked.
To fix this I suggest you logout on the device, delete your existing connection and create a new one. New downloads should show that they are correctly linked.
So I am fine doing this, but will I think this is unrealistic if people have a lot of books downloaded. Or its "expensive" to download books (in terms of time for example).
@kucksdorfs commented on GitHub (Nov 19, 2023):
> To fix this I suggest you logout on the device, delete your existing connection and create a new one. New downloads should show that they are correctly linked.
So I am fine doing this, but will I think this is unrealistic if people have a lot of books downloaded. Or its "expensive" to download books (in terms of time for example).
I can push up a fix in the next update. Progress will still be synced properly for all of those items because the server knows how to handle the old user ids. The main issue is that the alert is confusing and misleading.
I still recommend updating the server connection so you have the new UUIDs stored locally.
@advplyr commented on GitHub (Nov 19, 2023):
I can push up a fix in the next update. Progress will still be synced properly for all of those items because the server knows how to handle the old user ids. The main issue is that the alert is confusing and misleading.
I still recommend updating the server connection so you have the new UUIDs stored locally.
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 @YodaDaCoda on GitHub (Nov 19, 2023).
Steps to reproduce
Expected behaviour
Actual behaviour
Environment data
Audiobookshelf Version:
Android Issue
Android version: 13
Device model: OnePlus 9 5G
Stock or customized system: Stock
iOS Issue
iOS Version:
iPhone model:
@nichwall commented on GitHub (Nov 19, 2023):
Was this book downloaded before 0.9.67? Does redownloading the book fix the message?
@YodaDaCoda commented on GitHub (Nov 19, 2023):
This book was downloaded with v0.9.66 but the issue persists with a book freshly downloaded with v0.9.67
@kucksdorfs commented on GitHub (Nov 19, 2023):
I am on 0.9.6.7-beta (2.5.0 server) and I am getting that prompt on previously downloaded books and newly downloaded books. Progress appears to be retained.
Stock Android (motorola edge, android 11, security updates August 1 2022, Play System Updates October 1 2023), no root, app from Play Store.
@advplyr commented on GitHub (Nov 19, 2023):
I just realized what this probably is. You setup your connection on server v2.2.23 or below before we switched to UUIDs. So the user id stored on your device is the old user id and no longer matches the new one on your server.
To fix this I suggest you logout on the device, delete your existing connection and create a new one. New downloads should show that they are correctly linked.
@kucksdorfs commented on GitHub (Nov 19, 2023):
So I am fine doing this, but will I think this is unrealistic if people have a lot of books downloaded. Or its "expensive" to download books (in terms of time for example).
@advplyr commented on GitHub (Nov 19, 2023):
I can push up a fix in the next update. Progress will still be synced properly for all of those items because the server knows how to handle the old user ids. The main issue is that the alert is confusing and misleading.
I still recommend updating the server connection so you have the new UUIDs stored locally.
@advplyr commented on GitHub (Nov 27, 2023):
Fixed in v0.9.68-beta