Fix: Handle Null Byte Array in saveFile
Method
#1662
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.
Context
This PR addresses an issue in the
FilePicker.platform.saveFile
method where passing a nullUint8List
causes failures. This issue is primarily observed on Android (API 35), but the solution is implemented for both Android and iOS to ensure consistency.Root Cause
The null value for
Uint8List
was not handled correctly, leading to exceptions during file operations. Specifically:Solution
The fix ensures that:
Uint8List
is null, it is replaced with an emptyUint8List(0)
before being processed.Changes
saveFile
method to replace nullUint8List
withUint8List(0)
.Testing
References
Notes
This fix aligns with the goal of ensuring robustness in file operations across platforms, avoiding unexpected crashes due to null parameter values.
Checklist