Some Macs recently received a macOS system update which disabled the simulator runtimes used by Xcode 15, including the simulators for iOS, tvOS, watchOS, and visionOS. If your Mac received this update, you will receive the following error message and will be unable to use the simulator: The com.apple.CoreSimulator.SimRuntime.iOS-17-2 simulator runtime is not available. Domain: com.apple.CoreSimulator.SimError Code: 401 Failure Reason: runtime profile not found using "System" match policy Recovery Suggestion: Download the com.apple.CoreSimulator.SimRuntime.iOS-17-2 simulator runtime from the Xcode To resume using the simulator, please reboot your Mac. After rebooting, check Xcode Preferences → Platforms to ensure that the simulator runtime you would like to use is still installed. If it is missing, use the Get button to download it again. The Xcode 15.3 Release Notes are also updated with this information.

After enabling Source Control in Xcode 16, when I try to view the History, the app becomes unresponsive for several minutes, and the spinning beach ball appears. I’m experiencing the same issue with the latest version, Xcode 16.1 beta 2. However, in this version, the functionality works correctly for certain files, while for other files, the issue with the spinning beach ball persists. I frequently use Source Control in Xcode, and this issue is causing significant inconvenience during app development. Is there any way to resolve this?

Hi everyone, I am currently using Xcode 16.1, which only includes device support files up to iOS 16.4. However, I need to target iPhones running iOS 17 and iOS 18 (e.g., iPhone 15 and iPhone 16). Is there any way to acquire the device support files for iOS versions above 16.4 without upgrading to a new Xcode version that hasn't been released yet? I’m unable to upgrade my Xcode due to hardware limitations, but I still need to test my app on these newer devices. I’ve heard about manually adding device support files, but I’m unsure of the process or where to obtain them safely. Can anyone provide guidance or direct me to where I can find these files? Thanks in advance for your help!

hello, i want to test my app on an iPhone15 pro simulated device runnig ios 17,5 i have installed os images i have created a new simulated device But i do not see him into xcode 16 tool barr window as i want to run my app on this particular device i only a small list of devices please do not tell me again it is about some "/usr/var right acces problem" stuff i am very desapointed by new software releases that are working baddly compare to their previous version

