[Android] Fix Cursor Not Closing in File Picker to Prevent Log Spam. #27718
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hey there @bhavanesh2001! Thank you so much for your PR! Someone from the team will get assigned to your PR shortly and we'll get it reviewed. |
MartyIX
reviewed
Feb 11, 2025
Co-authored-by: MartyIX <203266+MartyIX@users.noreply.github.com>
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
jsuarezruiz
approved these changes
Feb 12, 2025
jfversluis
approved these changes
Feb 12, 2025
PureWeen
added
area-essentials
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
Description of Change
When using the File Picker API (FilePicker.PickAsync()) on Android , following warnings are being spammed on debug console:
This issue occurs because cursor does not being immediately closed.Even though the cursor is inside a using statement, Android system still logs these warnings.To ensure immediate cleanup, this PR explicitly calls
cursor.Close();preventing log spam and potential resource leaks.Issues Fixed
Fixes #27716