The mobile app will not stream the audio book. It works fine with using the web client on PC or mobile. Additionally, it gives a source error when trying to play after the audiobook has been downloaded. The following warning comes up in the logs.
File path does not exist /metadata/streams/39ae5f8c-60ed-4076-bdc3-d06334c86057/output-641.ts
What the logs show from successfully streaming from web client
Originally created by @wildcat1115 on GitHub (Oct 7, 2025).
### I have verified that the [bug is not already awaiting release](https://github.com/advplyr/audiobookshelf-app/issues?q=is%3Aissue%20label%3A%22awaiting%20release%22)
Yes
### What was the Problem?
The mobile app will not stream the audio book. It works fine with using the web client on PC or mobile. Additionally, it gives a source error when trying to play after the audiobook has been downloaded. The following warning comes up in the logs.
File path does not exist /metadata/streams/39ae5f8c-60ed-4076-bdc3-d06334c86057/output-641.ts
What the logs show from successfully streaming from web client
[INFO] FFMPEG transcoding started with command: ffmpeg -seek_timestamp 1 -f concat -safe 0 -ss 3129.9s -noaccurate_seek -i /metadata/streams/39ae5f8c-60ed-4076-bdc3-d06334c86057/files.txt -y -loglevel error -map 0:a -c:a copy -f hls -copyts -avoid_negative_ts make_non_negative -max_delay 5000000 -max_muxing_queue_size 2048 -hls_time 6 -hls_segment_type mpegts -start_number 636 -hls_playlist_type vod -hls_list_size 0 -hls_allow_cache 0 -hls_segment_filename /metadata/streams/39ae5f8c-60ed-4076-bdc3-d06334c86057/output-%d.ts /metadata/streams/39ae5f8c-60ed-4076-bdc3-d06334c86057/final-output.m3u8
### Steps to Reproduce the Issue
1. Try to play the audiobook on the mobile app
### What was Expected?
To play the audiobook
### Phone Model
Samsung Galaxy S21FE
### Phone OS
Android 15
### Audiobookshelf App Version
Android App - 0.10.1
### Installation Source
Google Play Store
### Additional Notes
_No response_
The audiobook was The Silmarillion from the Internet Archive.
The issue seems to resolved itself after an update. Thank you for looking into it though!
@wildcat1115 commented on GitHub (Nov 14, 2025):
Hello,
The audiobook was The Silmarillion from the Internet Archive.
The issue seems to resolved itself after an update. Thank you for looking into it though!
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 @wildcat1115 on GitHub (Oct 7, 2025).
I have verified that the bug is not already awaiting release
Yes
What was the Problem?
The mobile app will not stream the audio book. It works fine with using the web client on PC or mobile. Additionally, it gives a source error when trying to play after the audiobook has been downloaded. The following warning comes up in the logs.
File path does not exist /metadata/streams/39ae5f8c-60ed-4076-bdc3-d06334c86057/output-641.ts
What the logs show from successfully streaming from web client
[INFO] FFMPEG transcoding started with command: ffmpeg -seek_timestamp 1 -f concat -safe 0 -ss 3129.9s -noaccurate_seek -i /metadata/streams/39ae5f8c-60ed-4076-bdc3-d06334c86057/files.txt -y -loglevel error -map 0:a -c:a copy -f hls -copyts -avoid_negative_ts make_non_negative -max_delay 5000000 -max_muxing_queue_size 2048 -hls_time 6 -hls_segment_type mpegts -start_number 636 -hls_playlist_type vod -hls_list_size 0 -hls_allow_cache 0 -hls_segment_filename /metadata/streams/39ae5f8c-60ed-4076-bdc3-d06334c86057/output-%d.ts /metadata/streams/39ae5f8c-60ed-4076-bdc3-d06334c86057/final-output.m3u8
Steps to Reproduce the Issue
What was Expected?
To play the audiobook
Phone Model
Samsung Galaxy S21FE
Phone OS
Android 15
Audiobookshelf App Version
Android App - 0.10.1
Installation Source
Google Play Store
Additional Notes
No response
@advplyr commented on GitHub (Nov 13, 2025):
can you provide info on the audiobook
@wildcat1115 commented on GitHub (Nov 14, 2025):
Hello,
The audiobook was The Silmarillion from the Internet Archive.
The issue seems to resolved itself after an update. Thank you for looking into it though!