On https://developer.apple.com/documentation/AppIntentsTesting/testing-your-app-intents-code Apple showcases the following example using AppIntentsTesting to query entities indexed in spotlight. For me, calling .spotlightQuery on any entity definition causes a crash. func testAllEventsIndexed() async throws { let eventDef = definitions.entities["EventEntity"] let allIndexed = try await eventDef .spotlightQuery(nil) XCTAssertGreaterThanOrEqual(allIndexed.count, 3) } Crash: expression unexpectedly raised an error: Failed to obtain the result of the distributed invocation after it was executed. Remote threw executionPermissionDenied(requestBundleID: Is anyone else seeing this crash, or is it just me? Thanks!

On iOS 26, a Simulator screen recording shows the bottom corners of content go from rounded to square during normal push and sheet transitions. This happens on the simulator, but I don't see this on a real iPhone. Steps to reproduce: Create a new SwiftUI app and use the attached content view. Run on an iOS 26 Simulator. Start a Simulator screen recording. Tap a row to push, and tap "Filter" to present the sheet. Stop the recording and play it back frame by frame. Run the same app on a real iPhone and watch the transitions live. Question: Is this a new feature or a simulator bug? Configuration: Xcode 26.4.1 iOS 26 Simulator — iPhone 17 Pro Real device: iPhone 16 Pro Max Attachments: ContentView

With the latest Xcode 26.4 my project fails to compile due to a "compiler unable to type-check in reasonable time" error with a library I've been using for years and has not changed. The library is https://github.com/ngageoint/mgrs-ios and is specifically around this line https://github.com/ngageoint/mgrs-ios/blob/master/mgrs-ios/utm/UTM.swift#L96. Since this isn't my library I can't change it, but again we've been using this library for years now without issue - it was only when Xcode updated this morning that our compilation workflow broke. (Compilation machine is an M3 Pro with 18GB of RAM, so I don't think that's the problem here)

I submitted this to Feedback Assistant as FB22331090 and wanted to share a minimal reproducible example here in case others are seeing the same issue. Environment: Xcode 26.4 or Xcode 26.3 Apple Swift version 6.3 (swiftlang-6.3.0.123.5 clang-2100.0.123.102) Effective Swift language version 5.10 Deployment target: iOS 17.0 The sample app builds successfully for normal development use, but archive fails. The crash happens during optimization in EarlyPerfInliner while compiling the synthesized deinit of a nested generic Coordinator class. The coordinator stores a UIHostingController. Minimal reproducer: import SwiftUI struct ReproView<Content: View>: UIViewRepresentable { let content: Content func makeUIView(context: Context) -> UIView { context.coordinator.host.view } func updateUIView(_ uiView: UIView, context: Context) { context.coordinator.host.rootView = content } func makeCoordinator() -> Coordinator { Coordinator(content: content) } final class Coordinator { let host: UIHostingController<Content> init(content: Content) { host = UIHostingController(rootView: content) } } } Used from ContentView like this: ReproView(content: Text("Hello")) Steps: Create a new SwiftUI iOS app. Set deployment target to iOS 17.0. Add the code above. Archive. Expected result: Archive succeeds, or the compiler emits a normal diagnostic. Actual result: The Swift compiler crashes and prints: "Please submit a bug report" "While running pass ... SILFunctionTransform 'EarlyPerfInliner'" The crash occurs while compiling the synthesized deinit for ReproView.Coordinator. Relevant log lines from my archive log: line 209: Please submit a bug report line 215: While running pass ... EarlyPerfInliner line 216: for 'deinit' at ReproView.swift:19:17 One more detail: The same sample archived successfully when the deployment target was higher. Lowering the deployment target to iOS 17.0 made the archive crash reproducible. This may be related to another forum thread about release-only compiler crashes, but the reproducer here is different: this one uses a generic UIViewRepresentable with a nested Coordinator storing UIHostingController.

I'm trying to test my StoreKit package using local "Consumable.storekit" configuration added to test target as a .copy() resource. I receive various errors. On purchase attempts I receive StoreKitError.unknown. In the console I see this diagnostic messages: [SKTestSession] Error saving configuration file: Error Domain=SKInternalErrorDomain Code=3 "(null)" [SKTestSession] Error setting value to 1 for identifier 2 for com.apple.dt.xctest.tool: Error Domain=SKInternalErrorDomain Code=3 "(null)" I these last two cases product loading failed. It feels like session require mutable .storekit file? Also, some people mention that Host Application must be selected, but it's related to Xcode projects. What is the correct way to test StoreKit within a Swift Package?

