Getting this error trying to submit a build for External Beta App Review: "There was an error processing your request. Please try again later." Build shows "Ready to Submit," internal testing works fine, error happens even before selecting a build. Retried several times over a few days, no change. Checked export compliance, still confirming Test Information is fully filled out. Anyone hit this exact error, especially at the build-selection step?

I am getting this error when trying to run my tests: Library not loaded: @rpath/XCTestCore.framework/XCTestCore Referenced from: <498690CD-C914-3EE9-8EC1-C3BA4EF513CA> /Applications/Xcode-beta.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/lib/libXCTestSwiftSupport.dylib Reason: tried: '/Users/<>/Library/Developer/Xcode/DerivedData/Sonnet-bqruszxvmhdevmbxdbnagkvhywae/Build/Products/Test Project-iphonesimulator/XCTestCore.framework/XCTestCore' (no such file) It is only appearing on the DeviceHub. When I run the tests in my xcode 26, with the old Simulator, they run just fine.

Context is Swift UI iOS app with Xcode 26.6 In my project's Localizable.xcstrings, I have terms flagged as "don't translate". However, when I export the terms with the "Export localizations" menu command, these entry are still listed in the exported XLIFF files (with shouldTranslate:false) Any way to bypass these entries to get accurate clean XLIFF exports ? Thx&rgds, François

Hello! I'm using the new Xcode 26.3 RC and it's new MCP server: However, I am repeatedly prompted to give access to Codex (both the new macOS app and the CLI). And I'm seeing duplicates in the Xcode dropdown: It's pretty blocking in my workflow as I have to keep Allowing over and over again.

Xcode 27 Beta 3 / watchOS 27 Beta 3 - Apple Watch won’t show PIN when pairing in Device Hub (Solved) I ran into an issue where my Apple Watch could no longer pair with Xcode after I manually removed it from Device Hub. Environment Xcode 27 Beta 3 macOS Tahoe Beta iOS 27 Beta 3 watchOS 27 Beta 3 Symptoms iPhone appears in Device Hub and is Connected. Apple Watch does not appear in Device Hub. On Apple Watch: Settings → Privacy & Security → Developer Mode → Devices My Mac appears in the list. Tapping the Mac: Enter watch passcode. Tap Pair. Expected: Xcode should display a 6-digit PIN. Actual: Xcode remains on “Waiting to Pair” forever. No PIN is shown. Additional observations Running: xcrun devicectl list devices Only shows the iPhone. The Apple Watch never appears. Also, while reproducing the issue, coredeviced receives no pairing request at all. So it doesn’t look like the pairing challenge is failing—the pairing request never reaches the Mac. Things I tried (none worked) Restarted Mac, iPhone and Apple Watch. Removed pairing from Device Hub. Removed the Mac from Apple Watch Developer Mode → Devices. Turned Developer Mode off/on. Erased and re-paired the Apple Watch with the iPhone. Re-enabled wireless development. None of these solved the issue. Solution What finally worked was surprisingly simple: Completely power off the iPhone. Keep the Apple Watch and Mac powered on. Pair the Apple Watch from Device Hub again. Immediately after the iPhone was powered off, Xcode displayed the pairing PIN and the pairing completed successfully. After the watch was paired, I powered the iPhone back on and everything continued to work normally. My guess It seems the iPhone (the companion device) may be holding a stale developer pairing state after the watch is manually unpaired from Device Hub. With the iPhone powered off, the watch appears to communicate directly with the Mac, allowing the pairing challenge to be created successfully. Hopefully this helps anyone else who gets stuck at “Waiting to Pair” with no PIN appearing.

The following code crashes as soon as the app launches. struct ContentView: View { var body: some View { List { Rectangle() .fill(.red) .containerRelativeFrame([.horizontal, .vertical]) } .frame(width: 400, height: 800) } } I would expect the code not to crash. Note that using a ScrollView works perfectly fine: struct ContentView: View { var body: some View { ScrollView { Rectangle() .fill(.red) .containerRelativeFrame([.horizontal, .vertical]) } .frame(width: 400, height: 800) } } The documentation clearly stipulates that it should work with a list: A scrollable view like ScrollView or List Using Xcode 26.5 (17F42) and simply created a new macOS project using SwiftUI. Feedback FB23655564

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.

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.

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?