why crash? libsystem_kernel.dylib`mach_msg2_trap: 0x247cb8ccc <+0>: mov x16, #-0x2f ; =-47 0x247cb8cd0 <+4>: svc #0x80 -> 0x247cb8cd4 <+8>: ret

Overview On Xcode 27, when trying to run on a specific destination, the option to “Clear Recent” is missing. This was available in Xcode 26. Manage Devices option exists, but this is to permanently add / remove destinations, this is different from “Clear Recent”. Please bring back “Clear Recent” (from Xcode 26 to Xcode 27) option to Xcode as it is very useful Environment: macOS 26.5.1 (25F80) Xcode 27.0 beta (27A5194q) Feedback FB23055381

Since the introduction of visionOS and releasing a visionOS native app as part of our iOS/iPadOS app, we have had hundreds of warnings show up every time we build for iOS. These warnings show up for every asset (images and colors) that has a visionOS specific variant. The text of the warning itself looks like: The image set "account-cloud" has an unassigned child. If anyone has any way at all to make those warnings go away, I am all ears, though I am fairly confident it is something Apple needs to fix on their end. Fixing this is literally my entire wishlist for Xcode 27. Our feedback number for this from 2023 is: FB13398651

Is there a known workaround (other than forking) for watchOS builds in Xcode 27 that depend on packages without a declared watchOS 9.0 floor? I depend on several Apple SPM packages with no minimum deployment target, such as https://github.com/apple/swift-algorithms. My project's minimum is 26.0. Xcode 27 will not build watchOS targets with these packages because watchOS 8.0 is below its range of supported targets. /.../SourcePackages/checkouts/swift-algorithms/Package.swift The watchOS Simulator deployment target 'WATCHOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 27.0.x.

Overview When a project contains SwiftData and the Preview uses a in memory database, SwiftUI preview doesn't show the data Have a look at the ContentView preview Environment Xcode 27.0 beta (27A5194q) 26.5.1 (25F80) Feedback FB23041713 Please can you have a look at the feedback, it also has a sample project and screenshot

Glancing through this forum, this seems to be a recurrent pattern sigh. Symbols for watchOS 26.5 (23T570): Failed with HTTP status 403: Forbidden. Nibbling them over wireless doesn't work either, since after 1h or so, the connection just fails and never resumes. watchOS development platform is the worst experience since I started developing on C64 in 1983.

I was playing around with the brand-new reorderable API and couldn't get it to work within previews. Is there a specific way to get previews to work with reorderable, or do I need to compile every time? I was also curious if there will be an addition to the Array generic struct, as it seems like the solution there currently is is just an extension, although the way it's being promoted makes it seem like it is built into the type.

Hey, anyone figured out how Device Hub will work? I have a Mac OS 26.5.1 (25F80) version. It's not working with my device configurations. I have downloaded Xcode components of Xcode 27 and iOS 27 simulators, but device help seems to be not working. If anyone has a similar problem or has a fix, kindly let me know.

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

I have raised Feedback FB23036084 Just using it on an extremely small app that display six SwiftUI charts. I was just scrolling on a ScrollView of the charts. Th feedback has a link to the app on GitHub, the content of the generate report details and also the output of running xcrun simctl diagnose

When compiling the codebase with Xcode 27 and running it on a simulator or real device (with iOS 27 or iOS 26.x) the app keeps crashing in certain situations with the error "Thread 1: EXC_BAD_ACCESS (code=257, address=0x80000001097a409e)". The exact same codebase is working just fine on Xcode 26.5. I’ve tested changing the Xcode 27 toolchain to a custom one (6.3.2) but it still crashes. I’ve also tried to usual steps to delete the derived data folder and clear the cache. Nothing worked. Here's the Feedback ID I've opened: FB23035297. Is this happening to anyone else? Any idea?

Every time I try to login to my Anthropic account after pressing 'Sign In...', nothing appears to happen and cannot move past the Sign In... dialogue. The sign in screen appears and I can press 'Authorize' but nothing changes. Any tips on how to login to use Anthropic over OpenAI?

Summary: After upgrading to Xcode 26.4, app-hosted XCTest execution on physical devices running iOS 16 fails at test-planning time with "Logic Testing Unavailable." The same project and same device work under Xcode 26.2. The failure reproduces with a standalone minimal Xcode project, which suggests this is an Xcode regression rather than a project-configuration issue. Environment: Xcode: 26.4 (17E192) macOS: Tahoe 26.4 Failing device: iPhone 11 (iPhone12,1), iOS 16.0.3 Working comparisons: Xcode 26.2 + same iPhone 11 (iOS 16.0.3): works Xcode 26.4 + iPad Pro 11-inch (4th generation) on iOS 26.3: works Regression: Yes. Works on Xcode 26.2. Fails on Xcode 26.4. Same project, same signing setup, same physical iOS 16 device. Minimal reproduction: A minimal sample project with: one iOS app target one app-hosted unit-test target one UI-test target (for comparison; not required to reproduce) Steps for the unit-test repro on a physical device running iOS 16: Build for testing: xcodebuild -project TestProject.xcodeproj \ -scheme TestProject-UnitTests \ -sdk iphoneos \ -destination 'platform=iOS,id=<DEVICE_UDID>' \ -derivedDataPath DerivedData-Device-Unit \ -resultBundlePath Results-Device-Unit-Build.xcresult \ DEVELOPMENT_TEAM=<TEAM_ID> \ CODE_SIGN_STYLE=Automatic \ build-for-testing Run tests without building: xcodebuild -project TestProject.xcodeproj \ -scheme TestProject-UnitTests \ -sdk iphoneos \ -destination 'platform=iOS,id=<DEVICE_UDID>' \ -derivedDataPath DerivedData-Device-Unit \ -resultBundlePath Results-Device-Unit-Test.xcresult \ DEVELOPMENT_TEAM=<TEAM_ID> \ CODE_SIGN_STYLE=Automatic \ test-without-building Note: xcodebuild test (combined build and test) also fails with the same error. Expected result: The hosted unit tests run successfully on the connected physical device, as they do under Xcode 26.2. Actual result: Step 1 (build-for-testing) succeeds. Step 2 (test-without-building) fails immediately (within ~1 second) with: 2026-03-26 11:23:28.683 xcodebuild[51930:731004] DVTDeviceOperation: Encountered a build number "" that is incompatible with DVTBuildVersion. 2026-03-26 11:23:28.725 xcodebuild[51930:730966] [MT] DVTDeviceOperation: Encountered a build number "" that is incompatible with DVTBuildVersion. 2026-03-26 11:23:29.239 xcodebuild[51930:730966] Writing error result bundle to /var/folders/jl/knmkq18x4cg_3w087zgpfldm0000gn/T/ResultBundle_2026-26-03_11-23-0029.xcresult xcodebuild: error: Failed to build project TestProject with scheme TestProject-UnitTests.: Cannot test target “redacted” on “redacted”: Logic Testing Unavailable Logic Testing on iOS devices is not supported. You can run logic tests on the Simulator. Why this looks like an Xcode regression: The same project and same physical iOS 16.0.3 device work under Xcode 26.2. Under Xcode 26.4, build-for-testing still succeeds, so signing, provisioning, and bundle construction appear valid. The failure happens only when Xcode plans or launches the on-device test run. Before the failure, Xcode 26.4 logs: DVTDeviceOperation: Encountered a build number "" that is incompatible with DVTBuildVersion. A newer physical device running iOS 26.3 works under Xcode 26.4 without this warning. The issue also reproduces with a minimal standalone Xcode project, which makes a project-specific configuration problem unlikely. The Xcode-generated .xctestrun files for the passing Xcode 26.2 case and failing Xcode 26.4 case are structurally equivalent, making an .xctestrun format difference unlikely to be the cause.

Is it possible for Xcode to show the relative number after the code is folded? Instead of showing the relative line number before code is folded. For example, in the case below, for the line with "}", 2 should be displayed instead of 45. It really bothers me when jumping to the target line in vim mode. The number I key in doesn't match the number show in the left side of editor. My point is, at least make the number used in jumping command in vim mode matches the number show in the left side of the editor.

Hi, Xcode 27 markdown rendering look fantastic, a big thanks to everyone who contributed to it. Truly such a delight seeing rendered beautifully!! I didn't see it explained in any of the Xcode sessions, if there are WWDC sessions or documentation on this please let me know. Questions Tables get rendered really well, how can I add or remove columns in a table? For links I noticed that I needed to add the link first and then title for the link later, or are there alternate ways?

Hi everyone, I wanted to share that I had issues downloading the iOS 27 beta due to "Fetching Download Information" and wanted to share that running this worked for me: xcodebuild -downloadPlatform iOS -architectureVariant arm64

Hi, On Xcode 27, whenever I create a new Project and select App, an untitled project is created. What is good: When I go on to save the project, the project name uses it to update target name which is nice. Problem: Every time it uses a placeholder team ID, I have to go and manually update the bundle ID and team. This could also lead to unnecessary provisioning profiles created with placeholder IDs. Proposal FB23033844 Xcode to use the last used Bundle ID and Team. This will be similar to how things were in Xcode 26

Hi, On Xcode 27, Device Hub, how to view the simulator with Point Accurate and Pixel Accurate window sizes? These are existing options on Xcode 26 Simulator, so would be nice to have them in Xcode 27 Device Hub. This would be needed sometimes to quickly measure things using a on screen ruler. Feedback FB23033231 If there is no option currently can you please provide options to provide to view Point Accurate and Pixel Accurate window sizes

I downloaded Xcode 27 beta and it presents a license agreement, but tapping the Agree button is not working. It will ask for my computer password but after that, the window is not dismissed. Repeated taps on the Agree button do nothing. I've even tried sudo xcodebuild -license to no avail.

Environment Xcode 27.0 (Build 27A5194q) macOS 27.0 (Build 26A5353q), Apple Silicon Command Line Tools 27.0 Summary The iOS 27.0 (24A5355p) and watchOS 27.0 (24R5289n) Simulator runtimes download and mount successfully, but never register as usable. Both fail in exactly the same way. Every older runtime (e.g. iOS 26.2 / 23C54) works fine. What I see xcrun simctl list runtimes does NOT list iOS 27 or watchOS 27. They appear only under xcrun simctl runtime list (disk images), as: iOS 27.0 (24A5355p) State: Ready Image Kind: Patchable Cryptex Disk Image Signature State: Unknown Mount Path: /private/var/run/com.apple.security.cryptexd/mnt/... They never get promoted to /Library/Developer/CoreSimulator/Volumes/ the way working runtimes do. Where it actually breaks simdiskimaged finds and mounts the runtime with no error: "Found runtime bundle on disk image at: .../iOS 27.0.simruntime" "Got supported architectures back ... arm64" The runtime IS present in /Library/Developer/CoreSimulator/Images/images.plist, and its cryptex personalization manifest exists in /Library/Developer/CoreSimulator/Cryptex/Personalization/. BUT iOS 27 (24A5355p) and watchOS 27 (24R5289n) are the ONLY two images in the index whose signatureState is not verified. Every other runtime shows signatureState => verified. CoreSimulatorService therefore never registers them. So the cryptex mounts and the personalization ticket is present, but signature verification against that manifest never completes for these two new runtimes. Things I have already tried (no change) Deleted and re-downloaded the runtime via xcodebuild -downloadPlatform iOS (fresh image, identical result) Restarted CoreSimulatorService; ran sudo xcodebuild -runFirstLaunch Full reboot (cryptex re-mounts at boot but is still never verified/promoted) Deleted images.plist and let it rebuild Verified: system clock correct; gs.apple.com and ppq.apple.com reachable on 443; ~85 GB free disk; iphoneos27.0 SDK build (24A5355p) matches the downloaded runtime; simctl runtime match list shows 24A5355p as the chosen/default runtime. The standalone Simulator runtime .dmg for iOS 27 is not yet on Developer Downloads, so xcrun simctl runtime add isn't an option. Questions Is anyone else seeing iOS 27 / watchOS 27 runtimes stuck at Signature State: Unknown / signatureState != verified on this beta? Is there a way to force re-verification of an already-downloaded cryptex runtime without a standalone .dmg? Is this a known issue in the current beta? (FB filed.) Thanks!