It doesn't seem to be able to launch. It says "This version of Xcode is not compatible with this version of macOS." So, does that mean that users who have updated to macOS 27 cannot submit apps to the App Store? Do I have to wait until Xcode 27 starts accepting submissions? Environment: macOS 27.0 / Xcode 26.6 RC

Anyone else seeing a lot more "Class X is implemented in both ..." warnings on Xcode 27 than on Xcode 26? Same source, same flags, the count goes from a handful to a couple thousand, and some now correlate with real crashes (cast failures, missing protocol conformances) instead of the usual harmless first-wins behavior. Is this a known change in Swift 6.4 / Xcode 27? Is there a new flag I should be passing? Any suggestions welcome.

My Mac Catalyst app (distributed via TestFlight) crashes instantly at launch — before main() — on macOS 26.5.1 (25F80) when archived with Xcode 27 beta 3. The same code archived with Xcode 26.5 (GA) launches fine. Crash excerpt: Termination Reason: Namespace DYLD, Code 4, Symbol missing Symbol not found: _UIFontTextStyleBody Referenced from: <...> /Applications/Paku.app/Contents/MacOS/Paku Expected in: <...> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit (terminated at launch; ignore backtrace) What appears to be happening The symbol comes from completely ordinary UIKit code — e.g. UIFont.preferredFont(forTextStyle: .body). When linking with the Xcode 27 beta 3 SDK, the two-level namespace bind for _UIFontTextStyleBody in my binary points at AppKit, i.e. the beta SDK's AppKit.tbd declares (re-exports) the UIKit text-style constants for Catalyst. But the shipping OS doesn't provide that: on macOS 26.5.1, _UIFontTextStyleBody is absent from both the installed AppKit binary (checked with dyld_info -exports /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit) and the Xcode 26.5 GA SDK's AppKit.tbd. So any binary linked against the beta SDK hard-binds the symbol to AppKit and then fatally fails to bind on current GA macOS — a 100%-reproducible launch crash for every user not on the macOS 27 beta. Steps to reproduce Mac Catalyst target that uses any UIFont.TextStyle constant (e.g. .preferredFont(forTextStyle: .body)). Archive with Xcode 27 beta 3 and distribute via TestFlight. Launch on macOS 26.5.1 → immediate dyld abort with the report above. Questions Is this a known issue with the macOS 27 beta SDK's AppKit re-export list? It looks like these UIKit constants are being moved/re-exported through AppKit in the 27 cycle, but without availability/weak-linking info that would let binaries back-deploy to macOS 26. Is the intended behavior that Catalyst apps built with the 27 beta SDK simply can't run on macOS 26? If so, should App Store Connect / TestFlight have rejected or flagged the upload?

It is not possible to log into my Claude account in Xcode 27 beta 1 for the coding intelligence chat. When I click "Sign In," the browser opens, I authorize, the browser closes, and that's it. Nothing happens. Xcode does not recognize the login. I'm on MacOS 26.4.1 (25E253) and using Xcode 27.0 beta (27A5194q)

When trying to log into the Codex Plugin from Xcode, on the auth.openai.com site I can not progress. No option will progress from that page. Not: Continue with eMail Continue with Microsoft Continue with Apple Continue with Google Continue with phone number Is this a Safari (27.0, 22625.1.22.11.4) issue, or an OpenAI issue?

I am testing an existing iOS app with Xcode 27 beta 3. The build succeeds, but I am seeing a new linker warning from Swift Package product targets. ld: warning: address=0xF496F points before section(28) start and the target atom is ambiguous Environment: Xcode 27.0 beta 3 Build version: 27A5218g Platform: iOS Simulator Configuration: Debug Project type: iOS app with Swift Package dependencies, also embedding a watchOS app Build command: DEVELOPER_DIR=/Applications/Xcode-beta.app/Contents/Developer \ xcodebuild -project MyWeight/MyWeight.xcodeproj \ -scheme MyWeight \ -configuration Debug \ -destination "generic/platform=iOS Simulator" \ build The build succeeds: ** BUILD SUCCEEDED ** Warnings: MyWeight/MyWeightKit/Package.swift: MyWeightKit-watchOS-product: ld: warning: address=0xF493F points before section(28) start and the target atom is ambiguous MyWeight/MyWeightKit/Package.swift: MyWeightKit-iOS-product: ld: warning: address=0xF496F points before section(28) start and the target atom is ambiguous Both warnings appear during the link step for Swift Package product framework targets. Is this a known issue in Xcode 27 beta 3? Does it indicate a real issue in the produced simulator binary, or is it likely a linker/debug-info diagnostic?

