[Android] Properly Resolve File Paths in FilePicker When MANAGE_EXTERNAL_STORAGE is Granted #27975
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.
Issue Summary
The
FilePicker APIfor Android currently does not properly handle file access whenMANAGE_EXTERNAL_STORAGEis granted. This leads to an incorrect behavior where the absolute file path is not resolved, and instead, the FilePicker returns a cached copy.Root Cause
EnsurePhysicalPathalways forcesrequireExtendedAccess = true, which preventsResolveDocumentPathfrom executing when Scoped Storage is enforced on Android 10+ (API 29+).MANAGE_EXTERNAL_STORAGEis granted, meaning it doesn't attempt to resolve the path even when the permission is granted.Fix
requireExtendedAccess = falsewhenMANAGE_EXTERNAL_STORAGEis granted to allowResolveDocumentPathto execute.Current Behaviour:
current_behaviour.mp4
After Fix
after_fix.mp4
Issues Fixed
Fixes #6015