breautek commented on issue #613: URL: https://github.com/apache/cordova-plugin-file/issues/613#issuecomment-2593108621
I'm closing this as we have more information now since this issue was first opened. Since scoped access framework introduced in API 29, filesystem access to external storage (e.g. any `/storage/emulated/` or `/sdcard/` paths will be incredibly limited.) . These quirks are now documented [here](https://github.com/apache/cordova-plugin-file?tab=readme-ov-file#androids-external-storage-quirks). Therefore using the filesystem plugin will only be recommended for internal storage file management only. Using any of the `cordova.file.external*` constants will yield odd quirks due Android limitations. Android expects developers to stop using the File APIs and instead to use the `MediaStore` APIs when working with the external filesystem. On API 29, accessing the external filesystem via Filesystem APIs is completely blocked. On API 30 and later, this was slightly relaxed to allow for media files (audio, video, and images), and is for the most part limited to reads (not writes). The MediaStore API can't really be implemented in a "filesystem-like" fashion so there are no plans to interface with the native MediaStore API. If your app requires the use of external storage, it will be recommended to find a plugin that interfaces with the MediaStore API instead. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
