We read windowScene.statusBarManager?.statusBarFrame and pin views to the safe area. Mid-fold, the status bar and home-indicator insets change, but several child view controllers do not get viewSafeAreaInsetsDidChange until the animation finishes. Which callbacks are apps expected to use to track safe area continuously through a fold?

Our detents use fractions and absolute heights derived from the screen’s long side. After a fold, a detent that was “medium” on the outer display is far too short or too tall on the inner display until we rebuild the sheet. Do custom and system detents automatically track windowScene.screen.bounds, or must the app reassign sheet.detents when the scene geometry changes?

If the user folds or unfolds while our sheet is up, the detent heights and whether the sheet is inset are stale. We dismiss with animated: false and present again inside traitCollectionDidChange. Is the supported approach to update detents in place during the transition coordinator, and which callback is guaranteed to run after the sheet’s container has its final bounds?

The same .pageSheet is edge-to-edge on the folded phone and an inset sheet on the unfolded display, because the size class is regular. Our home sheet used to include its own tab bar so it could cover the real one. On the inner display that produces two tab bars. Should a phone-style edge-to-edge sheet on the inner display be requested with a specific modalPresentationStyle or UISheetPresentationController flag, rather than inferring it from “sheet width ≈ window width”?

When the automatic sidebar is active, a dimming layer covers the selected child. We cannot find a public property to disable it. Is that dimming UITabBarController’s own overlay, and is there a supported way to keep the selected controller fully interactive while the sidebar is visible?

On iOS 27 we set sidebar.preferredPlacement = .tabBar and sidebar.preferredLayout = .tile, and we also set mode = .tabBar. After unfolding, a sidebar can still appear and dim the content underneath. What is the correct combination so a five-item tab bar stays a tab bar on both Duo displays?

We create the window once in scene(_:willConnectTo:options:) with windowScene.coordinateSpace.bounds. After a fold, should that same scene’s screen.bounds and coordinateSpace.bounds animate to the new display, or does UIKit discard the session and deliver a new scene we must attach the window to?

We currently dismiss and rebuild a presented sheet whenever horizontalSizeClass changes. That also fires for rotation and for Split View or Stage Manager resizing. Is there a callback or geometry value that means “the device folded or unfolded,” separate from a normal size transition?

Hello everyone, We recently (a week ago) released our app, which includes an App Clip as a target. Before going live, we thoroughly tested the App Clip functionality using both the "Local Experience" and the "_XCAppClipURL" method. During testing, everything worked seamlessly. After going live, when we manually create QR codes using the default App Clip URLs, such as: https://appclip.apple.com/id?p= https://appclip.apple.com/id?p=&clip= The App Clip card is displayed, and the functionality works as expected. However, we encountered an issue where scanning the App Clip QR codes displays the message: "No usable data found." Our App Clip QR codes are dynamically generated with URLs in the format: https://example.com/clip?id= We implemented an advanced App Clip experience with the URL: https://example.com/clip This advanced App Clip experience is currently showing the status "Received" in App Store Connect. If this issue is due to the "Received" state of the advanced App Clip experience. Here are the key implementation details for your reference: We have added the domain "appclips:example.com" to the App Clip target's entitlement. The AASA (Apple App Site Association) file is hosted at https://example.com/.well-known/apple-app-site-association This file has been validated successfully and includes the correct entries for App Clips. The domain URL is "validated" status on App Store Connect. The Advance app clip is in "Received" status. The diagnostic for the URL is showing like a screen shot attached. This issue is critical for our marketing and user adoption. Could any of you please assist us in identifying and resolving this issue? If additional details or documentation are needed, we are happy to provide them promptly. Thank you for your support and assistance in this matter.