Since updating to macOS 14.4 (23E214) (I think) I can no longer run my App with target "My Mac (Designed for iPad)". The error is: Runningboard has returned error 5. Please check the system logs for the underlying cause of the error. Looking in console: System Policy: Xcode(39249) deny(1) file-read-data /private/var/db/MobileIdentityService/Configuration/Version.plist Interestingly, renaming the bundle id, build and run (fails too) and renaming back allows it to run once. Perhaps this is a bug in whatever is enforcing it not to run. Nothing else (clean, delete derived data, delete app container) allows it to run.

I have built a mergeable framework for distribution using Xcode 15. But when I try to merge it into an App target using -merge_framework in "Other linker flags", I get the error "Unknown argument: '-merge_framework'"? I'm not sure if the new linker is being used, but I assumed it would be used by default and I'm not sure of a way to enable it if not.

I want to support iOS 12+, but also want to use a SwiftPM package that only supports iOS 13+. The SwiftPM library is dynamic, so I want to build it, copy it to Frameworks, but not link to it, and then load it at runtime on iOS 13+. The last step is not too complex: if(@available(iOS 13, *)) { dlopen("MySwiftPMPackage.framework/MySwiftPMPackage", RTLD_LAZY); Class MySwiftPMPackageViewController = NSClassFromString(@"MySwiftPMPackageViewController"); // create an instance of `MySwiftPMPackageViewController` and use it } This works if I add the package to my target in "General > Frameworks, Libraries..." and "Build Phases > Target Dependencies" and then remove it from "Link binary with libraries" (despite the crash there in Xcode 14 the first time I try). It will then run on iOS 12 and iOS 13+. The problem is, every time I reload the project, the library is added back to "Link binary with libraries", presumably because the package refreshes. Is there any way to prevent it from being added back there?

I use GCKeyboard to detect key events, but if there is a text field on screen then arrow keys will cause the text field to become first responder due to the new _UIFocusEngineRepeatingPressGestureRecognizer automatically added to the window in iOS 16. Other than removing those manually, is there a way to prevent this behaviour?

I'm trying to build a framework supporting Apple Silicon with Mac Catalyst. The project builds fine in Xcode with the "Any Mac" destination. If I use the command xcodebuild -project "project.xcodeproj" -configuration "Release" -scheme "MyScheme" -destination "generic/platform=macOS,variant=Mac Catalyst,name=Any Mac" I get the error xcodebuild: error: Unable to find a destination matching the provided destination specifier: { generic:1, platform:macOS, variant:Mac Catalyst, name:Any Mac } Unsupported device specifier option. The device “My Mac” does not support the following options: name Please supply only supported device specifier options. ... Ineligible destinations for the "MyScheme" scheme: { platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Any iOS Device } { platform:iOS Simulator, id:dvtdevice-DVTiOSDeviceSimulatorPlaceholder-iphonesimulator:placeholder, name:Any iOS Simulator Device } { platform:macOS, variant:Mac Catalyst, name:Any Mac } I'm not sure why the destination is listed as ineligible when it builds correctly in Xcode, or why xcodebuild seems to use the "My Mac" device when generic is enabled. How can I build for Mac Catalyst on Apple Silicon with xcodebuild?