When using copyTo on android put the file in a uniquely named directory #397
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.
Summary
If you use
copyTo: 'cachesDirectory'
on Android, it copies the file directly into the cache directory. If there is a file already in there with the same name, it is overwritten. This is different to the behaviour on iOS, where the file is put into a uniquely named sub-directory to ensure it is not overwritten.I have modified the Android code to take the same approach as on iOS
Test Plan
Configure the picker with
copyTo: 'cachesDirectory'.
Open picker on android, select file and then log the
fileCopyUri
It will contain a unique subdirectory, i.e.
/data/user/0/[APPID]/cache/[UUID]/[FILENAME]
Compatibility
Checklist
README.md