@Bikrrr I just installed Xcode 27.2 Beta 3 and I created an iPhone Duo 27.2 simulator. It is still just Settings and Safari. :( Oops - I must have gotten 27.2 Beta 3 just a few hours before 27.2 RC came out. I need to do another download.

Please return this very useful feature. Filed FB25215831.

@elementarteilchen How are you adding the table view to the sheet? I had a similar issue where an inset grouped table view was appearing incorrectly as you are experiencing. In my case it came down to removing some references to safeAreaLayoutGuide in constraints being used to embed a UITableViewController in a container view controller. Once that was done the table view showed correctly on the Duo as well as still working on other devices and other versions of iOS.

FB25167902 has been submitted to cover this request.

FYI - I've submitted FB25167902 to cover the request for the Save, Edit, and Edit/Done buttons to be updated with icons. This enhancement request is UIKit specific.

Thanks Travis. I'm using UIKit. I've already implemented my own custom Edit/Done button using icons and it is working fine. I'm curious about the .axisBehavior you show in the SwiftUI code. Is there a UIKit equivalent? I don't see any mention of axisBehavior in the Xcode 27.1 developer documentation. And I don't see anything similar for UIBarButtonItem (or UIBarItem).

I'm dealing with issue as well. So far I'm changing my standard Edit buttons to use the "pencil" icon (no circle or square outline). And for the standard editButtonItem ("Edit"/"Done") button, I'm using "pencil" and "checkmark". An enhancement request should be filed requesting that these standard buttons be updated for the Duo to use icons as appropriate so every app doesn't need to create their own solution.

Please note that the simple code I posted constrains the size on both the Mac and on the iPad. You may want different size restrictions for the Mac and iPad.

You can set a min and max size in the UISceneDelegate method scene(_:willConnectTo:options:) by accessing the sizeRestrictions property of the UIWindowScene. Here's an example: func scene(_ scene: UIScene, willConnectTo session: UISceneSession, options connectionOptions: UIScene.ConnectionOptions) { guard let winScene = scene as? UIWindowScene else { return } if let sizes = winScene.sizeRestrictions { sizes.minimumSize = .init(width: 640, height: 480) // No smaller than 640x480 sizes.maximumSize = .init(width: .max, height: .max) // As big as the user wants } }

Keep in mind that the user can change the text size category (in the Settings app) while using your app. So your code should be listening for that change and updating the constraints as needed.

A standard UITableViewCell with a style of .value1 should give the desired results. If you want your own custom cell class with your own labels, you will need to apply one of two different sets of constraints depending on the current size category. Update the constraints any time the size category changes.

Thanks Quinn. Good information.

You do not need to plug your iPhone in to use it with Xcode. Debugging will likely be slower, but Xcode can communicate with your iOS device wirelessly.

@DTS Engineer I really appreciate the response. Very helpful. After looking into SMAppService, it does seem like a launch agent is most appropriate. The biggest issue I have now is trying to figure out how to make this work. My app and its needs are very far from simple. I have a very large data model that is stored locally in a SQLite database and the user can optionally choose to sync their data via iCloud (CloudKit). Trying to figure out how refactor all of the existing code and logic that deals with CKSyncEngine syncing, reading and writing the SQLite database, and updating the in-memory data model into the launch agent, all in a way that can be coordinated with the main GUI app (when it might happen to be running), it going to be, shall I say, challenging. Oh, and doing this in such a way that doesn't change how the iOS version currently works using background tasks.

Are your issues specific to Xcode 26.2? All of my existing behaviors works just fine with Xcode 26.0 and 26.1.1. I also had no trouble creating new custom behaviors and changing their names. I also had no issue deleting those custom behaviors. Though one note about editing a custom behavior's name. After entering the new name, you need to press the return key before clicking the Done button or the new name won't take. Perhaps that is the issue you are seeing. But I have not tested with Xcode 26.2.