Hi. Today we upgraded to Xcode 27 and installed the iOS 27 runtime component. Now storyboards cannot be opened. Xcode only displays "Loading iOS 27.0..." Besides, we cannot create simulators either. iOS 27 runtime appears missing even though it is installed. We tried removing and reinstalling the runtime but it didn't work. Right now all development came to a halt. Please help.

I can no longer use Codex within Xcode anymore because it says it's unsupported. gpt-5.5 has been out for several months...please update for support for it. I don't want to have to jump through a bunch of hoops using Terminal just to be able to use Codex in Xcode.

Large companies/applications are good to go for Duo release. Is there a timeframe when Xcode 27.1 will be available so we can build and submit to App Store in time for Duo release? Any guidance around this?

Environment Xcode 27.1 (27A9269) Simulator runtime: iOS 27.1 (24A94401) Device: iPhone Duo simulator (unfolded) macOS 26.7.1 (25G241), Apple silicon Mac Hardware keyboard connected (default Simulator setting) Summary After locking the iPhone Duo simulator with ⌘L and unlocking it, the whole display stays dimmed and appears unresponsive. Both apps in split view are affected. Pressing the ⌘ key once restores the screen immediately. This reproduces with only system apps (Settings + Safari), so it does not appear to be app-specific. Steps to reproduce Boot the iPhone Duo simulator (iOS 27.1) and unfold it. Open Settings and Safari side by side in split view. Press ⌘L to lock the device. Unlock (swipe up on the lock screen). Expected The display returns to normal brightness and both apps respond to input. Actual The entire display, including both split-view apps, stays dimmed. Taps appear to do nothing while it is dimmed. Pressing ⌘ once immediately restores normal brightness. After recovering, Settings had navigated to a different page, which suggests some taps were delivered while the screen was dimmed. Notes It looks like the simulator misses the ⌘ key-up when ⌘L locks the device, so iOS behaves as if ⌘ is still held (the hold-⌘ shortcut overlay dimming the screen). Locking with Device ▸ Lock from the Simulator menu avoids the ⌘ modifier entirely. In one case the dimmed state persisted across relaunching an app and only cleared after rebooting the simulator. We first hit this while testing our own app in split view, where it looked like an app hang. Sampling the app's process showed the main thread idle. Workaround Press ⌘ once after unlocking, or lock with Device ▸ Lock instead of ⌘L. Has anyone else seen this on the iPhone Duo simulator, or is this a known issue?

Hi everyone, I am developing an iOS companion app with an integrated watchOS component (a golf swing tracking tool using CoreMotion). I have run into an issue where the watchOS app gets stuck indefinitely in the "Installing..." state and never finishes installing on the physical Apple Watch. Environment (All on latest public releases): Xcode Version: Latest release (Xcode 18.x) macOS Version: Latest release (macOS Sequoia / latest version) iOS Version: Latest release (iOS 20.x) watchOS Version: Latest release (watchOS 13.x on Apple Watch Ultra 2) Deployment Target: Matched to latest minimum deployments Signing: "Automatically manage signing" enabled with an active Apple Developer Program account Steps to Reproduce: Connect the iPhone to the Mac via a physical cable. Select the iOS target in Xcode and successfully run/install the companion app onto the iPhone. Launch the stock Watch app on the paired iPhone. Scroll down to the "Available Apps" section, locate the development app, and tap "Install". The circular progress indicator starts spinning with the status "Installing...", but it remains in this state indefinitely (waited over 2 hours) without ever completing, timing out, or surfacing an error alert on either the iPhone or the Apple Watch. Troubleshooting Already Verified: Bundle ID Hierarchy: iOS App: com.company.appname Watch App: com.company.appname.watchkitapp Both targets share the exact same Development Team, signing certificate, and provisioning profiles. Developer Mode: Explicitly enabled and rebooted on the Apple Watch (Settings -> Privacy & Security -> Developer Mode). Also verified as enabled on the host iPhone. Connectivity & Cache: Cleared Xcode DerivedData (rm -rf ~/Library/Developer/Xcode/DerivedData). Performed hard reboots on both the iPhone and the Apple Watch to terminate any hung background sync daemons (installd / CoreDevice). Ensured both devices and the Mac are on the same Wi-Fi network with Bluetooth turned on. Questions: Under the current CoreDevice architecture, is installing local debug builds via the iPhone's stock Watch app still supported, or does it silently fail because the physical Apple Watch's UDID is not directly provisioned during an iOS-only build? Which subsystem in macOS Console.app (e.g., com.apple.dt.CoreDevice, com.apple.StreamingExtractor, or installd) is best for tracking the exact error/timeout code when the watch installation hangs? What is the currently recommended workflow to deploy and debug a paired watchOS target directly onto physical hardware? Any insights from the team or community would be greatly appreciated!

