Image
displays JPG photos taken in Portrait orientation in Landscape orientation (regression in 8.0.10)
#21314
Labels
area-controls-image
Image control
fixed-in-8.0.40
fixed-in-9.0.0-preview.4.10690
i/regression
This issue described a confirmed regression on a currently supported version
p/1
Work that is important, and has been scheduled for release in this or an upcoming sprint
platform/iOS 🍎
s/triaged
Issue has been reviewed
s/verified
Verified / Reproducible Issue ready for Engineering Triage
t/bug
Something isn't working
Milestone
Description
After updating .NET MAUI from
v8.0.7
tov8.0.10
, photos taken in Portrait orientation on my iPad Pro (11", 4th-gen, iOS v17.4) using the built-in Camera app and rear-facing camera are displayed in Landscape orientation.I'm able to reproduce this reliably by taking photos in the Camera app (or in a custom app that uses iOS APIs to take photos), but not with the MediaPicker, so my reproduction repository comes with a photo I took. I think this is because MediaPicker always returns the photo in PNG format, and this issue seems to only occur due to metadata (EXIF?) in the JPEG file.
You can reliably reproduce this issue by simply switching between 8.0.7 and 8.0.10. The screenshots below are from my reproduction repository, and the only difference between them is the .NET MAUI version the project is referencing.
If you just want an example image that can be used to reproduce this, you can find one here.
NOTE: This might affect other platforms/devices, but I'm specifically calling out iPad Pro because that's where I've reproduced it.
.NET MAUI v8.0.7
.NET MAUI v8.0.10
Steps to Reproduce
Resources\Images
Image
control that references your JPG file:Link to public reproduction project repository
https://github.com/zeldafreak/MauiImageRegression/tree/main
Version with bug
8.0.10 SR3
Is this a regression from previous behavior?
Yes, this used to work in .NET MAUI
Last version that worked well
8.0.7 SR2
Affected platforms
iOS
Affected platform versions
iOS 17.4, iPad Pro (11", 4th-gen)
Did you find any workaround?
Rolling back to v8.0.7 restores the original behavior.
Relevant log output
No response
The text was updated successfully, but these errors were encountered: