This repository was archived by the owner on Feb 22, 2023. It is now read-only.
[Image_Picker] fixed image orientation problem on Android #1878
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
This PR fixes (or tries to fix) orientation problems in the displayed images.
It uses the Exif information to normalize the image rotation so the image is always displayed correctly.
It will not solve all cases, as there are images without the correct Exif information, but will solve cases where the picture was taken with the phone up side down.
Related Issues
flutter/flutter#35334
Solving in the framework would be the best solution, but I think it may take some time to land if we wait the framework.
Breaking change
It will always create a new image file on Android. The current implementation sometimes creates an image file, that the developer already need to clear up after using the image if a resize was required. With the orientation fix we need a new file every time.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]). This will ensure a smooth and quick review process.///).flutter analyze) does not report any problems on my PR.Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?