[Bug]: update nuked all app data, blank connect page #1192

Closed
opened 2026-04-24 23:52:41 +02:00 by adam · 24 comments
Owner

Originally created by @wtanksleyjr on GitHub (Apr 23, 2025).

I have verified that the bug is not already awaiting release

Yes

What was the Problem?

The 4/20 patch just installed, and now the app doesn't have any of my local books and doesn't do anything when I ask it to connect to the server (more specifically, it switches to the server connect page, but nothing is displayed in it; no status, no login.

Steps to Reproduce the Issue

No idea, I'm guessing it's the update but don't know how to find anything and can't spend time because big commute.

What was Expected?

ewvfbbkjhjb come ON

Phone Model

Samsung Flip3

Phone OS

Android ?

Audiobookshelf App Version

Android App - 0.9.79

Installation Source

Google Play Store

Additional Notes

No response

Originally created by @wtanksleyjr on GitHub (Apr 23, 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 4/20 patch just installed, and now the app doesn't have any of my local books and doesn't do anything when I ask it to connect to the server (more specifically, it switches to the server connect page, but nothing is displayed in it; no status, no login. ### Steps to Reproduce the Issue No idea, I'm guessing it's the update but don't know how to find anything and can't spend time because big commute. ### What was Expected? ewvfbbkjhjb come ON ### Phone Model Samsung Flip3 ### Phone OS Android ? ### Audiobookshelf App Version Android App - 0.9.79 ### Installation Source Google Play Store ### Additional Notes _No response_
adam added the bug label 2026-04-24 23:52:41 +02:00
adam closed this issue 2026-04-24 23:52:41 +02:00
Author
Owner

@nichwall commented on GitHub (Apr 23, 2025):

I have been able to reproduce this from a fresh app start a few times. Completely closing the app and opening it again correctly connects to the server and shows locally downloaded media.

Logs from the app on 0.9.80-beta on Android below. This includes both the failure to load anything, then restarting the app and everything loading.

04/23/2025 07:18:38.454 [INFO] cleanLogs: Removed 46 logs older than 48 hours
04/23/2025 07:18:38.908 [INFO] mounted: initializing first load (android v0.9.80-beta)
04/23/2025 07:18:45.837 [INFO] mounted: initializing first load (android v0.9.80-beta)
04/23/2025 07:18:46.117 [INFO] mounted: Server not connected, attempt connection
04/23/2025 07:18:46.357 [INFO] attemptConnection: Got server config, attempt authorize (https://[SERVER_ADDRESS] (chell))
04/23/2025 07:18:46.677 [INFO] attemptConnection: Successful connection to last saved server config (https://[SERVER_ADDRESS] (chell))
04/23/2025 07:18:46.722 [INFO] initLibraries loading library Podcasts
04/23/2025 07:18:47.625 [INFO] Calling syncLocalSessions
04/23/2025 07:18:47.631 [INFO] [ApiHandler] syncLocalMediaProgressForUser: Server connection https://[SERVER_ADDRESS] (chell)
04/23/2025 07:18:47.640 [INFO] syncLocalMediaProgressForUser: Found 15 local media progress
04/23/2025 07:18:47.829 [INFO] syncLocalMediaProgressForUser: Finishing syncing local media progress with server. 15 up-to-date, 0 updated
04/23/2025 07:18:47.834 [INFO] syncLocalSessionsWithServer: No saved local playback sessions to send to server.
04/23/2025 07:18:47.874 [INFO] mounted: fully initialized
@nichwall commented on GitHub (Apr 23, 2025): I have been able to reproduce this from a fresh app start a few times. Completely closing the app and opening it again correctly connects to the server and shows locally downloaded media. Logs from the app on 0.9.80-beta on Android below. This includes both the failure to load anything, then restarting the app and everything loading. ``` 04/23/2025 07:18:38.454 [INFO] cleanLogs: Removed 46 logs older than 48 hours 04/23/2025 07:18:38.908 [INFO] mounted: initializing first load (android v0.9.80-beta) 04/23/2025 07:18:45.837 [INFO] mounted: initializing first load (android v0.9.80-beta) 04/23/2025 07:18:46.117 [INFO] mounted: Server not connected, attempt connection 04/23/2025 07:18:46.357 [INFO] attemptConnection: Got server config, attempt authorize (https://[SERVER_ADDRESS] (chell)) 04/23/2025 07:18:46.677 [INFO] attemptConnection: Successful connection to last saved server config (https://[SERVER_ADDRESS] (chell)) 04/23/2025 07:18:46.722 [INFO] initLibraries loading library Podcasts 04/23/2025 07:18:47.625 [INFO] Calling syncLocalSessions 04/23/2025 07:18:47.631 [INFO] [ApiHandler] syncLocalMediaProgressForUser: Server connection https://[SERVER_ADDRESS] (chell) 04/23/2025 07:18:47.640 [INFO] syncLocalMediaProgressForUser: Found 15 local media progress 04/23/2025 07:18:47.829 [INFO] syncLocalMediaProgressForUser: Finishing syncing local media progress with server. 15 up-to-date, 0 updated 04/23/2025 07:18:47.834 [INFO] syncLocalSessionsWithServer: No saved local playback sessions to send to server. 04/23/2025 07:18:47.874 [INFO] mounted: fully initialized ```
Author
Owner

@strykerx commented on GitHub (Apr 23, 2025):

Same issue here. I was not able to get the app to function normally from completely closing and reopening the app.

@strykerx commented on GitHub (Apr 23, 2025): Same issue here. I was not able to get the app to function normally from completely closing and reopening the app.
Author
Owner

@wtanksleyjr commented on GitHub (Apr 23, 2025):

I couldn't make it work simply by closing and reopening, but after a phone restart, open, close, and reopen (as nichwall described) it found everything. Whew! @strykerx try a reboot, maybe it'll help...

@wtanksleyjr commented on GitHub (Apr 23, 2025): I couldn't make it work simply by closing and reopening, but after a phone restart, open, close, and reopen (as nichwall described) it found everything. Whew! @strykerx try a reboot, maybe it'll help...
Author
Owner

@nichwall commented on GitHub (Apr 23, 2025):

App version 0.9.80 adds app logging accessible by the user (the logs are still pretty limited), but if you can confirm the logs to see if [INFO] mounted: initializing first load (android v0.9.80-beta) is showing up multiple times from failing to start and restarting the app, that would be helpful.

Your server address is automatically redacted in the logs, and can be accessed from the side menu.

@nichwall commented on GitHub (Apr 23, 2025): App version 0.9.80 adds app logging accessible by the user (the logs are still pretty limited), but if you can confirm the logs to see if `[INFO] mounted: initializing first load (android v0.9.80-beta)` is showing up multiple times from failing to start and restarting the app, that would be helpful. Your server address is automatically redacted in the logs, and can be accessed from the side menu.
Author
Owner

@advplyr commented on GitHub (Apr 23, 2025):

Probably the same issue with AbsLogger and lateinit that I fixed already. I'm working on a release to come soon

@advplyr commented on GitHub (Apr 23, 2025): Probably the same issue with AbsLogger and `lateinit` that I fixed already. I'm working on a release to come soon
Author
Owner

@cupanoodle commented on GitHub (Apr 23, 2025):

Same issue I think just happened to me about a hour back. Strangely it happened randomly during playback and well after the app was updated. None of the workarounds mentioned here worked for me (restart app, restart phone.

Image
Image
Image

@cupanoodle commented on GitHub (Apr 23, 2025): Same issue I think just happened to me about a hour back. Strangely it happened randomly during playback and well after the app was updated. None of the workarounds mentioned here worked for me (restart app, restart phone. ![Image](https://github.com/user-attachments/assets/8df0fab5-43e7-461f-850c-b4603a02ed22) ![Image](https://github.com/user-attachments/assets/b4a05d5f-4a82-4629-8a2d-bf1db27e1afd) ![Image](https://github.com/user-attachments/assets/1c388ec9-5b2f-4741-af27-71e767c8da90)
Author
Owner

@skyzuma commented on GitHub (Apr 23, 2025):

same here on flip 5 android 14 after an update to the latest :( (conn per local pihole domain)

delete cache and data on system app settingspage > re edit serverdata > worked now ...

@skyzuma commented on GitHub (Apr 23, 2025): same here on flip 5 android 14 after an update to the latest :( (conn per local pihole domain) delete cache and data on system app settingspage > re edit serverdata > worked now ...
Author
Owner

@skyzuma commented on GitHub (Apr 23, 2025):

but it woked instant on my tablet (sm-t725) - (conn per local ip:port)

@skyzuma commented on GitHub (Apr 23, 2025): but it woked instant on my tablet (sm-t725) - (conn per local ip:port)
Author
Owner

@nichwall commented on GitHub (Apr 23, 2025):

You do not need to reset the app data/cache. You only need to restart the app (completely closing the app). It may need to be restarted once or twice

@nichwall commented on GitHub (Apr 23, 2025): You do not need to reset the app data/cache. You only need to restart the app (completely closing the app). It may need to be restarted once or twice
Author
Owner

@skyzuma commented on GitHub (Apr 23, 2025):

no, a restart doesnt help ... i needed to delete data/cache ...

@skyzuma commented on GitHub (Apr 23, 2025): no, a restart doesnt help ... i needed to delete data/cache ...
Author
Owner

@Safemode commented on GitHub (Apr 23, 2025):

I just had this happen to me a little bit ago, I'd force closed the app and cleared cache only, and had to open/force close/reopen a few times before it came up and reconnected to my server. Pixel 9 Pro with Android 15 on app version 0.9.80

@Safemode commented on GitHub (Apr 23, 2025): I just had this happen to me a little bit ago, I'd force closed the app and cleared cache only, and had to open/force close/reopen a few times before it came up and reconnected to my server. Pixel 9 Pro with Android 15 on app version 0.9.80
Author
Owner

@Konraddo commented on GitHub (Apr 24, 2025):

Had the same issue. Clearing user data and cache fixed it.

@Konraddo commented on GitHub (Apr 24, 2025): Had the same issue. Clearing user data and cache fixed it.
Author
Owner

@lkiesow commented on GitHub (Apr 24, 2025):

Same issue here. App says not connected, you cannot connect and it will also not show local files. Restart helped the first time. Now, it doesn't anymore. The logs repeatedly state initializing first load (android v0.9.80-beta):

04/23/2025 23:05:28.304 [INFO] mounted: initializing first load (android v0.9.80-beta)
04/23/2025 23:05:59.153 [INFO] mounted: initializing first load (android v0.9.80-beta)
04/23/2025 23:05:59.293 [INFO] mounted: Server not connected, attempt connection
04/23/2025 23:05:59.299 [INFO] attemptConnection: Got server config, attempt authorize (https://[SERVER_ADDRESS] (lars))
04/23/2025 23:06:01.729 [INFO] attemptConnection: Successful connection to last saved server config (https://[SERVER_ADDRESS] (lars))
04/23/2025 23:06:01.903 [INFO] initLibraries loading library libaudio
04/23/2025 23:06:02.222 [INFO] Calling syncLocalSessions
04/23/2025 23:06:02.225 [INFO] [ApiHandler] syncLocalMediaProgressForUser: Server connection https://[SERVER_ADDRESS] (lars)
04/23/2025 23:06:02.228 [INFO] syncLocalMediaProgressForUser: Found 1 local media progress
04/23/2025 23:06:03.494 [INFO] syncLocalMediaProgressForUser: Finishing syncing local media progress with server. 1 up-to-date, 0 updated
04/23/2025 23:06:03.504 [INFO] syncLocalSessionsWithServer: No saved local playback sessions to send to server.
04/23/2025 23:06:03.536 [INFO] mounted: fully initialized
04/23/2025 23:06:12.085 [INFO] playLibraryItem: Received play request for library item 8f03de5b-7a24-4982-a5ba-6fc811338b95 
[…]
04/24/2025 08:00:07.371 [INFO] userMediaProgressUpdate: Received updated media progress for current user from socket event. Media item id d08e0cf9-658f-40d4-b233-96de0a440e05
04/24/2025 12:58:23.142 [INFO] cleanLogs: Removed 2369 logs older than 48 hours
04/24/2025 12:58:23.657 [INFO] mounted: initializing first load (android v0.9.80-beta)
04/24/2025 12:59:21.451 [INFO] mounted: initializing first load (android v0.9.80-beta)
04/24/2025 12:59:27.394 [INFO] cleanLogs: Removed 10 logs older than 48 hours
04/24/2025 12:59:27.811 [INFO] mounted: initializing first load (android v0.9.80-beta)
04/24/2025 12:59:51.364 [INFO] cleanLogs: Removed 4 logs older than 48 hours
04/24/2025 12:59:51.744 [INFO] mounted: initializing first load (android v0.9.80-beta)
04/24/2025 13:07:27.320 [INFO] cleanLogs: Removed 60 logs older than 48 hours
04/24/2025 13:07:27.758 [INFO] mounted: initializing first load (android v0.9.80-beta)
04/24/2025 13:07:46.066 [INFO] cleanLogs: Removed 2 logs older than 48 hours
04/24/2025 13:07:46.482 [INFO] mounted: initializing first load (android v0.9.80-beta)
04/24/2025 13:08:13.411 [INFO] mounted: initializing first load (android v0.9.80-beta)
04/24/2025 13:08:55.570 [INFO] cleanLogs: Removed 10 logs older than 48 hours
04/24/2025 13:08:55.973 [INFO] mounted: initializing first load (android v0.9.80-beta)
04/24/2025 14:19:40.915 [INFO] cleanLogs: Removed 566 logs older than 48 hours
04/24/2025 14:19:41.320 [INFO] mounted: initializing first load (android v0.9.80-beta)
04/24/2025 14:23:21.924 [INFO] mounted: initializing first load (android v0.9.80-beta)
04/24/2025 14:25:16.597 [INFO] cleanLogs: Removed 44 logs older than 48 hours
04/24/2025 14:25:17.007 [INFO] mounted: initializing first load (android v0.9.80-beta)
04/24/2025 14:25:26.300 [INFO] cleanLogs: Removed 2 logs older than 48 hours
04/24/2025 14:25:26.711 [INFO] mounted: initializing first load (android v0.9.80-beta)
04/24/2025 14:26:29.490 [INFO] mounted: initializing first load (android v0.9.80-beta)
04/24/2025 14:33:26.860 [INFO] mounted: initializing first load (android v0.9.80-beta)
04/24/2025 14:33:33.213 [INFO] cleanLogs: Removed 64 logs older than 48 hours
04/24/2025 14:33:33.621 [INFO] mounted: initializing first load (android v0.9.80-beta)
04/24/2025 14:41:26.091 [INFO] mounted: initializing first load (android v0.9.80-beta)
04/24/2025 14:41:35.337 [INFO] cleanLogs: Removed 64 logs older than 48 hours
04/24/2025 14:41:35.749 [INFO] mounted: initializing first load (android v0.9.80-beta)
04/24/2025 14:41:41.431 [INFO] mounted: initializing first load (android v0.9.80-beta)
04/24/2025 14:42:22.232 [INFO] mounted: initializing first load (android v0.9.80-beta)

Probably the same issue with AbsLogger and lateinit that I fixed already. I'm working on a release to come soon

Any ETA for a fixed release?

@lkiesow commented on GitHub (Apr 24, 2025): Same issue here. App says not connected, you cannot connect and it will also not show local files. Restart helped the first time. Now, it doesn't anymore. The logs repeatedly state `initializing first load (android v0.9.80-beta)`: ``` 04/23/2025 23:05:28.304 [INFO] mounted: initializing first load (android v0.9.80-beta) 04/23/2025 23:05:59.153 [INFO] mounted: initializing first load (android v0.9.80-beta) 04/23/2025 23:05:59.293 [INFO] mounted: Server not connected, attempt connection 04/23/2025 23:05:59.299 [INFO] attemptConnection: Got server config, attempt authorize (https://[SERVER_ADDRESS] (lars)) 04/23/2025 23:06:01.729 [INFO] attemptConnection: Successful connection to last saved server config (https://[SERVER_ADDRESS] (lars)) 04/23/2025 23:06:01.903 [INFO] initLibraries loading library libaudio 04/23/2025 23:06:02.222 [INFO] Calling syncLocalSessions 04/23/2025 23:06:02.225 [INFO] [ApiHandler] syncLocalMediaProgressForUser: Server connection https://[SERVER_ADDRESS] (lars) 04/23/2025 23:06:02.228 [INFO] syncLocalMediaProgressForUser: Found 1 local media progress 04/23/2025 23:06:03.494 [INFO] syncLocalMediaProgressForUser: Finishing syncing local media progress with server. 1 up-to-date, 0 updated 04/23/2025 23:06:03.504 [INFO] syncLocalSessionsWithServer: No saved local playback sessions to send to server. 04/23/2025 23:06:03.536 [INFO] mounted: fully initialized 04/23/2025 23:06:12.085 [INFO] playLibraryItem: Received play request for library item 8f03de5b-7a24-4982-a5ba-6fc811338b95 […] 04/24/2025 08:00:07.371 [INFO] userMediaProgressUpdate: Received updated media progress for current user from socket event. Media item id d08e0cf9-658f-40d4-b233-96de0a440e05 04/24/2025 12:58:23.142 [INFO] cleanLogs: Removed 2369 logs older than 48 hours 04/24/2025 12:58:23.657 [INFO] mounted: initializing first load (android v0.9.80-beta) 04/24/2025 12:59:21.451 [INFO] mounted: initializing first load (android v0.9.80-beta) 04/24/2025 12:59:27.394 [INFO] cleanLogs: Removed 10 logs older than 48 hours 04/24/2025 12:59:27.811 [INFO] mounted: initializing first load (android v0.9.80-beta) 04/24/2025 12:59:51.364 [INFO] cleanLogs: Removed 4 logs older than 48 hours 04/24/2025 12:59:51.744 [INFO] mounted: initializing first load (android v0.9.80-beta) 04/24/2025 13:07:27.320 [INFO] cleanLogs: Removed 60 logs older than 48 hours 04/24/2025 13:07:27.758 [INFO] mounted: initializing first load (android v0.9.80-beta) 04/24/2025 13:07:46.066 [INFO] cleanLogs: Removed 2 logs older than 48 hours 04/24/2025 13:07:46.482 [INFO] mounted: initializing first load (android v0.9.80-beta) 04/24/2025 13:08:13.411 [INFO] mounted: initializing first load (android v0.9.80-beta) 04/24/2025 13:08:55.570 [INFO] cleanLogs: Removed 10 logs older than 48 hours 04/24/2025 13:08:55.973 [INFO] mounted: initializing first load (android v0.9.80-beta) 04/24/2025 14:19:40.915 [INFO] cleanLogs: Removed 566 logs older than 48 hours 04/24/2025 14:19:41.320 [INFO] mounted: initializing first load (android v0.9.80-beta) 04/24/2025 14:23:21.924 [INFO] mounted: initializing first load (android v0.9.80-beta) 04/24/2025 14:25:16.597 [INFO] cleanLogs: Removed 44 logs older than 48 hours 04/24/2025 14:25:17.007 [INFO] mounted: initializing first load (android v0.9.80-beta) 04/24/2025 14:25:26.300 [INFO] cleanLogs: Removed 2 logs older than 48 hours 04/24/2025 14:25:26.711 [INFO] mounted: initializing first load (android v0.9.80-beta) 04/24/2025 14:26:29.490 [INFO] mounted: initializing first load (android v0.9.80-beta) 04/24/2025 14:33:26.860 [INFO] mounted: initializing first load (android v0.9.80-beta) 04/24/2025 14:33:33.213 [INFO] cleanLogs: Removed 64 logs older than 48 hours 04/24/2025 14:33:33.621 [INFO] mounted: initializing first load (android v0.9.80-beta) 04/24/2025 14:41:26.091 [INFO] mounted: initializing first load (android v0.9.80-beta) 04/24/2025 14:41:35.337 [INFO] cleanLogs: Removed 64 logs older than 48 hours 04/24/2025 14:41:35.749 [INFO] mounted: initializing first load (android v0.9.80-beta) 04/24/2025 14:41:41.431 [INFO] mounted: initializing first load (android v0.9.80-beta) 04/24/2025 14:42:22.232 [INFO] mounted: initializing first load (android v0.9.80-beta) ``` > Probably the same issue with AbsLogger and lateinit that I fixed already. I'm working on a release to come soon Any ETA for a fixed release?
Author
Owner

@wtanksleyjr commented on GitHub (Apr 24, 2025):

Restart helped the first time. Now, it doesn't anymore.

Same happened to me, spent my commute (when at traffic lights) restarting. It actually did restart correctly eventually.

@wtanksleyjr commented on GitHub (Apr 24, 2025): > Restart helped the first time. Now, it doesn't anymore. Same happened to me, spent my commute (when at traffic lights) restarting. It actually did restart correctly eventually.
Author
Owner

@sir-wilhelm commented on GitHub (Apr 25, 2025):

I ran into this today; I was able to get it connected after doing 3-4 app restarts (force stop/open).

@sir-wilhelm commented on GitHub (Apr 25, 2025): I ran into this today; I was able to get it connected after doing 3-4 app restarts (force stop/open).
Author
Owner

@zatkinson08 commented on GitHub (Apr 25, 2025):

I just hit this issue on v0.9.80-beta. I cleared storage, logged back into server and downloaded current book again. I was good to go after that. I have similar screenshots to what was posted already. No login option (blank).

@zatkinson08 commented on GitHub (Apr 25, 2025): I just hit this issue on v0.9.80-beta. I cleared storage, logged back into server and downloaded current book again. I was good to go after that. I have similar screenshots to what was posted already. No login option (blank).
Author
Owner

@m4teh commented on GitHub (Apr 25, 2025):

Same issue. Force close + reopen about 8 times fixed it.

Also this update has really messed up layout on Pixel 9 Pro.

Image

@m4teh commented on GitHub (Apr 25, 2025): Same issue. Force close + reopen about 8 times fixed it. Also this update has really messed up layout on Pixel 9 Pro. ![Image](https://github.com/user-attachments/assets/50177ce9-8088-4d16-ba17-6ae1f2e3c9c7)
Author
Owner

@WickedSquirrel commented on GitHub (Apr 25, 2025):

Have the same issue.. force closing (from the app properties) and opening again worked for me.

@WickedSquirrel commented on GitHub (Apr 25, 2025): Have the same issue.. force closing (from the app properties) and opening again worked for me.
Author
Owner

@RoboticInterface commented on GitHub (Apr 25, 2025):

I can confirm behavior on Android v0.9.80-beta & running on Pixel9. Past few days I have had the above issue, but closing and re-opening the app was enough. Today force stops and phone restarts do nothing to resolve the issue.

@RoboticInterface commented on GitHub (Apr 25, 2025): I can confirm behavior on Android v0.9.80-beta & running on Pixel9. Past few days I have had the above issue, but closing and re-opening the app was enough. Today force stops and phone restarts do nothing to resolve the issue.
Author
Owner

@ilmaren commented on GitHub (Apr 26, 2025):

I had the same issue.
I saw this is already marked as "awaiting release", but I want to add that after reinstalling the app (v. 0.9.80-beta), I am now able to stream, but not to download to the local storage: the android app crash and the server (docker 2.20.0) return the following log

2025-04-26 00:30:07.245
DEBUG
[SocketAuthority] User Online <user>

2025-04-26 00:30:13.831
INFO
[LibraryItemController] User "<user>" requested download for item "<file>"

2025-04-26 00:30:13.854
INFO
[LibraryItemController] User "<user>" requested download for item "<file>"

2025-04-26 00:30:13.870
INFO
[LibraryItemController] User "<user>" requested download for item "<file>"

2025-04-26 00:30:13.902
ERROR
[LibraryItemController] Failed to download file "<file>" Error: Request aborted at onaborted (/node_modules/express/lib/response.js:1052:15) at onfinish (/node_modules/express/lib/response.js:1088:50) at AsyncResource.runInAsyncScope (node:async_hooks:206:9) at listener (/node_modules/on-finished/index.js:170:15) at onFinish (/node_modules/on-finished/index.js:101:5) at callback (/node_modules/ee-first/index.js:55:10) at Socket.onevent (/node_modules/ee-first/index.js:93:5) at Socket.emit (node:events:536:35) at emitErrorNT (node:internal/streams/destroy:169:8) at emitErrorCloseNT (node:internal/streams/destroy:128:3) { code: 'ECONNABORTED' }

2025-04-26 00:30:13.947
INFO
[LibraryItemController] Downloaded file "<file>"

2025-04-26 00:30:14.007
INFO
[LibraryItemController] Downloaded file "<file>"

2025-04-26 00:30:14.155
DEBUG
[SocketAuthority] User Offline <user>

2025-04-26 00:30:14.160
INFO
[SocketAuthority] Socket disconnected from client "<user>" after 6944ms (Reason: transport close)

This happens if I use the default folder, if I create a new folder (Android App Shared Storage), and download the book there, it nearly works (sometimes it returns RangeNotSatisfiableError on a random mp3 - this means not always on the same file - and sometimes all the files are downloaded regularly), but then doesn't let me stream or play it and return that there is no local file.

I hope this could be of some help

@ilmaren commented on GitHub (Apr 26, 2025): I had the same issue. I saw this is already marked as "awaiting release", but I want to add that after reinstalling the app (v. 0.9.80-beta), I am now able to stream, but not to download to the local storage: the android app crash and the server (docker 2.20.0) return the following log ``` 2025-04-26 00:30:07.245 DEBUG [SocketAuthority] User Online <user> 2025-04-26 00:30:13.831 INFO [LibraryItemController] User "<user>" requested download for item "<file>" 2025-04-26 00:30:13.854 INFO [LibraryItemController] User "<user>" requested download for item "<file>" 2025-04-26 00:30:13.870 INFO [LibraryItemController] User "<user>" requested download for item "<file>" 2025-04-26 00:30:13.902 ERROR [LibraryItemController] Failed to download file "<file>" Error: Request aborted at onaborted (/node_modules/express/lib/response.js:1052:15) at onfinish (/node_modules/express/lib/response.js:1088:50) at AsyncResource.runInAsyncScope (node:async_hooks:206:9) at listener (/node_modules/on-finished/index.js:170:15) at onFinish (/node_modules/on-finished/index.js:101:5) at callback (/node_modules/ee-first/index.js:55:10) at Socket.onevent (/node_modules/ee-first/index.js:93:5) at Socket.emit (node:events:536:35) at emitErrorNT (node:internal/streams/destroy:169:8) at emitErrorCloseNT (node:internal/streams/destroy:128:3) { code: 'ECONNABORTED' } 2025-04-26 00:30:13.947 INFO [LibraryItemController] Downloaded file "<file>" 2025-04-26 00:30:14.007 INFO [LibraryItemController] Downloaded file "<file>" 2025-04-26 00:30:14.155 DEBUG [SocketAuthority] User Offline <user> 2025-04-26 00:30:14.160 INFO [SocketAuthority] Socket disconnected from client "<user>" after 6944ms (Reason: transport close) ``` This happens if I use the default folder, if I create a new folder (Android App Shared Storage), and download the book there, it nearly works (sometimes it returns RangeNotSatisfiableError on a random mp3 - this means not always on the same file - and sometimes all the files are downloaded regularly), but then doesn't let me stream or play it and return that there is no local file. I hope this could be of some help
Author
Owner

@nichwall commented on GitHub (Apr 26, 2025):

@ilmaren you may be running into https://github.com/advplyr/audiobookshelf-app/issues/1553

The server reporting the connection as aborted makes sense if the app is crashing during download

@nichwall commented on GitHub (Apr 26, 2025): @ilmaren you may be running into https://github.com/advplyr/audiobookshelf-app/issues/1553 The server reporting the connection as aborted makes sense if the app is crashing during download
Author
Owner

@sir-wilhelm commented on GitHub (Apr 26, 2025):

I've not gotten stuck on the "server not connected" page since downloading v0.9.81-beta from the app store.

@sir-wilhelm commented on GitHub (Apr 26, 2025): I've not gotten stuck on the "server not connected" page since downloading v0.9.81-beta from the app store.
Author
Owner

@github-actions[bot] commented on GitHub (Apr 26, 2025):

Fixed in v0.9.81-beta.

@github-actions[bot] commented on GitHub (Apr 26, 2025): Fixed in [v0.9.81-beta](https://github.com/advplyr/audiobookshelf-app/releases/tag/v0.9.81-beta).
Author
Owner

@ilmaren commented on GitHub (Apr 26, 2025):

@ilmaren you may be running into #1553

The server reporting the connection as aborted makes sense if the app is crashing during download

Thank you @nichwall

@ilmaren commented on GitHub (Apr 26, 2025): > [@ilmaren](https://github.com/ilmaren) you may be running into [#1553](https://github.com/advplyr/audiobookshelf-app/issues/1553) > > The server reporting the connection as aborted makes sense if the app is crashing during download Thank you @nichwall
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf-app#1192