Xcode tells me Previewing in executable targets now requires a new build layout for unoptimized builds. Either set ENABLE_DEBUG_DYLIB to YES for this target, or break out your preview code into a separate framework with its own scheme. How do enable that in Package.swift. swiftSettings don't work (.define and unsafeFlags with -D ...). Creating a library product that the executable then depends on doesn't help either. I have two targets, one is an executable target. The #Preview macro is in the non-executable target.

Problem statement: The Claude Agent component for currently installed by Xcode 26.6 or 27.0 Beta 3 is 2.1.175 which doesn't appear to support the Claude Apps Gateway (see code.claude.com/docs/en/claude-apps-gateway) Versions from 2.1.198 are required. Net effect is that when your organisation switches to the app gateway Xcode's Claude integration no longer works due to the lack of support in the installed component. Questions: Given the component is a signed binary is there any other way to use the locally installed Claude cli (current version 2.1.202)? When is an update expected? Is there any consideration for the rapid evolution of these agents to prevent blocking issues like this?

Hello, I am wondering if DeviceHub will include support at some point for Simulator Device Sets (usually created via simctl)? While I can still start Simulators from a DeviceSet via simctl still with Xcode 27, it doesn’t launch in the DeviceHub, I simply see the headless Simulator running (which I can see this in ActivityMonitor). So it looks like any Simulators not created with DeviceHub won’t run/render in DeviceHub? Usually with the Simulator.app I can run: $ open -a Simulator.app --args -DeviceSetPath /Volumes/Simulators/26.1.0/CustomDeviceSet and then the Simulator app opens with the Device Set list and I then can run simulators I pre-prepared from the Simulator.app. If I try the same command with DeivceHub: $ open -a DeviceHub.app --args -DeviceSetPath /Volumes/Simulators/26.1.0/CustomDeviceSet While It does start the DeviceHub app it doesn't do anything with the DeviceSetPath argument. I would expect to see the devices from the device set directory to show up in the DeviceHub UI list if it were honored. Thanks!

I'm experiencing a reproducible issue that completely blocks Xcode on an Apple Silicon Mac. Environment • MacBook Air (M4) • macOS 26.5.2 (25F84) • Xcode 26.6 (17F113) • Also reproduced with Xcode 26.5 (17F42) Issue Xcode terminates immediately before the main window appears. Instruments also terminates immediately. The command: xcodebuild -version works normally. However, any command that requires SDK initialization immediately terminates, for example: xcodebuild -showsdks The process is killed instantly. Crash reports consistently show: SIGKILL (Code Signature Invalid) Termination Reason: Namespace CODESIGNING, Code 2, Invalid Page The crash occurs during dyld page authentication: dyld4::fixupPageAuth64() What I have already tried • Reinstalled Xcode • Reinstalled macOS • Reinstalled Command Line Tools • Reinstalled Rosetta • Tested in Safe Mode • Tested with a newly created macOS user • Removed caches and DerivedData • Verified Xcode signatures The behavior is identical in every case. Interestingly, xcodebuild -version succeeds, but every SDK-related command is killed immediately, suggesting the failure occurs during SDK/framework initialization rather than Xcode startup itself. I have already submitted: Feedback Assistant: FB23586800 DTS Case: 20879405 Has anyone else seen the same issue on Apple Silicon (especially M4)? Any known workaround or confirmation that this may be a macOS 26.5.x / Xcode 26.5–26.6 regression would be greatly appreciated.

Hullo, I wanted to turn a class in a struct and move intelligence in a protocol extension, but when I try to call inits in the extension I get 'self' used before 'self.init' call or assignment to 'self' How do I call self.init or assign to self before updating the values? Of course init does no accept mutating.

