Download can't be restarted and would fill up internal app storage #692

Open
opened 2026-04-24 23:34:32 +02:00 by adam · 3 comments
Owner

Originally created by @Demian98 on GitHub (Sep 5, 2023).

Steps to reproduce

  1. Start a download in the ABS App.
  2. Close the app and swipe it up in the app menu (to end it).
  3. Open the app and start the download again.

Actual behaviour

  • Problem 1: All files which are already in place for the first failed download will not get deleted or overwritten. It will look like this:
    • chapter 1.mp3
    • chapter 1 (1).mp3
    • chapter 2.mp3
    • chapter 2 (1).mp3
    • chapter 3.mp3
    • chapter 3 (1).mp3
  • Problem 2: When the folder "Internal App Storage" is used, failed downloads can't be clean manual, as it can't be accessed in the file manager app. For custom defined download locations, there is the option to scan or force scan the folder.
    For Internal App Storage this is not available. So when a download is failed, there is no way for the user to clean this data and over time it will get more block space. Then the user needs to reinstall the app to have the app data deleted.

Preferred solution

All audiobooks which are selected to be downloaded should be displayed in the specific folder under local media. Also, when the download is not finished yet.
The download progress, size on the local storage and issues could be displayed there.

Possible actions for the user:

  • Remove (stop the download in case it is still running and delete local data)
  • Pause and resume download
  • Restart the download if it was interrupted for any reason.

Other solutions

  • Solution 1: Make the download process restart save, so that downloads could be continued after the app was closed.
  • Solution 2: When a download is started and there is already local data for this audiobook (due to a failed download) delete the local data first. Maybe prompt the user with a warning, if he wants to continue.
  • Solution 3: Enable the possibility to scan and force scan the Internal App Storage download location. In this way, the users can be sure to have all data in their visible.

Conclusion

The preferred solution would bring a lot of benefit to the app in making the download process and management of offline data a lot easier to handle.
If not possible for some reason, then just solution 2 and 3 would also help a little.

Environment data

Audiobookshelf Version: 2.3.3

  • Android App?
  • iOS App?

Android Issue

Android version: 13

Originally created by @Demian98 on GitHub (Sep 5, 2023). ### Steps to reproduce 1. Start a download in the ABS App. 2. Close the app and swipe it up in the app menu (to end it). 3. Open the app and start the download again. ### Actual behaviour - Problem 1: All files which are already in place for the first failed download will not get deleted or overwritten. It will look like this: - chapter 1.mp3 - chapter 1 (1).mp3 - chapter 2.mp3 - chapter 2 (1).mp3 - chapter 3.mp3 - chapter 3 (1).mp3 - Problem 2: When the folder "Internal App Storage" is used, failed downloads can't be clean manual, as it can't be accessed in the file manager app. For custom defined download locations, there is the option to scan or force scan the folder. For Internal App Storage this is not available. So when a download is failed, there is no way for the user to clean this data and over time it will get more block space. Then the user needs to reinstall the app to have the app data deleted. ### Preferred solution All audiobooks which are selected to be downloaded should be displayed in the specific folder under local media. Also, when the download is not finished yet. The download progress, size on the local storage and issues could be displayed there. Possible actions for the user: - Remove (stop the download in case it is still running and delete local data) - Pause and resume download - Restart the download if it was interrupted for any reason. ### Other solutions - Solution 1: Make the download process restart save, so that downloads could be continued after the app was closed. - Solution 2: When a download is started and there is already local data for this audiobook (due to a failed download) delete the local data first. Maybe prompt the user with a warning, if he wants to continue. - Solution 3: Enable the possibility to scan and force scan the Internal App Storage download location. In this way, the users can be sure to have all data in their visible. ### Conclusion The preferred solution would bring a lot of benefit to the app in making the download process and management of offline data a lot easier to handle. If not possible for some reason, then just solution 2 and 3 would also help a little. ### Environment data Audiobookshelf Version: 2.3.3 - [x] Android App? - [ ] iOS App? #### Android Issue Android version: 13
adam added the bugandroid labels 2026-04-24 23:34:32 +02:00
Author
Owner

@Keavon commented on GitHub (Oct 9, 2023):

There should also be a way to explicitly cancel a download.

@Keavon commented on GitHub (Oct 9, 2023): There should also be a way to explicitly cancel a download.
Author
Owner

@DavidPesticcio commented on GitHub (Feb 27, 2024):

Perhaps "restarted" should additionally distinguish between: replace and resume/retry, along with a cancel option - long-hold-to-select? 😃

@DavidPesticcio commented on GitHub (Feb 27, 2024): Perhaps "restarted" should additionally distinguish between: replace and resume/retry, along with a cancel option - long-hold-to-select? :smiley:
Author
Owner

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

I have been working on refactoring the Android download logic over the past few months (progress was a bit slow due to life getting in the way). This refactor was primarily focused on cleaning up the framework, and not specifically aimed at fixing any particular issue. However, it is possible that the changes may have resolved this issue as a side effect.

If you get a chance, please try sideloading the APK located at the end of the pull request and let me know if you run into other issues, whether this issue still occurs, or if this issue appears to be resolved. The APK can be downloaded from the "Build APK" workflow at the end of the page by clicking on "View Details", then clicking on "Summary", then downloading the APK. The PR is https://github.com/advplyr/audiobookshelf-app/pull/1587

I am requesting feedback on all of the open Android download issues, so apologies if you receive multiple notifications.

Workflow run
APK download

@nichwall commented on GitHub (May 26, 2025): I have been working on refactoring the Android download logic over the past few months (progress was a bit slow due to life getting in the way). This refactor was primarily focused on cleaning up the framework, and not specifically aimed at fixing any particular issue. However, it is possible that the changes may have resolved this issue as a side effect. If you get a chance, please try sideloading the APK located at the end of the pull request and let me know if you run into other issues, whether this issue still occurs, or if this issue appears to be resolved. The APK can be downloaded from the "Build APK" workflow at the end of the page by clicking on "View Details", then clicking on "Summary", then downloading the APK. The PR is https://github.com/advplyr/audiobookshelf-app/pull/1587 I am requesting feedback on all of the open Android download issues, so apologies if you receive multiple notifications. ![Workflow run](https://github.com/user-attachments/assets/ac386c0c-5a3c-4b10-98a1-1c5626358348) ![APK download](https://github.com/user-attachments/assets/ded054e4-0cc5-457c-bb59-f1651197fbbc)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf-app#692