▿ DeviceKit.(unknown context at $1058036ec).ErrorDescription title: "The developer disk image could not be mounted on this device." errorClass: "CoreDeviceError" errorCode: "12040" DeviceIdentifier: 0DFB4363-6028-52E1-8C03-17D79DAxxxx #0 super: NSMutableString super: NSString super: NSObject ▿ underlyingErrors: 1 element ▿ DeviceKit.(unknown context at $1058036ec).ErrorDescription - title: "Personalization of the Cryptex-based developer disk image failed." - errorClass: "NSError" - errorCode: "12051" - DDIBuildUpdate: 27A5194q (developerTools) #1 - super: NSMutableString - super: NSString - super: NSObject - DDIPath: /Library/Developer/DeveloperDiskImages/iOS_DDI #2 - super: NSMutableString - super: NSString - super: NSObject - DDIPlatform: iOS #3 - super: NSString - super: NSObject - DDIVariant: external #4 - super: NSString - super: NSObject - DeviceBoardID: 4 #5 - super: NSNumber - super: NSValue - super: NSObject - DeviceChipID: 33040 #6 - super: NSNumber - super: NSValue - super: NSObject - DeviceFusing: prod #7 - super: NSString - super: NSObject - DeviceIdentifier: 0DFB4363-6028-52E1-8C03-17D79DA5E159 #8 - super: NSMutableString - super: NSString - super: NSObject - NSLocalizedFailureReason: An error occurred while personalizing the developer disk image. #9 - super: NSMutableString - super: NSString - super: NSObject - NSLocalizedRecoverySuggestion: Ensure the device is running a supported version of the operating system. If the issue persists, gather a diagnostic report by running 'devicectl diagnose' from Terminal and file a bug report at https://bugreport.apple.com. #10 - super: NSMutableString - super: NSString - super: NSObject - NSURL: file:///Library/Developer/DeveloperDiskImages/iOS_DDI/ #11 - super: NSObject - UseCredentials: 0 #12 - super: NSNumber - super: NSValue - super: NSObject ▿ underlyingErrors: 1 element ▿ DeviceKit.(unknown context at $1058036ec).ErrorDescription - title: "The operation couldn’t be completed. (CryptexKitHost.TatsuError error 4.)" - errorClass: "NSError" - errorCode: "4"

When building our project for Mac Catalyst with Xcode 26.2, we get this warning almost a hundred times, once for every object file: directory not found for option '-L/var/run/com.apple.security.cryptexd/mnt/com.apple.MobileAsset.MetalToolchain-v17.3.48.0.UZtKea/Metal.xctoolchain/usr/lib/swift/maccatalyst' Somehow, every Link <FileName>.o build step got the following parameter, regardless if the target contained Metal files or not: -L/var/run/com.apple.security.cryptexd/mnt/com.apple.MobileAsset.MetalToolchain-v17.3.48.0.UZtKea/Metal.xctoolchain/usr/lib/swift/maccatalyst The toolchain is mounted at this point, but the directory usr/lib/swift/maccatalyst doesn't exist. When building the project for iOS, the option doesn't exist and the warning is not shown. We already check the build settings, but we couldn't find a reason why the linker is trying to link against the toolchain here. Even for targets that do contain Metal files, we get the following linker warning: search path '/var/run/com.apple.security.cryptexd/mnt/com.apple.MobileAsset.MetalToolchain-v17.3.48.0.UZtKea/Metal.xctoolchain/usr/lib/swift/maccatalyst' not found Is this a known issue? Is there a way to get rid of these warnings?

Was working before, no longer working this week. Trying to sign in to my Claude Pro account via Xcode Intelligence. Goes to browser, I login, and accept authorization in Claude then redirect back to Xcode is reject. Everytime, multiple browsers, and even trying the add "/" that others have noted for other cases.

This button is enabled for new projects I've created in Xcode 27, but I haven't been able to see it in a not grayed-out state with any of my existing projects created with prior versions of Xcode.

Hi, whenever I build my app to a simulator it launched device hub but then nothing, makes my Mac extremely hot and cause fans to engage all for nothing. Is it because I'm still on MacOS 26.5.1? Just seems like device hub is broken for me I can only launch testing on physical devices.

I am testing the Xcode 27 Beta and new Device Hub app on my MacBook Pro (M5) with macOS Tahoe 26.5.1, but every time I try to create a new Simulator, the process begins to run, but then fails after this message appears that says “Family quit unexpectedly." I looked over the details of the issue, and it is indeed directly linked to the failing simulator creation. Since this issue makes it impossible to Build and Run any app in the new Xcode 27 beta, it makes it almost completely useless for me. I have already downloaded the iOS 27 simulator, but it fails to boot in the Device Hub.

I can't figure out what I'm doing wrong, maybe it's just "in development." I am running on Tahoe, but running the 27 beta. I created a simulator and asked it to run and it did, but claude had to jump through hoops to get it to actually display. The hub only shows my appleTV device that I test on. Simulators do not show at all. Even when running. Hints on what I am doing wrong? Is it because I'm on Tahoe? Known bug? Dumb user?