Tahoe 26.5.2 Debugging a macOS desktop C++ application on a Mac Mini M1 2020. The application runs under Rosetta2. Once the debugger has hit a breakpoint: Step Over freezes up every single time. Step Into usually works the first two or three times, then freezes. Sometimes Xcode eventually shows an error message saying that it has killed the lldb process. The debug output shows a warning "Unable to obtain a task name port right for pid 428: (os/kern) failure (0x5)". PID 428 is not listed in Activity Monitor. The only way out of this situation appears to be to kill the application. The application runs as expected when there are no breakpoints. I am occasionally getting the error "Debug session ended with code -1: lost connection" I have sent several reports to Apple via the Feedback Assistant.

Does the annually updated requirement that apps uploaded to App Store Connect must be built with the latest SDK (i.e. Xcode version) only apply to the main executable or to embedded binaries (e.g. frameworks) also?

Neither in Xcode 27 beta 1 or 2 we have been able to use simulators for the intel x86 architecture. Is there any way to get them?

I can sign into AppStore Connect from Chrome, not sometimes in Safari. I get an error dialog that says The operation couldn’t be completed. Unable to log in with account ''. An unexpected failure occurred while logging in (Underlying error code -1001). Apple servers all seem up, so it's just me apparently

Summary: Xcode 26.5 on macOS 26.5.1 (25F80) does not record recently opened projects. The Welcome window permanently shows "No Recent Projects" regardless of how many projects are opened. Open recent projects menu item no longer exists in new versions. Only on welcome. Steps to Reproduce: Launch Xcode 26.6 on macOS 26.5.1 Open an existing .xcodeproj or .xcworkspace file by double-clicking in Finder Close the project Open the Welcome window (Shift+Cmd+1 or via Window menu) Expected Result: The recently opened project appears in the Recent Projects list. Actual Result: The Welcome window shows "No Recent Projects". The keys IDERecentEditorDocuments and IDERecentWorkspaceDocuments in com.apple.dt.Xcode.plist remain empty or absent after opening projects. Diagnostic Steps Already Taken: Confirmed com.apple.quarantine xattr removed from Xcode plist Confirmed Full Disk Access granted to Xcode Confirmed plist is writable (no uchg flag, correct ownership) Deleted com.apple.dt.Xcode.plist entirely and allowed Xcode to recreate it — issue persists Confirmed ApplePersistenceIgnoreState is not set globally or per-app Confirmed NSGlobalDomain ApplePersistenceIgnoreState is not set Projects are opened by double-clicking physical .xcodeproj files in Finder (not aliases or symlinks) Environment: Xcode Version: 26.5 macOS Version: 26.5.1 (Build 25F80) Hardware: MacBook Pro

Environment • macOS 27 beta 2 • Xcode 27 beta • Apple Silicon Mac Summary After upgrading to macOS 27 beta 2 and Xcode 27 beta, an old iOS 18.5 simulator runtime remains registered internally but cannot be removed. There appears to be an inconsistency between different CoreSimulator commands. Observed Behavior xcrun simctl runtime list only reports the current runtime: == Disk Images == -- iOS -- iOS 26.1 (23B86) - 0753590B-CF3F-4944-899E-4F70698DB87C (Ready) Total Disk Images: 1 (7.8G) However, xcrun simctl list runtimes -j still reports an additional runtime: identifier: com.apple.CoreSimulator.SimRuntime.iOS-18-5 SimulatorVersion: 18.5 Build: 22F77 bundlePath: /Library/Developer/CoreSimulator/Volumes/iOS_22F77/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 18.5.simruntime runtimeRoot: /Library/Developer/CoreSimulator/Volumes/iOS_22F77/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 18.5.simruntime/Contents/Resources/RuntimeRoot The runtime is reported as: "isAvailable": true The runtime no longer appears anywhere in Xcode. Attempting to remove it using the documented command fails: xcrun simctl runtime delete 22F77 Output: No runtime disk images or bundles found matching '22F77'. No matching images found to delete Using the runtime identifier also fails. The corresponding MobileAsset still exists: /System/Library/AssetsV2/com_apple_MobileAsset_iOSSimulatorRuntime/ It contains: c0d3fd05106683ba0b3680d4d1afec65f098d700.asset Its Info.plist contains: SimulatorVersion = 18.5 Build = 22F77 Another asset exists for the current runtime: SimulatorVersion = 26.1 Build = 23B86 The directory /Library/Developer/CoreSimulator/Volumes/iOS_22F77 exists as an empty directory. It appears to become active only when CoreSimulator queries the runtime. The runtime asset is no longer referenced by /System/Library/AssetsV2/com_apple_MobileAsset_iOSSimulatorRuntime/com_apple_MobileAsset_iOSSimulatorRuntime.xml Expected Result After upgrading Xcode/macOS: • old runtimes should either be removable through xcrun simctl runtime delete or • they should no longer remain registered if Xcode has already removed them. Actual Result Different CoreSimulator commands report different runtime states. simctl runtime list only reports iOS 26.1. simctl list runtimes -j still reports iOS 18.5 as available. The old runtime cannot be deleted using the official command. The MobileAsset remains on disk and occupies storage, but there appears to be no supported method to remove it. Notes This looks like CoreSimulator's runtime registry and the runtime deletion mechanism have become inconsistent after upgrading to macOS 27 beta 2 and Xcode 27 beta.

If I use the Claude Code agent within Xcode 27 beta 2, it defaults to Opus 4.8, but that burns through tokens too quickly so I'd like to switch it to Opus 4.7 or Sonnet, but there's no way to change that anywhere in Xcode that I can see? Also, if I use Chat, rather than the agent, then Xcode lets you select models, however for Claude it only offers Sonnet 4.5. Why? Why not 4.6 at least? Where are these limitations coming from? It's not from Claude so it must be Xcode Why are these limitations present?

I have had two kernel panics while building in Xcode, or running extremely simple interactions with a single Swift Double in playgrounds in Xcode. Has any one else seen this while building in Xcode? For whatever it is worth, Gemini states it is not a hardware problem, but something to do with "aggressive memory security protocols to support modern unified architectures and stricter platform boundaries", and that this is a an assertion error in Darwin. Given that this happened twice over the last three days, I'm a little concerned. Thanks in advance Hardware: M5 Max with 129 GB, and ~720 GB of storage First incident configuration (while building in Xcode): Xcode: 26.5 MacOS: 26.5.1 Second incident configuration (while running a playground in Xcode): Xcode: Version 26.6 (17F113) MacOS: 26.5.2 Second incident (looks like an underflow in Core 0): "bug_type":"210", ..., "os_version":"macOS 26.5.2 (25F84)", "roots_installed":0, ... "product" : "Mac17,6", "kernel" : "Darwin Kernel Version 25.5.0: ... "socRevision" : "11", "panicString" : "panic(cpu 0 caller 0xfffffe0051dde6fc): vm_object_activity_end(0xf3fffe14df4d2e00): underflow ... @vm_object_internal.h:700 Debugger message: panic Memory ID: 0xff OS release type: User OS version: 25F84 Kernel version: Darwin Kernel Version 25.5.0: ... Exclaves boot status: BOOTED_EXCLAVEKIT Fileset Kernelcache UUID: 5311854233360499876BA3DD5FD3C710 Kernel UUID: BEA0911B-FF13-3AE9-816D-8DEF9DD951DF ... roots installed: 0 Paniclog version: 15 CORE 0 is the one that panicked. Check the full backtrace for details. CORE 1: PC=0xfffffe0051d5e7e0, LR=0xfffffe0051e5dc3c, FP=0xfffffecffaf33af0 CORE 2: PC=0xfffffe0051d14b6c, LR=0xfffffe0051d14b6c, FP=0xfffffec34a8f7ee0 ...

Please help me understand how build SDKs work in Xcode 27. Let's say I have an older app that uses UIDesignRequiresCompatibility. When I a) select an iOS 26 Simulator in Xcode 27 and press "play" (build an run), the app shows up in design compatibility mode. b) select an iOS 27 Simulator in Xcode 27 and press "play" (build an run), the app shows up ignoring design compatibility mode. My questions: Does that mean a) is using iOS 26 as build SDK and b) is using iOS 27 as build SDK? What would happen if running an app built using iOS 26 build SDK on iOS 27? What would happen if running an app built using iOS 27 build SDK on iOS 26? How can 2. and 3. be done with the simulator? When I submit to App Store Connect, which build SDK is used?