Dear Apple Support Team,
We are investigating a camera preview orientation issue on an iPad and would appreciate guidance on the relevant UIKit and AVFoundation behavior.
Our app uses Flutter and the third-party Regula Document Reader SDK for passport MRZ scanning. We understand that third-party SDK internals are outside Apple’s support scope. Our question concerns the relationship between the active interface orientation, presentation lifecycle, and camera preview connection orientation.
- Device: iPad (A16), hardware identifier
iPad15,7 - iPadOS:
27.2.1, as reported by the device and diagnostic export - App distribution: TestFlight
- App version in the diagnostic log:
2.0.14, build7 - Flutter plugin:
flutter_document_reader_api 9.8.1718 - Runtime Regula SDK API version:
9.8.6944 - Runtime Regula SDK Core version:
9.8.20492
- Hold the affected iPad in landscape orientation and open the app.
- Open the passport scanner.
- The scanner interface appears in landscape, but the camera image appears rotated by 90 degrees.
- Open Control Center, then dismiss it and return to the app.
- The preview can then appear in the correct orientation.
- Close and reopen the scanner; the issue may recur.
Physically rotating the device does not consistently resolve the issue.
Expected: The preview should match the current interface orientation from initial presentation.
Actual: The preview initially has an orientation mismatch and may recover only after leaving and returning to the app.
We collected initial-entry and app-resume observations within the same scanner session:
- Before scanner presentation, the active
UIWindowScene.interfaceOrientationislandscapeRight. - The SDK’s presenting view controller belongs to the active application window.
- The scanner controller has landscape dimensions of approximately
1180 × 820. - The third-party SDK’s supported interface orientation is configured for landscape right.
- However, the initial preview connection reports
videoOrientation = portraitandvideoRotationAngle = 90. - Updating supported interface orientations and requesting layout updates did not resolve the initial mismatch in this test.
- A subsequent app-resume observation reports
videoOrientation = landscapeRightandvideoRotationAngle = 0. This change is recorded before our app’s delayed layout refresh.
We recognize that interface orientation and capture rotation are different concepts, and that connection metadata alone does not establish the displayed pixel orientation. We are providing these observations alongside the visible symptom rather than treating a particular angle as universally correct.
Our separate QR scanner and receipt camera work normally on the same device. The passport scanner also works normally on many other iPads. We have not established that this affects all devices running this iPadOS version.
An app-side orientation enum comparison issue was corrected before collecting the build 7 log, but the preview mismatch remained.
We have not isolated the cause to iPadOS, our presentation code, or the SDK’s capture initialization. We do not yet have a focused standalone Xcode reproduction project. We are also preparing an inquiry to the SDK vendor.
- Are there known circumstances in which a camera preview initially uses portrait orientation despite being presented in a landscape
UIWindowScene? - What is the recommended lifecycle point for determining the initial interface orientation and configuring the preview connection, particularly while presentation or rotation transitions are in progress?
- Which supported APIs should be used to keep preview rotation synchronized with interface changes on this iPadOS version?
- Could the recovery after dismissing Control Center indicate an initialization or lifecycle ordering issue? What additional observations would help distinguish these possibilities?
- What should we include in a minimal native reproduction or system diagnostic collection to make this issue actionable?
We can provide a symptom video and an application diagnostic export. These were collected in separate tests on the same affected device and are not time-synchronized. The application export is not an Apple sysdiagnose.
Thank you for any guidance on how to investigate this further.
With Best Regards,
GTF_Japan_Service