It appears that recording video of a device in Device Hub does not record the associated audio of the device. Are there any plans to do this? (Or a workaround that's easier than rerouting the audio output to an audio editor app and recording it separately?) It would be incredibly useful for making app demonstrations and tutorials.

Has anyone managed to get Copilot working using the new ACP integration in Xcode 26.6 and Xcode 27 beta? I have tried setting it up using the path to the copilot binary as instructed and the flags --acp --stdio but Xcode just displays a "Your request couldn't be completed" error: JSON-RPC global stream failed: The operation couldn’t be completed. (IDEIntelligenceProtocol.JSONRPCElement.Error error 1.) I am running the latest version of copilot cli and it works in many other IDEs.

Mac Pro 2019, Tahoe 26.3, Xcode 26.2 Mac Mini 2023 M2, Tahoe 26.3, Xcode 26.2 On Mac Pro 2019 the app is only Intel while on Mac Mini 2023 M2 it is ARM64 only. Both have Standard Architectures (Apple Silicon, Intel). Both have Build Active Architecture Only is set to No (Debug + Release). Happen for default new projet macOS -> App and Obj-C, Xib. No change to defaults setting except uncheck "Automaticaly manage signing" and "Signing Certificate" set to "Sign to Run Locally" HOWEVER On Mac Pro 2019, BigSur 11.7.10, Xcode 14.10 the application is build Universal ! Why cannot build universal with Tahoe 26.3, Xcode 26.2 ? Can I submit a Mac applcation to App Store Connect with BigSur 11.7.10, Xcode 14.10 ? What are the minimal version of Mac Os and Xcode to submit a Mac applcation to App Store Connect ?

I'm trying to let a few teammates build and run my app on their own devices, and I'd like to understand the correct approach for our situation. Setup We are a small team. Each of us uses a free personal Apple Developer team (individual Apple IDs, no paid membership yet). The app (an iOS app with a Watch app and a WidgetKit extension) uses App Groups and HealthKit. Bundle IDs: com.example.MyApp, com.example.MyApp.watchkitapp, com.example.MyApp.Widget. App Group: group.example.MyApp. It builds fine for me. When a teammate opens the project and tries to run on device, they get: Failed Registering Bundle Identifier The app identifier "com.example.MyApp" cannot be registered to your development team because it is not available. Change your bundle dentifier to a unique string to try again. What I've observed My other apps that have no entitlements build fine for every teammate. Looking at their embedded profiles, those sign with a wildcard profile (TEAMID.*). This app signs with an explicit profile (TEAMID.com.example.MyApp). If a teammate removes HealthKit and App Groups from all targets, the app builds for them under their own team using the same bundle ID. My understanding (please correct me) App Groups and HealthKit require an explicit App ID, which can only be registered to one team. Since I registered com.example.MyApp first, no other personal team can register the same explicit App ID hence the error. My questions Is that understanding correct — that an entitled (explicit) App ID can only ever belong to a single team? Is there any supported way to keep the same bundle identifier and keep App Groups + HealthKit while teammates build under their own separate personal teams? Or is moving to an Organization account (everyone as members of one shared team) the only way to share an entitled bundle ID across multiple developers? For free personal-team development, is the recommended pattern to give each developer a unique bundle ID + App Group (e.g. via per-developer .xcconfig), keeping entitlements intact? Just want to confirm I'm choosing the right approach before committing to it. Thanks!

I find the inspector, file navigator, issue navigator, etc. all hard to read. Is there a way to increase the size of these texts without changing all of the text on my machine?

Hello, I’ve been experiencing a persistent issue in Xcode since version 26.0, and it is still present in 26.2. When using the split view to display two files side by side, the area in the top‑right corner of the window (the inspector / options panel) starts flickering continuously. This happens regardless of whether I’m using the light or dark theme, and even with the Liquid Glass effect disabled in macOS settings. None of these changes have any impact on the issue. I have already submitted a bug report through Xcode (Feedback Assistant), but the issue is still present as of today. The flickering makes the interface difficult to use and visually very distracting. I’ve attached a video to clearly show the issue. I will review the attachment at the time I publish this post. Thanks in advance for any help or feedback. Video 1 https://www.icloud.com/iclouddrive/077l-R7Ybvxz89NI-B7DliEuA#xcode_bug1 Video 2 https://www.icloud.com/iclouddrive/0f6bJp48ioGRdkYiA2U4sI-cg#xcode-bug2

Since today (5th June), my Codex seems to be broken. First there is no response (wait for hours), now it just crash with this error whenever I issue a command: JSON-RPC global stream failed: The operation couldn’t be completed. (IDEIntelligenceProtocol.JSONRPCElement.Error error 1.) I have a ChatGPT Pro subscription and I don't know what to do. I have restarted Xcode, sign out and in of my account, delete DerivedData, restart machine, reinstall Xcode.

Last year, I changed my iMac i7 (2015) to a new Mac mini M1 with SD disk. I saw the difference, it was incredible fast...but now after one year of working on my project, I get freeze screen and automatic reboot I have 16Go RAM...and often more than 10Go for xcode ! I work with storyboard and I have more than 100 VC. Do I need to change parameter on Xcode to optimize or I must have now min 32 RAM. What is the best requirement for important project?