When I add an SVG file to an asset catalog Image Set, the Attributes Inspector shows Color Space: Generic RGB instead of sRGB. The rendered color on device does not match the hex value in the SVG.

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": <key>__AssetDefaultGarbageCollectionBehavior</key> <string>NeverCollected</string> 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 cannot delete it via the GUI. Simctl: xcrun simctl list runtimes does not list this version. Running xcrun simctl runtime delete 22F77 fails with: "No runtime disk images or bundles found matching '22F77'." Manual Deletion: sudo rm -rf [path] fails with "Operation not permitted", presumably because /System/Library/AssetsV2 is SIP-protected. Third-party Tools: Apps like DevCleaner do not detect this runtime (likely because they only scan ~/Library or /Library, not /System/Library). Has anyone found a way to force the system (perhaps via mobileassetd or a specific xcrun flag) to re-evaluate this folder and respect a deletion request? I am trying to avoid booting into Recovery Mode just to delete a cache file. Any insights on how AssetsV2 handles these "orphaned" files would be appreciated.

Hello Hivemind! We are facing an issue that I think many people do these days - how to successfully work from home and specifically how to debug an iPhone from a remote location. We are working from home due to COVID 19, we're using VNC to connect to our Mac's at the office. For most needs, we can use that Mac's iOS simulator. However some of our teams are working on Network Extension to develop VPN which is not supported by the simulator. We are looking for a solution to enable them to work efficiently. There can be 2 options: Debug over the internet - use a local iPhone so we can control it manually, and be able to connect to it with the remote Mac (the one in the office) that is running Xcode and debugging. Have the device connected to the remote mac, and be able to control it remotely. This option should be direct control via that Mac's USB, because since we are developing a VPN product - we sometimes have network issues during debug. The solution should be - Fast enough to allow debugging of networking issues (UI waits on you, but servers don't. So we need to be able to make flows that won't break if debugger is slow). Reliable enough so we don't need to have "some guy in the office". Any suggestion will be most appreciated, thanks!

On macOS 26.6 (25G72), Xcode 26.6 (17F113), xcodebuild -showBuildSettings -json exits naturally with code 74 and reports that the project cannot be read / does not exist. Minimal control: A synthetic three-file .xcodeproj with one iOS application target, one shared scheme and an internal workspace. It contains no app source, package dependencies, extensions or build scripts. Its plist/XML and object references passed static validation. This does not establish that Xcode accepts the project. Reproduction outline: Run xcodebuild for this control under a custom sandbox-exec profile, with a clean environment, isolated HOME/cache/DerivedData, Release configuration, iphoneos SDK, generic/platform=iOS, automatic package resolution disabled, signing disabled, and -showBuildSettings -json. No build or device operation is requested. The profile keeps the control project read-only, restricts access to protected host data, and denies network and Simulator/device services. The exact profile is not attached to this question. Observed: The synthetic control also exits 74 and produces no settings JSON. Adding only a literal file-read-metadata allowance for the public data-volume root removed that observed denial, but exit 74 remained. Separate Foundation canonical-path and volume-URL metadata queries passed under the resulting policy. Owned-process diagnostics did not establish a causal link between another denial and the loader failure. We have not established the root cause or an Xcode regression. We understand that custom SBPL is not documented for third-party use. Is there a supported diagnostic interface that exposes the loader's underlying NSError/domain/code at this stage, before building? Do result bundles cover this specific early failure, or is another documented diagnostic method required?

