You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I ask because sadly Google plans to ruin the storage permission, and allow to use only SAF API to get access to files, and from there you can use InputStream and not File or file-path.
The text was updated successfully, but these errors were encountered:
you mentioned Stream means continuing small bytes and loop read, but not whole file, it's a wonderful idea and I will check if the original lib support this operation.
How could I know how many bytes to provide?
Don't the various file types need to have a minimal size for themselves, and some have a suffix of data and not just prefix?
The SAF API is truly a bad API, but that's the only thing that Google seems to be offering for all types of files. It's even very slow compared to the normal File API, at least in terms of folders-traversal (see here: https://issuetracker.google.com/issues/130261278 ) ...
I truly hope that Google will avoid this.
They already plan to ruin other types of apps too: apps that use the system-alert-window permission (allows to put content on top of other apps, floating), and clipboard apps (not being able to access it in the background).
Or just file-path or File instance?
I ask because sadly Google plans to ruin the storage permission, and allow to use only SAF API to get access to files, and from there you can use InputStream and not File or file-path.
The text was updated successfully, but these errors were encountered: