“Xcode”

I have an orphaned asset folder taking up 9.13GB located at: /System/Library/AssetsV2/com_apple_MobileAsset_iOSSimulatorRuntime/c0d3fd05106683ba0b3680d4d1afec65f098d700.asset It contains SimulatorRuntimeAsset version 18.5 (Build 22F77). Active Version: My current Xcode setup is using version 26.2 (Build 23C54). I checked the plist files in the directory and found what seems to be the cause of the issue: The Never Collected Flag: The Info.plist inside the orphaned asset folder explicitly sets the garbage collection behavior to NeverCollected: __AssetDefaultGarbageCollectionBehavior NeverCollected The Catalog Mismatch: The master catalog file (com_apple_MobileAsset_iOSSimulatorRuntime.xml) in the parent directory only lists the new version (26.2). Because the old version (18.5) is missing from this XML, Xcode and mobileassetd seem to have lost track of it entirely. What I Have Tried (All Failed) Xcode Components: The version 18.5 does not appear in Settings -> Components, so I cann

Is it mandatory for all developers to migrate to Xcode 26 starting from April 28, 2026? What happens if a developer submits or distributes a build created using Xcode 16 after April 28, 2026? Will it still be accepted or supported? Our app is distributed only via an internal company portal (not through the App Store). In this case, are we still required to build and distribute the app using Xcode 26 after April 28, 2026? If a hotfix is required before our next planned release (July 2026), how safe is it to use the UIDesignRequiresCompatibility flag as a temporary solution, assuming Xcode 26 becomes mandatory? Are there any risks or limitations associated with this approach? What are the potential issues if a team continues development on Xcode 16 while others have migrated to Xcode 26? For example, could there be compatibility, build, or integration challenges in such a mixed environment? If the UIDesignRequiresCompatibility flag is used as a temporary wor

Hi everyone, I'm building an iOS app using Capacitor 6 with Swift Package Manager (SPM). I have a custom native plugin (AppleIAPPlugin) for StoreKit 2 In-App Purchases that lives in the App target (not as an SPM package). Despite compiling successfully, the JavaScript bridge throws: AppleIAP plugin is not implemented on ios Setup AppleIAPPlugin.swift: swift import Foundation import Capacitor import StoreKit @objc(AppleIAPPlugin) public class AppleIAPPlugin: CAPPlugin, CAPBridgedPlugin { public let identifier = AppleIAPPlugin public let jsName = AppleIAP public let pluginMethods: [CAPPluginMethod] = [ CAPPluginMethod(name: getProducts, returnType: CAPPluginReturnPromise), CAPPluginMethod(name: purchase, returnType: CAPPluginReturnPromise), CAPPluginMethod(name: restorePurchases, returnType: CAPPluginReturnPromise), CAPPluginMethod(name: getCurrentEntitlements, returnType: CAPPluginReturnPromise), CAPPluginMethod(name: openManageSubscriptions, returnType: CAPPluginReturnPromise), ] @objc func getProducts(_ call

According tho Claude, The crash is clearly a bug in Xcode's built-in AI chat feature (IDEIntelligenceChat), not an authentication issue or anything on your end. What the crash log shows: The crash is happening in IDEIntelligenceChat — specifically in ChatInputEditorView.updateView and SourceEditorDataSource.ideChat_gracefullyApplyChangesToReflect. It's a SIGTRAP (assertion/precondition failure) triggered while SwiftUI is trying to lay out the AI chat panel. This is an Apple bug in Xcode 26.2 itself.

Hi, I am developing instant snapshot backup solution for macOS using Endpoint Security. We have stumbled upon a Kernel Panic when using fclonefileat API. We are catching a kernel panic on customer machines when attempting to clone the file during ES sync callback: panic(cpu 0 caller 0xfffffe002c495508): apfs_io_lock_exclusive : Recursive exclusive lock attempt @fs_utils.c:435 I have symbolized the backtrace to know it is related to clone operation with the following backtrace: apfs_io_lock_exclusive apfs_clone_internal apfs_vnop_clonefile I made a minimal repro that boils down to the following operations: apfs_crash_stress - launch thread to do rsrc writes static void *rsrc_write_worker(void *arg) { int id = (int)(long)arg; char buf[8192]; long n = 0; fill_pattern(buf, sizeof(buf), 'W' + id); while (n < ITERATION_LIMIT) { int file_idx = n % NUM_SOURCE_FILES; int fd = open(g_src_rsrc[file_idx], O_WRONLY | O_CREAT, 0644); if (fd >= 0) { off_t off = ((n * 4096) % RSRC_DATA_SIZE); pwrite(fd, buf, sizeof(buf