M4 Mac Mini: Xcode generates private keys with wrong label - codesigning impossible Background This is a follow up to my November 2024 thread "Keychain issues after installing backup on new Mac" which was closed because I had a temporary workaround. That workaround using my wife's MacBook Air for signing is not sustainable. I used AI assistance to determine the root cause. My DTS case 102877839447 is open but has not yet been forwarded to a DTS engineer. Environment Mac Mini M4, macOS 15.4.1 (Build 25E253) Xcode 26.4.1 (17E202) Team ID: Q23726668V (Computerade Products) Working comparison machine: MacBook Air, macOS 15.3 Precise Bug — Reproducible Every Time Every time Xcode generates a new certificate and key pair on my Mac Mini: Certificate: Apple Development: Michael Birch (9KD5TCGGHG) ✅ Private key: Apple Development: Michael Birch (Computerade Products) ❌ The key uses the organization name instead of the certificate identifier. They never pair as a valid codesigning identity. security find-identity -v -p codesigning always returns 0 valid identities. Cryptographic Evidence The internal application labels confirm the keys are cryptographically unrelated to their certificates: Key internal application label: 53C26EB056997276B5E938258D00665ACABD1F0F Certificate public key hash: 57cd1af4a9162f26b1a6d750e05a63a2166b75ff These do not match ❌ Confirmed Eliminated As Causes Keychain search list corruption — found and fixed Partition list — set correctly Access control — set to allow all applications Full Disk Access — granted to Xcode Xcode caches and preferences — completely cleared Login keychain — completely reset Orphaned certificates and keys — all removed SIP enabled, system fully up to date Valid P12 Import Also Fails A p12 exported from the working MacBook Air and cryptographically verified as a matched pair also fails on the Mac Mini: security import returns MAC verification failed Keychain Access import returns OSStatus -2 Importing certificate and key separately as PEM files succeeds but they are not recognized as a valid identity pair despite matching application labels A3F3F193B7896DA9055353F59AB450778CB09AE7 Question Is there a known issue with M4 Mac Mini keychain infrastructure where private keys are generated with incorrect internal application labels? Is there a lower level diagnostic or fix beyond what the security command provides? The problem is specific to my Mac Mini M4 and persisted thru more than a year of Mac OS and xCode updates.

My project uses spm https://github.com/airbnb/lottie-spm.git. When I use xcode cloud in XCode to create a workflow, it asks me to connect airbnb in github. In fact, this repo is public, it's unnecessary. Then I tried to fork this https://github.com/airbnb/lottie-spm.git to my own domain, and xcode cloud created the workflow, but it was failed: Build - iOS encountered a failure that caused the build to fail. Issue an out-of-date resolved file was detected at /Volumes/workspace/repository/xxx.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved, which is not allowed when automatic dependency resolution is disabled; please make sure to update the file to reflect the changes in dependencies. Running resolver because the following dependencies were added: 'lottie-spm' (https://github.com/xxx/lottie-spm.git)2026-10-04 03:11:57.970 xcodebuild[2735:14329] Writing error result bundle to /var/folders/zn/fgtz2b0j5014hc3fs53llxg80000gn/T/ResultBundle_2026-04-10_03-11-0057.xcresult Finally, I modify the spm url to original and commit, push the project, it build successfully.

Using devicectl 518.33, I need to check only whether two files exist in an installed development app's App Group container, without launching the app, copying the container, or reading file contents. The request uses: device info files --domain-type appGroupDataContainer --domain-identifier group.ru.ordo.app --subdirectory OrdoEnforcement --no-recurse --verbose --json-output /dev/stdout The device was wired and paired. The command returned exit 1, CoreDevice.ActionError code 3. File existence remains unknown. The local help lists appGroupDataContainer but does not specify its domain-identifier contract. Is metadata-only listing of an iOS App Group container supported? What exact identifier and access prerequisites are required? Is there a documented alternative that does not launch the app, copy its container, or read file contents?

Hello! I'm new to xcode and am developing an iOS app. I hit the following error when build my app: MY_SHA no identity found Command CodeSign failed with a nonzero exit code I have generated my certificate through xcode. I can see the Certificate and the private key in Keychain -> login. But it's not that private key is under the Certificate. They are listed in parallel. The certificate appears in Certificate tab but not in My Certificate Tab. Would that matter? security find-certificate -a -Z | grep -A1 "Apple Development" Gives me the certificate. But security find-identity -v -p codesigning give 0 valid identity found. Could you help me figure out what could be the reason for this? I've been stuck for several days now. Thank you so much!

Hi, I can't switch between Korean and English input with my Mac's physical keyboard in Device Hub. The globe button on the software keyboard switches fine. Simulate Hardware Keyboard is on. I tried Ctrl+Space and Caps Lock. Nothing changes the language in the simulator. Xcode 27.1 beta, Device Hub 27.1 beta. Anyone else seeing this or know a workaround?

Dear Apple Developer Community, Our app monitors a user-defined region by using startMonitoring on an instance of CLLocationManager. While it works as intended on a real device, starting with Xcode 27, this method invocation always results in >locationManager ... monitoringDidFailFor< being called. The error code is always kCLErrorDomain Code=5 but this only occurs within iOS 27 simulators. It works perfectly in iOS 26 simulators. Additionally, CLLocationManager.isMonitoringAvailable(for: CLCircularRegion.self) always returns false on these iOS 27 simulators. This issue blocks parts of our automated system tests. Is it a bug or on purpose? Thank you in advance.

I discovered a disk space issue with Xcode on my 1TB hard disk. Xcode doesn’t delete old or unused Simulators, causing them to mix and consume valuable space. Deleting them from the Window > Devices & Simulators menu didn’t work, so I used Disk Utility to find and delete them. However, they persisted. To regain disk space, I completely removed Xcode and the Developer Folder. After reinstalling Xcode, I regained about 80% of my disk space. Despite unmounting the Simulators, they remained. For those unable or unwilling to do this, the Mac App Store offers DevCleaner, a utility that removes old Xcode Cache and Simulators. Thanks. I hope I've helped someone else. Dan Uff

Hello, It seems that starting Xcode 27, the logs from NetworkExtensions do not show up in the Xcode Console anymore. They still show in Console.app somehow. I have filed a bug report (FB24985332) about it, if you encounter the same issue, please upvote this so that the NetworkExtension team can fix this faster, thanks !

Seems like there is an issue in Xcode 27 beta 4 & 5 where DeviceHub doesn't show iOS 16 devices or simulators. I've checked the filters to ensure I haven't hidden anything and the are listed in the Xcode destination dropdown.

is there a way to change where device hub saves its screenshots? i remember being able to change this in the old Simulator app. i tried holding down the option key while clicking the screenshot button, but that did nothing.

Hello team, We are currently evaluating the Declared Age Range API for supporting age-related regulatory requirements in our application, and we would appreciate some clarification regarding iOS version compatibility. Based on the documentation, we understand that newer age-related capabilities such as isEligibleForAgeFeatures and Regulatory Features are available only on newer iOS versions (for example, iOS 26.4+). We would like to clarify the following: Is the Declared Age Range API itself available only on iOS 26+ devices, or can age range information also be retrieved on earlier iOS versions? For users running iOS versions below 26, will the Declared Age Range API: Return age range information? Return a limited response? Be completely unavailable? Is our understanding correct that applications running on iOS versions earlier than iOS 26 cannot obtain age range information through the Declared Age Range API and therefore cannot determine whether age-related regulatory requirements apply? Are there any recommended fallback approaches for supporting age-verification or age-assurance requirements on devices running iOS versions below 26? Has anyone successfully implemented a solution that provides equivalent age-related signals or regulatory age-verification handling for users on earlier iOS versions? If so, are there any best practices or recommended approaches? Any clarification or guidance would be greatly appreciated. Thanks!