[GitHub] [cordova-plugin-file] breautek commented on issue #494: Cannot read files under cordova.file.externalRootDirectory for Android 11

[GitBox <gi...@apache.org>]

breautek commented on issue #494:
URL: https://github.com/apache/cordova-plugin-file/issues/494#issuecomment-1126064751

   > he externalRootDirectory directory is no longer a writable path with the Android's new filesystem. Google doesn't explicitly say which paths are no longer accessible, but it does [vaguely](https://developer.android.com/about/versions/11/privacy/storage#migrate-data-for-scoped-storage) say that some paths that used to be writable will no longer be accessible.
   
   >>If your app uses the legacy storage model and previously targeted Android 10 or lower, you might be storing data in a directory that your app cannot access when the [scoped storage](https://developer.android.com/training/data-storage#scoped-storage) model is enabled...
   
   https://github.com/apache/cordova-plugin-file/issues/408#issuecomment-1126059587
   
   For this reason I'm closing this as won't fix.
   
   @Jusse2299  The `MANAGE_EXTERNAL_STORAGE` is kind of an escape-hatch permission that allows full control over the android filesystem. It is available to third-party apps (such as apps developed by us) but you have to justify the reason for using hte permission to Google. Typically this permission is for File manager or virus scanner kind of apps where they require broad unrestricted access as a core functionality of their app.


-- 
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-unsubscribe@cordova.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org