You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I encountered an issue where loading an image from a captured photo URL results in the image being rotated. However, when loading the same image using SDWebImage, it displays correctly without any rotation issues.
Steps to reproduce:
Capture a photo using the device camera.
Load the image URL using SKPhoto.photoWithImageURL(_:).
The image may appear rotated.
Interestingly, when using SDWebImage to load the same URL, the image is displayed correctly.
It seems that SKPhotoBrowser may not be handling the image’s EXIF metadata, particularly the orientation information, causing the image to be displayed in the wrong orientation.
The text was updated successfully, but these errors were encountered:
@woaiqiu947 Thanks for the issue report.
Would you please try out the main branch also? I don't have time to tag the latest version recently.
And 7.1.0 is already 2 years ago.
My assumption is:
The main branch also haven't solve this issue, since the library is using its own implementation on handling images.
SDWebImage/Kingfisher has handled EXIF data properly, from my pevious experience.
#452 also has a similar issue, base on image orientation. But the source is from device camera.
Will try to fix it when time allowed. Meanwhile, please feel free to create PR!
I encountered an issue where loading an image from a captured photo URL results in the image being rotated. However, when loading the same image using SDWebImage, it displays correctly without any rotation issues.
Steps to reproduce:
Interestingly, when using SDWebImage to load the same URL, the image is displayed correctly.
It seems that SKPhotoBrowser may not be handling the image’s EXIF metadata, particularly the orientation information, causing the image to be displayed in the wrong orientation.
The text was updated successfully, but these errors were encountered: