Docs: Expanded the docs on the limitations of external filesystems fo… #593
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added an entire docs section on the quirks of external storage system on Android for API 29+ devices.
It explains at a high level what the issue is and offers an NPM search for a media store plugin that should provide a better alternative moving forward.
In summary
Android way of using the MediaStore API, which has been a concept since API level 1, but effectively now being enforced. As of API 30, there is a FUSE API which ties File API operations to MediaStore, allowing limited access to the external storage system through File APIs, which is mostly meant for NDK to access media assets.
API 29 will enforce Scoped Access for all newer apps (apps that has never been deployed to the play store) and doesn't have FUSE, making the Media Store API the only way to access external filesystem which is why it cannot be relied on.
The documentation changes makes aware of these quirks.