Originally created by @clockwinder on GitHub (Jul 31, 2023).
Steps to reproduce
Audiobook originally stored at /audiobooks/J.K. Rowling/1 - Harry Potter and the Philosophers Stone/01 Chapter 01 - The Boy Who Lived.mp3 or similar, I don't remember the exact structure.
File cached and played properly on android.
Audiobook moved to /audiobooks/J.K. Rowling/Harry Potter - Stephen Fry/1 - Harry Potter and the Philosophers Stone/01 Chapter 01 - The Boy Who Lived.mp3 and library rescanned.
When file is cached in the android app, the file is put in Download/Audiobook/J.K. Rowling/Harry Potter and the Philosophers Stone, Book 1/01 Chapter 01 - The Boy Who Lived.mp3
One android device attempts to play the cache and crashes after 2-3 seconds, another android device throws an error Item download complete but failed to create library item
Expected behaviour
I expect the file to cache in the same new directory structure as the server.
Actual behaviour
The file appears to be cached in the wrong location which might be the source of the error/crash?
Environment data
Audiobookshelf Version: v2.3.2
Android App
Android Issue
Android version: 0.9.65-beta
Device model: Moto G7 Power
Stock or customized system: LineageOS 20
Originally created by @clockwinder on GitHub (Jul 31, 2023).
### Steps to reproduce
1. Audiobook originally stored at `/audiobooks/J.K. Rowling/1 - Harry Potter and the Philosophers Stone/01 Chapter 01 - The Boy Who Lived.mp3` or similar, I don't remember the exact structure.
2. File cached and played properly on android.
3. Audiobook moved to `/audiobooks/J.K. Rowling/Harry Potter - Stephen Fry/1 - Harry Potter and the Philosophers Stone/01 Chapter 01 - The Boy Who Lived.mp3` and library rescanned.
4. When file is cached in the android app, the file is put in `Download/Audiobook/J.K. Rowling/Harry Potter and the Philosophers Stone, Book 1/01 Chapter 01 - The Boy Who Lived.mp3`
5. One android device attempts to play the cache and crashes after 2-3 seconds, another android device throws an error `Item download complete but failed to create library item`
### Expected behaviour
- I expect the file to cache in the same new directory structure as the server.
### Actual behaviour
- The file appears to be cached in the wrong location which might be the source of the error/crash?
### Environment data
Audiobookshelf Version: v2.3.2
Android App
#### Android Issue
Android version: 0.9.65-beta
Device model: Moto G7 Power
Stock or customized system: LineageOS 20
adam
added the bug label 2026-04-24 23:32:53 +02:00
Forcing a re-scan of the full audiobook library did not fix the issue, the app still crashes when attempting to play the cached audiobook.
@clockwinder commented on GitHub (Aug 3, 2023):
Forcing a re-scan of the full audiobook library did not fix the issue, the app still crashes when attempting to play the cached audiobook.
The file structure on the device is not going to match the file structure on the server. This seems like unnecessary extra work. I'll most likely remove the scan options to avoid confusion in the future
@advplyr commented on GitHub (Sep 11, 2023):
The file structure on the device is not going to match the file structure on the server. This seems like unnecessary extra work. I'll most likely remove the scan options to avoid confusion in the future
Sorry if it seemed like I was asking for something to be changed.
I just want to know how to fix the crash I'm having on my end.
@clockwinder commented on GitHub (Sep 12, 2023):
Sorry if it seemed like I was asking for something to be changed.
I just want to know how to fix the crash I'm having on my end.
You'll have to delete the item from inside the app local downloads page. Or clear data from the app and delete the downloads from your file system and re-download.
@advplyr commented on GitHub (Sep 12, 2023):
You'll have to delete the item from inside the app local downloads page. Or clear data from the app and delete the downloads from your file system and re-download.
Re-downloading from what structure? I don't recommend using the "Scan" feature at all. After it downloads it shouldn't be moved on the file system.
@advplyr commented on GitHub (Sep 12, 2023):
Re-downloading from what structure? I don't recommend using the "Scan" feature at all. After it downloads it shouldn't be moved on the file system.
I'm sorry the the confusion, I'm not familiar with the terminology you use on this project.
I just deleted the cached audiobook from my android device, then redownloaded it. When I go to play the cached file on my android device it plays ~1 second of audio and crashes.
This is the only book for which this happens, and it only started happening after I re-arranged files on the server end. if streaming the audio (not cached), it does not crash.
@clockwinder commented on GitHub (Sep 12, 2023):
I'm sorry the the confusion, I'm not familiar with the terminology you use on this project.
I just deleted the cached audiobook from my android device, then redownloaded it. When I go to play the cached file on my android device it plays ~1 second of audio and crashes.
This is the only book for which this happens, and it only started happening after I re-arranged files on the server end. if streaming the audio (not cached), it does not crash.
There is no good way to get logs for the app. I'm not sure what the problem could be. I would recommend copying the audio files on your server to create a new book to test with. Try downloading the new book and narrowing down what is going on.
@advplyr commented on GitHub (Sep 12, 2023):
There is no good way to get logs for the app. I'm not sure what the problem could be. I would recommend copying the audio files on your server to create a new book to test with. Try downloading the new book and narrowing down what is going on.
Okay, I copied the book in question to a new directory:
Then I used the scan feature (I see above you say to not use that, but I don't understand how to manually update the library without that), and the book showed up under recently added. So I cached it on the android device and when I went to play the file it played ~2 seconds of the file then the app crashed.
@clockwinder commented on GitHub (Sep 12, 2023):
Okay, I copied the book in question to a new directory:

Then I used the scan feature (I see above you say to not use that, but I don't understand how to manually update the library without that), and the book showed up under recently added. So I cached it on the android device and when I went to play the file it played ~2 seconds of the file then the app crashed.
What about if you replace those audio files with audio files from another book that you know are already working
@advplyr commented on GitHub (Sep 12, 2023):
What about if you replace those audio files with audio files from another book that you know are already working
I deleted the audio files in the new test folder, replaced them with audio files from another audiobook, then when I went to cache the audiofiles from my android device I got "Item download complete but failed to create library item". So I ssume there's a metadata mixup?
Did I miss a step in that test?
@clockwinder commented on GitHub (Sep 12, 2023):
I deleted the audio files in the new test folder, replaced them with audio files from another audiobook, then when I went to cache the audiofiles from my android device I got "Item download complete but failed to create library item". So I ssume there's a metadata mixup?
Did I miss a step in that test?
On the non-test version of the book, I cached again and tried playing a file for a later chapter in the book, and the crash happened as well. In case you were thinking there was a problem with the file/s.
@clockwinder commented on GitHub (Sep 12, 2023):
On the non-test version of the book, I cached again and tried playing a file for a later chapter in the book, and the crash happened as well. In case you were thinking there was a problem with the file/s.
I'm not sure if this is relevant, but I have noticed since enabling "Store metadata with item", that there are plenty of directories without an .abs file in them.
Okay, I've tried deleting the book from the system and re-adding it, which does not work. I've taken the first audio file and added it under a new book title, which allowed that file to play, but as soon as I put the matadata back to what was accurate, I had the crash again.
@clockwinder commented on GitHub (Sep 12, 2023):
I'm not sure if this is relevant, but I have noticed since enabling "Store metadata with item", that there are plenty of directories without an .abs file in them.
Okay, I've tried deleting the book from the system and re-adding it, which does not work. I've taken the first audio file and added it under a new book title, which allowed that file to play, but as soon as I put the matadata back to what was accurate, I had the crash again.
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 @clockwinder on GitHub (Jul 31, 2023).
Steps to reproduce
/audiobooks/J.K. Rowling/1 - Harry Potter and the Philosophers Stone/01 Chapter 01 - The Boy Who Lived.mp3or similar, I don't remember the exact structure./audiobooks/J.K. Rowling/Harry Potter - Stephen Fry/1 - Harry Potter and the Philosophers Stone/01 Chapter 01 - The Boy Who Lived.mp3and library rescanned.Download/Audiobook/J.K. Rowling/Harry Potter and the Philosophers Stone, Book 1/01 Chapter 01 - The Boy Who Lived.mp3Item download complete but failed to create library itemExpected behaviour
Actual behaviour
Environment data
Audiobookshelf Version: v2.3.2
Android App
Android Issue
Android version: 0.9.65-beta
Device model: Moto G7 Power
Stock or customized system: LineageOS 20
@clockwinder commented on GitHub (Aug 3, 2023):
Forcing a re-scan of the full audiobook library did not fix the issue, the app still crashes when attempting to play the cached audiobook.
@advplyr commented on GitHub (Sep 11, 2023):
The file structure on the device is not going to match the file structure on the server. This seems like unnecessary extra work. I'll most likely remove the scan options to avoid confusion in the future
@clockwinder commented on GitHub (Sep 12, 2023):
Sorry if it seemed like I was asking for something to be changed.
I just want to know how to fix the crash I'm having on my end.
@advplyr commented on GitHub (Sep 12, 2023):
You'll have to delete the item from inside the app local downloads page. Or clear data from the app and delete the downloads from your file system and re-download.
@clockwinder commented on GitHub (Sep 12, 2023):
Yes, I have done that. After re-downloading the file from the new structure, the crash persists.
@advplyr commented on GitHub (Sep 12, 2023):
Re-downloading from what structure? I don't recommend using the "Scan" feature at all. After it downloads it shouldn't be moved on the file system.
@clockwinder commented on GitHub (Sep 12, 2023):
I'm sorry the the confusion, I'm not familiar with the terminology you use on this project.
I just deleted the cached audiobook from my android device, then redownloaded it. When I go to play the cached file on my android device it plays ~1 second of audio and crashes.
This is the only book for which this happens, and it only started happening after I re-arranged files on the server end. if streaming the audio (not cached), it does not crash.
@clockwinder commented on GitHub (Sep 12, 2023):
Is there a way I can provide logs from the app to help?
@advplyr commented on GitHub (Sep 12, 2023):
There is no good way to get logs for the app. I'm not sure what the problem could be. I would recommend copying the audio files on your server to create a new book to test with. Try downloading the new book and narrowing down what is going on.
@clockwinder commented on GitHub (Sep 12, 2023):
Okay, I copied the book in question to a new directory:

Then I used the scan feature (I see above you say to not use that, but I don't understand how to manually update the library without that), and the book showed up under recently added. So I cached it on the android device and when I went to play the file it played ~2 seconds of the file then the app crashed.
@advplyr commented on GitHub (Sep 12, 2023):
What about if you replace those audio files with audio files from another book that you know are already working
@clockwinder commented on GitHub (Sep 12, 2023):
I deleted the audio files in the new test folder, replaced them with audio files from another audiobook, then when I went to cache the audiofiles from my android device I got "Item download complete but failed to create library item". So I ssume there's a metadata mixup?
Did I miss a step in that test?
@clockwinder commented on GitHub (Sep 12, 2023):
On the non-test version of the book, I cached again and tried playing a file for a later chapter in the book, and the crash happened as well. In case you were thinking there was a problem with the file/s.
@clockwinder commented on GitHub (Sep 12, 2023):
I'm not sure if this is relevant, but I have noticed since enabling "Store metadata with item", that there are plenty of directories without an .abs file in them.
Okay, I've tried deleting the book from the system and re-adding it, which does not work. I've taken the first audio file and added it under a new book title, which allowed that file to play, but as soon as I put the matadata back to what was accurate, I had the crash again.