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
*`cordova.file.tempDirectory` - Temp directory that the OS can clear at will. Do not
111
111
rely on the OS to clear this directory; your app should always remove files as
@@ -194,6 +194,26 @@ the `cordova.file.*` properties map to physical paths on a real device.
194
194
**Note**: If external storage can't be mounted, the `cordova.file.external*`
195
195
properties are `null`.
196
196
197
+
#### Android's External Storage Quirks
198
+
199
+
With the introduction of [Scoped Storage](https://source.android.com/docs/core/storage/scoped) access to External Storage is unreliable or limited via File APIs.
200
+
Scoped Storage was introduced in API 29. While existing apps may have the ability to opt out, this option is not available for new apps. On Android API 30 and later, Scoped Storage is fully enforced.
201
+
202
+
Additionally, Direct File Access **is not** supported on API 29. This means this plugin **cannot** access external storage mediums on API 29 devices.
203
+
204
+
API 30 introduced [FUSE](https://source.android.com/docs/core/storage/scoped) which allowed limited access to external storage using File APIs, allowing this plugin to
205
+
partially work again.
206
+
207
+
Limited access includes but isn't limited to:
208
+
- Read only access with appropriate `READ_EXTERNAL` or [READ_MEDIA_*](https://developer.android.com/training/data-storage/shared/media#access-other-apps-files) permissions.
209
+
- Read only access is limited to media files, but not documents.
210
+
- Writes are limited to only files owned by your app. Modifying files owned by a third-party app (including an image file created via the camera plugin for example) is not possible via the File API.
211
+
- Not all paths in external storage is writable.
212
+
213
+
These limitations only applies to external filesystems (e.g. `cordova.file.external*` paths). Internal filesystems such as `cordova.file.dataDirectory` path are not imposed by these limitations.
214
+
215
+
If interfacing with the external file system is a requirement for your application, consider using a [MediaStore](https://www.npmjs.com/search?q=ecosystem%3Acordova%20storage%20access%20framework) plugin instead.
0 commit comments