Sorry, I did not file a bug report.

Actually once you use Xcode 13.4.1 and connect to the iOS/iPadOS 15.7 device, Xcode 14 works just fine using the iOS/iPadOS 15.7 device. I'm doing it as I type this.

@Alex J Bowden - Xcode 13.4.1 worked just fine for me in supporting iOS 15.7. If it helps, I'm running Xcode 13.4.1 on an Intel MacBook Pro with macOS 12.6. Not sure it makes a difference but I had Xcode 14.0 running and the iOS 15.7 device plugged in. I then started Xcode 13.4.1 and almost immediately the Devices screen of 13.4.1 showed that the 15.7 was ready. I closed both versions of Xcode and then restarted Xcode 14.0 and 14.0 was now happy to work with the iOS 15.7 device.

Doh!. So simple. I had created a new iOS project just to test something quick with Mac Catalyst and never even considered the iOS deployment target. Thank you.

This is no longer true. See my recent post below. AVFoundation and the AVCam demo are now supported under Mac Catalyst.

FYI - AVFoundation is now supported under Mac Catalyst.

I'd rather have a definitive answer than rely on anecdotal evidence from 1 user.

Any thoughts on my reply?

I’ve made attempts to generate touch events or directly call target/action pairs of the gestures provided by UITextInteraction but so far no luck. Too many private APIs involved for me to find a working hack along those lines.

Sorry but I am just now seeing your reply. How do the various macOS apps respond to the setting change? BTW - In my specific case, I'm using Mac Catalyst to port an iOS app to macOS. Ideally the change in setting in macOS would have the same effect as it does under iOS - the trait collection would be updated with the new size category leading to things automatically updating their size as appropriate.

Sorry, just saw your reply. This is great! This ended up being so simple - for iOS 17. Unfortunately I need to support iOS 15+ and UITextSelectionDisplayInteraction is only for iOS 17+. I've spent the last several hours trying to find a solution for iOS 16. Why is this so hard? Thanks so much at least for the iOS 17 solution. I'll keep digging for iOS 15/16. I'll post a full solution when I come up with one.

This is related to the post at https://developer.apple.com/forums/thread/749614

I actually submitted a bug report yesterday with a sample app. It's FB15458347. Thanks.

Any update on this issue? I've just discovered that my Mac Catalyst app is having the same issue ever since I updated my Mac to macOS 15.1.

Will the Xcode documentation be fixed in the next Xcode update? Should a bug report be filed in the Feedback app or is there no point since you know about the issue? Thanks.