I just hit this same regression myself after updating to Xcode 15.1 (from Xcode 15) today. It's pretty sad to see such an obvious regression in a minor release. Apple claims Objective-C is still fully supported (I asked about this at WWDC), so there's really no excuse for such an obvious testing miss. FWIW, selecting Extension also does not work anymore, though I don't know if I ever tried that one before. Thanks for filing feedback. I need to file a report myself when I get a chance.

This sounds similar to the issue being discussed here: https://stackoverflow.com/questions/77555891/printing-issue-running-a-designed-for-ipad-app-on-macos/77570505 I have been testing exclusively on macOS 14+ and, unfortunately, I don't have a machine running an earlier macOS version on which to test. Did you file a feedback report with Apple? I would encourage anyone encountering this problem to file their own feedback report and reference FB13420491.

I also hit this problem when trying to enable ASAN on my iOS app when running with run destination set to My Mac (Designed for iPad) (iOS 17 SDK, 14.1.1). I haven't tried the same configuration running under iOS (device or simulator) yet, as I was doing primary testing on macOS. Seems this isn't supported on MacOS Can we get an official comment on this? I would consider this to be a bug. Did you file any feedback about this problem? I just filed the following feedback for my case; I would encourage anyone else hitting this problem to file their own feedback report: FB13420394 Xcode: Running iOS 17 app on macOS with ASAN enabled crashes with error: AddressSanitizer: CHECK failed: sanitizer_mac.cpp:1215 "((ret_value)) <= (((1ULL << 36)))" (0x7ffffdffffff, 0x1000000000) (tid=497045)

If you are affected by this, please make sure that you file a report using Feedback Assistant and reference my feedback report FB12267927. Apple can only fix issues that they are aware of. So far, it seems this is not on the list of known issues, and it's unlikely to come to their attention via comments in the forum alone.

I'm not sure if it's the same as your issue, but I'm encountering a regression with IMAP + self-signed SSL certificate ("bad certificate format" -9,808), which does not occur with iOS 16.5. I've not found any workaround, so I'm unable to access my e-mail from my phone now. I filed feedback FB12267927 for this.

Seriously? One obvious application is to implement a bookmark management functionality to supplement Safari’s lousy bookmark management UI that’s not been improved in 20 years. The value of having such API should be self evident. It seems such functionality is long overdue in Safari. I see threads asking about this feature going back 11 years or more. Directing people to the feedback “black hole” is a good way to keep everyone in the dark and stifle any productive discussion.