fix: auto upload collect changed files #15764
Open
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
The application collects modified files from
ContentObserverWork
as an array of strings, for example:content://media/external/images/media/2281
. This array is then optionally passed to theAutoUploadWorker
. The goal is to avoid scanning the entire local folder and instead only process the files that have changed.However, errors can occur during this operation—for instance, the file path could be null, or the file may not exist. Such cases can result in upload information being lost, which may cause the auto-upload to fail.
Example crash log:
Changes
Instead of failing the entire worker when encountering such issues, we should handle all potential edge cases. As a fallback, the worker should scan the entire local folder to ensure no files are missed for upload.
Documentation and links have been added to the functions, and function and variable names have been changed to prevent further confusions.
How to test?