Seal
Seal copied to clipboard
JunkFood02
Storage Access Framework support for download directories
For devices running Android 10 (API 29) or higher, App gain write permission to Download/ and Documents/ by default. But the only way for accessing or writing files outside these two directories is to use Storage Access Framework. Seal does not support SAF currently. As a result, any download outside these two directories would get a Permission Denied error.
With SAF support, we could manually copy downloaded files to destination and delete original files after finish downloading without permission problems. SAF could also provide SD Card support #25 Reference: dvd
@farabox1 Hi, you can just uninstall/reinstall the app or clear the data of app to reset the download directory
@JunkFood02 Check this project out when you have the time, i think it will help you get references on how to implement a way to access other directories then Download
https://github.com/deniscerri/ytdlnis
references on how to implement a way to access other directories then Download
The use case in Seal could be much more complicated than this and dvd. Such as custom command, temporary files management, and resume download with .part files, some of these features may conflict with the SAF.
references on how to implement a way to access other directories then Download
The use case in Seal could be much more complicated than this and dvd. Such as custom command, temporary files management, and resume download with
.partfiles, some of these features may conflict with the SAF.
I see, anyway I thought it would help a little 😃
This problem is coming, what should I do?
We haven't implemented yet SAF, a storage framework that Google made for making the file saving more secure and controllable by the users. In Seal this is kinda hard to implement because it probably means to a rewrite of the basic functions of the app.
I'm using latest beta as of writing this and mine is saving audio only to music as selected in that system file access manager and YouTube folder which is default for seal anyway I think. I get what you're saying about adding the function to make this problem go away but be nice if we could dismiss the warning once understood if possible. Lovely ui and app thankyou!
@JunkFood02 I'm trying to implement SAF in the app that I'm actually developing. If I'm able to do it I'm gonna share the code with you so we can add it to Seal. I know that there are some files like config.txt or cookies.txt that can't be saved with SAF because they need to be localizable to the app in all moment, but according to Android Developers documentation, there is an App-specific file storing so we can use that for both of that files and SAF for the Downloads.
@JunkFood02 I'm trying to implement SAF in the app that I'm actually developing. If I'm able to do it I'm gonna share the code with you so we can add it to Seal. I know that there are some files like config.txt or cookies.txt that can't be saved with SAF because they need to be localizable to the app in all moment, but according to Android Developers documentation, there is an App-specific file storing so we can use that for both of that files and SAF for the Downloads.
config.txt and cookies.txt are already created in app's internal storage. The real problem of SAF migration is not the plain implementation but actually the conflict with other features, since many of them needs directly access to the file system
Temporary solution could be to allow parts… Either finalise each video or emulate zip file creation (no compression).
#455 Workaround PR for being able to use SD cards in Seal. It was only tested in Android 12. The changes can be reverted/changed.
Added in v1.8.0-beta.1, please help test this new feature out, we're ready to hear your feedback 🙌
