Originally created by @UnixNight on GitHub (Nov 23, 2023).
Steps to reproduce
Have downloaded audiobook on v0.9.66
update to 0.9.67
open downloaded book
Expected behaviour
Audiobook should open as expected
Actual behaviour
White screen with the error "Attempted to assign to readonly property"
Environment data
Audiobookshelf Version: 2.5.0 docker
Android App?
iOS App?
Android Issue
Android version:
Device model:
Stock or customized system:
iOS Issue
iOS Version: 17.1.1
iPhone model: iPhone 14 Pro Max
Originally created by @UnixNight on GitHub (Nov 23, 2023).
### Steps to reproduce
1. Have downloaded audiobook on v0.9.66
2. update to 0.9.67
3. open downloaded book
### Expected behaviour
- Audiobook should open as expected
### Actual behaviour
- White screen with the error "Attempted to assign to readonly property"
### Environment data
Audiobookshelf Version: 2.5.0 docker
- [ ] Android App?
- [x] iOS App?
#### Android Issue
Android version:
Device model:
Stock or customized system:
#### iOS Issue
iOS Version: 17.1.1
iPhone model: iPhone 14 Pro Max
adam
added the bug label 2026-04-24 23:37:21 +02:00
I have a bunch of books downloaded on 0.9.66 and some podcast episodes and I couldn't reproduce this so this must be a specific case. I couldn't see any assignments being made to readonly properties in the update
@advplyr commented on GitHub (Nov 23, 2023):
I have a bunch of books downloaded on 0.9.66 and some podcast episodes and I couldn't reproduce this so this must be a specific case. I couldn't see any assignments being made to readonly properties in the update
I was able to view the files from the download page but accessing the book from the main view was still throwing an error
Does downloading the book again fix it?
@advplyr I misread this. Redownloading after deleting it from the Download page seems to have resolved this issue. Weird
@UnixNight commented on GitHub (Nov 23, 2023):
> Can you delete the item from the downloads page?
I was able to view the files from the download page but accessing the book from the main view was still throwing an error
> Does downloading the book again fix it?
@advplyr I misread this. Redownloading after deleting it from the Download page seems to have resolved this issue. Weird
Someone else mentioned this in Discord so unless that was you then you aren't the only one this happened to. I haven't been able to find a cause and so far it's too rare to have anything to go off of. Will re-open if more cases come up
@advplyr commented on GitHub (Nov 24, 2023):
Someone else mentioned this in Discord so unless that was you then you aren't the only one this happened to. I haven't been able to find a cause and so far it's too rare to have anything to go off of. Will re-open if more cases come up
I happened to come across this issue on a device that had a downloaded book that was downloaded on server v2.2.23 or below. Since it was downloaded on v2.2.23 or below it was using the old id before we switched to using UUIDs. This caused the issue.
The reason this is rare is because the item will have to have been downloaded on server <= v2.2.23 and you will have to be running a server now that is >= v2.3.0. This will be fixed in the next release but I still think users should re-download to get the UUIDs stored locally.
@advplyr commented on GitHub (Nov 25, 2023):
I happened to come across this issue on a device that had a downloaded book that was downloaded on server v2.2.23 or below. Since it was downloaded on v2.2.23 or below it was using the old id before we switched to using UUIDs. This caused the issue.
The reason this is rare is because the item will have to have been downloaded on server <= v2.2.23 and you will have to be running a server now that is >= v2.3.0. This will be fixed in the next release but I still think users should re-download to get the 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 @UnixNight on GitHub (Nov 23, 2023).
Steps to reproduce
Expected behaviour
Actual behaviour
Environment data
Audiobookshelf Version: 2.5.0 docker
Android Issue
Android version:
Device model:
Stock or customized system:
iOS Issue
iOS Version: 17.1.1
iPhone model: iPhone 14 Pro Max
@nichwall commented on GitHub (Nov 23, 2023):
Does downloading the book again fix it?
@UnixNight commented on GitHub (Nov 23, 2023):
Downgrading will just repeatedly crash the app unfortunately
@advplyr commented on GitHub (Nov 23, 2023):
Can you delete the item from the downloads page?
@advplyr commented on GitHub (Nov 23, 2023):
I have a bunch of books downloaded on 0.9.66 and some podcast episodes and I couldn't reproduce this so this must be a specific case. I couldn't see any assignments being made to readonly properties in the update
@UnixNight commented on GitHub (Nov 23, 2023):
I was able to view the files from the download page but accessing the book from the main view was still throwing an error
@advplyr I misread this. Redownloading after deleting it from the Download page seems to have resolved this issue. Weird
@advplyr commented on GitHub (Nov 24, 2023):
Someone else mentioned this in Discord so unless that was you then you aren't the only one this happened to. I haven't been able to find a cause and so far it's too rare to have anything to go off of. Will re-open if more cases come up
@UnixNight commented on GitHub (Nov 24, 2023):
That wasn't me. Hopefully it was just a weird edge case
@advplyr commented on GitHub (Nov 25, 2023):
I happened to come across this issue on a device that had a downloaded book that was downloaded on server v2.2.23 or below. Since it was downloaded on v2.2.23 or below it was using the old id before we switched to using UUIDs. This caused the issue.
The reason this is rare is because the item will have to have been downloaded on server <= v2.2.23 and you will have to be running a server now that is >= v2.3.0. This will be fixed in the next release but I still think users should re-download to get the UUIDs stored locally.
@UnixNight commented on GitHub (Nov 26, 2023):
Well that explains why my downloaded book suddenly stopped syncing with the book on the server
@advplyr commented on GitHub (Nov 27, 2023):
Fixed in v0.9.68-beta