I have a simple wrapper class around WCSession to allow for easier unit testing. I'm trying to update it to Swift 6 concurrency standards, but running into some issues. One of them is in the sendMessage function (docs here It takes [String: Any] as a param, and returns them as the reply. Here's my code that calls this: @discardableResult public func sendMessage(_ message: [String: Any]) async throws -> [String: Any] { return try await withCheckedThrowingContinuation { (continuation: CheckedContinuation<[String: Any], Error>) in wcSession.sendMessage(message) { response in continuation.resume(returning: response) // ERROR HERE } errorHandler: { error in continuation.resume(throwing: error) } } } However, I get this error: Sending 'response' risks causing data races; this is an error in the Swift 6 language mode Which I think is because Any is not Sendable. I tried casting [String: Any] to [String: any Sendable] but then it says: Conditional cast from '[String : Any]' to '[String : any Sendable]' always succeeds Any ideas on how to get this to work?

I've got a 2023 M2 MacBook Pro and used to get great battery life out of it (> 6 hours when using it for development purposes). Now however, all of a sudden, that has dropped off a cliff, and the only thing that has changed is Xcode 16 has appeared. As I'm compiling a project I can literally see the % amount of the battery charge remaining tick down in front of my eyes as I watch. I just compiled a project twice and during that time the battery dropped from from %89 to %79 and Xcode is listed as a culprit using significant battery drain. Anybody else noticed anything similar? Anything that can be done to to decrease Xcode's battery drain?

I am trying to add a Swift Package from a private Gitlab repository to my Xcode 16 project, and it fails. First symptom is Unable to load the Read Me in the Xcode SPM package browser. And when I add the package, I get a repo.git could not be resolved error. I've used ProxyMan to sniff the network calls issued by Xcode, and it looks like my Gitlab credentials are not provided as part of the GET request when, for example, Xcode tries to fetch the README.md file from the repository. And when I try to add the package, there are no HTTP network calls issued by Xcode at all. I have tried adding a Gitlab account to Xcode's Accounts preference pane, and entering the repository's credentials directly when adding the package. Both yield the same result. Here's a screen capture of Xcode trying to fetch the README: https://share.cleanshot.com/FNRHm6fq I am unable to test this in Xcode 15, as I have upgraded my Mac to Sequoia and Xcode 15 can't be installed on this version of macOS. I have submitted FB15370281 for this issue.

This project had been stable for years, doing hundreds of updates for customers but XCode has suddenly started generating lists of errors with every build. I have sent in reports in Feedback Assistant but never get any response. Is this a recent regression in XCode? This project is Objective-C++ with C++11, clang with lots of assembly for both CPU families. Cleaning up ... Building XCode Project... --- xcodebuild: WARNING: Using the first of multiple matching destinations: { platform:macOS, arch:arm64, id:00006001-000851861A42401E } { platform:macOS, arch:x86_64, id:00006001-000851861A42401E } { platform:macOS, name:Any Mac } --- xcodebuild: WARNING: Using the first of multiple matching destinations: { platform:macOS, arch:arm64, id:00006001-000851861A42401E } { platform:macOS, arch:x86_64, id:00006001-000851861A42401E } { platform:macOS, name:Any Mac } 2024-10-02 22:42:09.000 xcodebuild[3235:7055835] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103 Details: createItemModels creation requirements should not create capability item model for a capability item model that already exists. Function: createItemModels(for:itemModelSource:) Thread: <_NSMainThread: 0x6000033fc2c0>{number = 1, name = main} Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide. 2024-10-02 22:42:09.000 xcodebuild[3235:7055835] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103 Details: createItemModels creation requirements should not create capability item model for a capability item model that already exists. Function: createItemModels(for:itemModelSource:) Thread: <_NSMainThread: 0x6000033fc2c0>{number = 1, name = main} Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide. 2024-10-02 22:42:09.000 xcodebuild[3235:7055835] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103 Details: createItemModels creation requirements should not create capability item model for a capability item model that already exists. Function: createItemModels(for:itemModelSource:) Thread: <_NSMainThread: 0x6000033fc2c0>{number = 1, name = main} Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide. 2024-10-02 22:42:09.000 xcodebuild[3235:7055835] [MT] DVTAssertions: Warning in /System/Volumes/Data/SWE/Apps/DT/BuildRoots/BuildRoot11/ActiveBuildRoot/Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-22269/IDEFoundation/Provisioning/Capabilities Infrastructure/IDECapabilityQuerySelection.swift:103 Details: createItemModels creation requirements should not create capability item model for a capability item model that already exists. Function: createItemModels(for:itemModelSource:) Thread: <_NSMainThread: 0x6000033fc2c0>{number = 1, name = main} Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide. 2024-10-02 22:42:09.000 xcodebuild[3235:7055835] [MT] DVTAssertions: Warning in === CUT 10000 LINES of XCode Errors === PS: the maximum length on these forum posts is crazy small!

I am trying to add an XCUITest target to an existing application. When I try to run the tests, I get the error "Invalid configuration: MyProjectUITests sets both USES_XCTRUNNER and either TEST_HOST or RUNTIME_TEST_HOST". I have seen information stating that it might be because I have multiple apps built from different build configurations in the same scheme, but I could not resolve the issue with any of the suggestions I saw. I've attached a screenshot of the error message and a link to a project stripped down to just the existing configuration to help with diagnosing this issue. I would really love to be able to get some UI tests running. My Project

When using rvictl, I notice that it creates 2 interfaces. One of which establishes a link local connection between the iPhone and the Mac. What is this connection for? Why is it so talkative? and why can I only bring one of the created interfaces down but not the other? When I try to bring down the interfaces with the ifconfig enX down command it stops the DHCP requests and several TCP DUP ACK, but the other interface is persistent and will not stop talking. Can someone explain what type of traffic is being transmitted between the Mac and the iPhone?

Translated Report (Full Report Below) Process: Xcode [32132] Path: /Applications/Xcode.app/Contents/MacOS/Xcode Identifier: com.apple.dt.Xcode Version: 16.0 (23051) Build Info: IDEApplication-23051000000000000~2 (16A242d) App Item ID: 497799835 App External ID: 869020508 Code Type: ARM-64 (Native) Parent Process: launchd [1] User ID: 501 Date/Time: 2024-10-02 10:43:40.6653 -0500 OS Version: macOS 14.6.1 (23G93) Report Version: 12 Anonymous UUID: 0E2EB149-11CD-556E-AD70-0143A1FB92FE Time Awake Since Boot: 5100 seconds System Integrity Protection: enabled Crashed Thread: 9 Dispatch queue: com.apple.root.default-qos Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6 Terminating Process: Xcode [32132] Application Specific Information: abort() called Application Specific Signatures: NSInvalidArgumentException Application Specific Backtrace 0: 0 CoreFoundation 0x000000019fa0a2ec __exceptionPreprocess + 176 1 DVTFoundation 0x0000000102e545cc DVTFailureHintExceptionPreprocessor + 388 2 libobjc.A.dylib 0x000000019f4ee158 objc_exception_throw + 60 3 CoreFoundation 0x000000019fabc56c -[NSObject(NSObject) __retain_OA] + 0 4 CoreFoundation 0x000000019f973f3c forwarding + 1580 5 CoreFoundation 0x000000019f973850 _CF_forwarding_prep_0 + 96 6 IDEDistribution 0x000000010ce4c810 -[IDEDistributionProcessingPipelineContext packagePathForVariant:] + 648 7 IDEDistribution 0x000000010ce40fec -[IDEDistributionCreateIPAStep name] + 88 8 IDEDistribution 0x000000010ce4a760 __98-[IDEDistributionProcessingPipeline observationForPhaseStateChanges:stepIndex:pipelineStepsCount:]_block_invoke + 96 9 DVTFoundation 0x0000000102f337d4 -[NSObject(DVTObservingConvenience) dvt_newObserverForKeyPath:options:owner:creationBacktrace:withHandlerBlock:] + 380 10 DVTFoundation 0x0000000102f345a4 -[NSObject(DVTObservingConvenience) dvt_newObserverForKeyPath:options:withHandlerBlock:] + 124 11 IDEDistribution 0x000000010ce4a624 -[IDEDistributionProcessingPipeline observationForPhaseStateChanges:stepIndex:pipelineStepsCount:] + 152 12 IDEDistribution 0x000000010ce4a998 -[IDEDistributionProcessingPipeline processForThinningVariant:distributionItem:stepClass:stepIndex:pipelineStepsCount:error:] + 420 13 IDEDistribution 0x000000010ce4a150 -[IDEDistributionProcessingPipeline process:] + 1112 14 IDEDistribution 0x000000010ce567e8 -[IDEDistributionPackagingStep loadDrivableFromExportOptions:error:] + 204 15 IDEDistribution 0x000000010ce1de20 -[IDEDistributionDriver runWithDestinationPath:wantsExportStep:] + 2000 16 IDEDistribution 0x000000010ce75eb0 $s15IDEDistribution29RecoverableDistributionDriverC3runyyFyyYbcfU + 160 17 IDEDistribution 0x000000010ce7626c $sIeg_IeyB_TR + 28 18 libdispatch.dylib 0x000000019f703750 _dispatch_call_block_and_release + 32 19 libdispatch.dylib 0x000000019f7053e8 _dispatch_client_callout + 20 20 libdispatch.dylib 0x000000019f708580 _dispatch_queue_override_invoke + 928 21 libdispatch.dylib 0x000000019f716ea8 _dispatch_root_queue_drain + 392 22 libdispatch.dylib 0x000000019f7176b8 _dispatch_worker_thread2 + 156 23 libsystem_pthread.dylib 0x000000019f8b1fd0 _pthread_wqthread + 228 24 libsystem_pthread.dylib 0x000000019f8b0d28 start_wqthread + 8 Thread 0:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x19f874df4 mach_msg2_trap + 8 1 libsystem_kernel.dylib 0x19f8875e4 mach_msg2_internal + 80 2 libsystem_kernel.dylib 0x19f87d9c4 mach_msg_overwrite + 476 3 libsystem_kernel.dylib 0x19f875178 mach_msg + 24 4 CoreFoundation 0x19f995680 __CFRunLoopServiceMachPort + 160 5 CoreFoundation 0x19f993f44 __CFRunLoopRun + 1208 6 CoreFoundation 0x19f993434 CFRunLoopRunSpecific + 608 7 HIToolbox 0x1aa13d19c RunCurrentEventLoopInMode + 292 8 HIToolbox 0x1aa13cfd8 ReceiveNextEventCommon + 648 9 HIToolbox 0x1aa13cd30 _BlockUntilNextEventMatchingListInModeWithFilter + 76 10 AppKit 0x1a31f2cc8 _DPSNextEvent + 660 11 AppKit 0x1a39e94d0 -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 700 12 AppKit 0x1a31e5ffc -[NSApplication run] + 476 13 IDEKit 0x106c4f524 -[IDEApplication run] + 60 14 AppKit 0x1a31bd240 NSApplicationMain + 880 15 dyld 0x19f52b154 start + 2476

I’ve developed an Apple Watch extension for an existing iOS app. When I run the app on the watch via Xcode using the simulator, everything works fine. However, when I try to install it on my iPhone, the Watch app doesn’t show it in the "Available Apps" list, so I can't install it on the watch. The Apple Watch is connected to my iPhone, and I can see other apps available for installation without any issues. I also created a brand new project with watchOS support to troubleshoot, but the same problem occurred. Any ideas on how to resolve this?

I'm trying to upload a build to app store connect. It's a build from a Unity project with the polyspatial SDK, and I also need to include a c++ library, which I've added as a dylib signed with the same provisioning profile as the app. The profile is an Apple Distribution profile created from an enterprise account. It succesfully uploads to Appstore connect, but fails with the following error message: ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it. This is unhelpful as I'm using a current version of Xcode. I've read that it's a provisioning issue, but I'm using the provisioning profile for apple distribution on an enterprise account, not an ad hoc profile. I've tried manually adding the SwiftSupport folder from the Xcode toolchain to the ipa/xarchive, resign and upload with Transporter, but that doesn't work. After spending a day trying to troubleshoot this, I'm at a loss. Any help with this is much appreciated. Note: I can sideload the app onto an AVP with an ad hoc build and ad hoc provisioning profile (I've added the signed dylib to build phases Link with Libraries and Embed Frameworks). Somehow this doesn't need the SwiftSupport?

Hi, the really handy shortcut to refresh the preview canvas in Xcode via keyboard shortcut option+command+p is not available anymore (!?!?). Also the menu-entry 'Canvas' in the previous versions <16.1 is not anymore. Did I miss any option to enable this again or was this some kind of silly cleanup driven by Apple?

Hi, I am encountering a linking issue with a project for an iOS .NET MAUI application that I am developing using Visual Studio 17.11.4. This project includes a custom static library (.a). The custom static library (.a) depends on the libxml2 library. However, it appears that libxml2 is not included in Xcode 15.4 (Sonoma OS), resulting in the following error: error : Undefined symbols for architecture arm64: error : "_xmlBufferCreate", referenced from: .... I have set the following additional arguments for compilation: -cxx -gcc_flags "-lz -lxml2". Despite my efforts to install libxml2 using Homebrew, I have not been successful. Could you please advise on how I can resolve this issue? Specifically, what is the path that Xcode uses to include libxml2?

I have Xcode 16 and iPadOS 18.0 I am trying other connect the iPad to Xcode. It started with preparing iPad and Xcode will continue when the operation completes. It hangs now for 2 hours. What is wrong with it? There is lot of space at the iPad IOS 18.0 (22A3354) Pad Pro (11-inch) (2nd generation) It worked earlier with Xcode 15 and iPadOS 17

I have a small Swift command line tool for MacOS. I have added a small demo CoreML model to the project and can correctly load the model in Swift like let model = try! Matcher_512x256(). However, once I add a single C++ or Objective C file to the Compile Sources of my build target, the compilation fails with an error stating that the model cannot be found: "...ModelAndCpp/ModelAndCpp/main.swift:11:18 Cannot find 'Matcher_512x256' in scope". Please help me resolve this. Does XCode change into a different "compilation mode" once a C++ file is present which might cause this error? XCode version is 16A242d. I can reproduce the issue with a tiny repository (5 small files) which I have uploaded here on GitHub. To reproduce the issue, simply remove the .m and .cpp files from Compile Sources to compile correctly, or add one of them to get the error. Thank you and best regards, Manuel

When requiring some components from the SwiftUI framework, Xcode 16.0 recommends importing SwiftUICore in its quick fix error suggestions. Previously, SwiftUI would be suggested. What is the difference between the two and which is the recommended one for importing?

Can Xcode15 compile on an iPhone of iOS18？I want to update my iPhone to iOS18， but I do not want to update my Xcode.

Hello! I have been successfully building out my Xcode project in the past few months to my iPhone 15. I recently got a new iPhone 16 pro and have been having a hell of a time trying to figure out how to build to my new phone. Here's the error I am getting: Unknown file type in '/Users/username/Desktop/filename/Libraries/libiPhone-lib.a' please help! Any suggestions would be greatly appreciated. NOTE: I am using a M1 laptop with Sequoia OS

When I copy and paste example code in apple developer documentation, LongPressGesture does not work as expected in Xcode Version 16.0 (16A242) and iOS 18. It seems updating(_:body:) method does not work when used with LongPressGesture. When I make a breakpoint in updating(_:body:) method and long press the blue circle on the screen of simulator(or device), it is expected to be caught in breakpoint or it is expected that color of circle turns from blue to red to green. However, it is not caught in breakpoint and never turns to red. Question of Stackoverflow is about same issue and I can not use onLongPressGesture method to implement required feature of my app. I submitted bug report via Feedback Assistant and my report's ID is FB15127375 and FB15173175. Please tell me if there is any investigation about this issue. Development environment: Xcode Version 16.0 (16A242), macOS 14.5 Run-time configuration: iOS 18.0