[Android] Preserve captured photo result after process death and camera reinitialization #429
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
#417
Description
This fix ensures that the captured photo result is correctly preserved across process death - when the camera screen was in the background, the app was killed due to low memory, the process was recreated, and the camera reinitialized.
The updated implementation uses
rememberSaveableto retain the captured photo path across process restarts and reattaches it to the camera result when the composable is recreated. This guarantees that users don’t lose their photo capture results after process death when the camera component is reinitialized.In short, this change improves reliability and makes camera usage with
FileKitmore resilient in real-world scenarios (e.g. when backgrounding or switching apps during capture).