Build, test, and submit your app using Xcode, Apple's integrated development environment.

Xcode Documentation

Posts under Xcode subtopic

Post

Replies

Boosts

Views

Activity

Calling .spotlightQuery() using AppIntentsTesting results in a crash on Xcode 27 beta 1
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!
4
0
33
1h
can not create iOS 27 Simulator
Apple M1 Pro, 26.5.1 (25F80) XCode 27.0 Beta (27A5194q) Command Line tools for Xcode 27 are installed. Device Hub Version 27.0 (235.4.2) Within device hub I can not create iOS 27 simulators. Only the 26.5 simulators are listed there. I installed the iOS 27.0 SDK. Also deleted and reinstalled it. The computer was restarted. No change. I am unable to create the proper iOS 27 Simulators. Any idea why this is not working? Thanks for the help upfront.
9
1
138
1h
Simulator screen recording shows iOS 26 navigation/sheet transition corner-rounding that is not visible on device
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
0
0
5
1h
[Feature request] Xcode 27 Easier Previewing while using coding agent
Filed a feature request in feedback assistant, but starting a discussion here as well since I'm probably not the only one. The issue I have is that coding assistant and previews seem to be mutually exclusive. That means that when I'm iterating on UI, I either have to rely on the coding assistant showing me preview screenshots (cannot interact), firing up Device Hub (have to manually kick off a build after each change) or manually opening the associated preview (requires a lot of hoping back and forth). This feels inefficient and means I have to hop around and manage my windows and tabs more. A slight work around is to open a split view with the file and preview there. This layout is inefficient and clunky. I would love if Xcode supported a pinned preview next to coding assistant (or automatically showed the relevant one). I imagine this working just like showing a preview next to a file cmd + opt + return hides/shows the preview. FB23219611
1
0
19
2h
Xcode 27: spike in "Class X is implemented in both" warnings
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.
0
0
12
2h
Xcode 26 on macOS 27?
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
1
5
235
3h
Xcode 26.4 breaks compilation
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)
4
2
294
3h
Xcode 26.4 and 26.3: Swift compiler crashes during archive with iOS 17 deployment target
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.
3
1
310
4h
Is SKTestSession available for Swift Package tests?
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?
1
0
20
10h
Unable to debug with iOS 27 and xcode-beta
▿ 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"
2
1
89
13h
Linker trying to link Metal toolchain for every object file on Catalyst
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?
2
3
1k
14h
Claude auth redirect failing
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.
2
1
100
15h
Xcode 27 Device Hub unable to create simulator
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.
6
5
815
19h
Calling .spotlightQuery() using AppIntentsTesting results in a crash on Xcode 27 beta 1
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!
Replies
4
Boosts
0
Views
33
Activity
1h
can not create iOS 27 Simulator
Apple M1 Pro, 26.5.1 (25F80) XCode 27.0 Beta (27A5194q) Command Line tools for Xcode 27 are installed. Device Hub Version 27.0 (235.4.2) Within device hub I can not create iOS 27 simulators. Only the 26.5 simulators are listed there. I installed the iOS 27.0 SDK. Also deleted and reinstalled it. The computer was restarted. No change. I am unable to create the proper iOS 27 Simulators. Any idea why this is not working? Thanks for the help upfront.
Replies
9
Boosts
1
Views
138
Activity
1h
Simulator screen recording shows iOS 26 navigation/sheet transition corner-rounding that is not visible on device
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
Replies
0
Boosts
0
Views
5
Activity
1h
Codex integration just stopped working
Nothing changed on my end, Pro subscription still active, but Xcode 26.5 (17F42) simply does not want to log into Codex anymore. It opens the OAuth flow and after finishing and closing the window, it still says "Not Signed In". Codex login works everywhere else, including the Codex app. What to do?
Replies
26
Boosts
2
Views
708
Activity
1h
[Feature request] Xcode 27 Easier Previewing while using coding agent
Filed a feature request in feedback assistant, but starting a discussion here as well since I'm probably not the only one. The issue I have is that coding assistant and previews seem to be mutually exclusive. That means that when I'm iterating on UI, I either have to rely on the coding assistant showing me preview screenshots (cannot interact), firing up Device Hub (have to manually kick off a build after each change) or manually opening the associated preview (requires a lot of hoping back and forth). This feels inefficient and means I have to hop around and manage my windows and tabs more. A slight work around is to open a split view with the file and preview there. This layout is inefficient and clunky. I would love if Xcode supported a pinned preview next to coding assistant (or automatically showed the relevant one). I imagine this working just like showing a preview next to a file cmd + opt + return hides/shows the preview. FB23219611
Replies
1
Boosts
0
Views
19
Activity
2h
Xcode 27: spike in "Class X is implemented in both" warnings
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.
Replies
0
Boosts
0
Views
12
Activity
2h
Xcode 26 on macOS 27?
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
Replies
1
Boosts
5
Views
235
Activity
3h
Xcode 26.4 breaks compilation
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)
Replies
4
Boosts
2
Views
294
Activity
3h
Agents in Xcode: Codex Sign In not working
Hey all, the codex sign in isn't working for me in Agents. I am using the 26.5 release candidate version. It always says "Not Signed In". I have completed the Sign In process multiple times. Anyone else seeing this? I have filed Feedback FB22732574
Replies
25
Boosts
6
Views
1.1k
Activity
4h
Xcode 26.4 and 26.3: Swift compiler crashes during archive with iOS 17 deployment target
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.
Replies
3
Boosts
1
Views
310
Activity
4h
Is SKTestSession available for Swift Package tests?
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?
Replies
1
Boosts
0
Views
20
Activity
10h
Unable to debug with iOS 27 and xcode-beta
▿ 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"
Replies
2
Boosts
1
Views
89
Activity
13h
Linker trying to link Metal toolchain for every object file on Catalyst
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?
Replies
2
Boosts
3
Views
1k
Activity
14h
Claude auth redirect failing
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.
Replies
2
Boosts
1
Views
100
Activity
15h
What is the logic for when the Enter Resize Mode button is enabled in the Device Hub?
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.
Replies
2
Boosts
0
Views
60
Activity
18h
How to pinch in Device Hub?
My question is how to pinch in and out in Device Hub. I can't find that function. I'm on a Macbook. Thanks.
Replies
1
Boosts
0
Views
49
Activity
18h
Device Hub Breaks on use
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.
Replies
2
Boosts
0
Views
60
Activity
19h
DeviceHub lacks any CarPlay simulator
iPhoneSimulator.app used to have the ability to show an external display / CarPlay display, but this feature does not appear to be available in DeviceHub.app, making it difficult (/impossible :( ) to test CarPlay features from the simulator.
Replies
2
Boosts
0
Views
88
Activity
19h
How to simulate two-finger touches in the Device Hub?
My app relies on two-finger tap for some interactions. This was easy in the old simulator by holding down option while clicking. Is there an equivalent interaction in Device Hub? (Option-click no longer seems to work.) If not, will this be added back in a future beta?
Replies
1
Boosts
0
Views
32
Activity
19h
Xcode 27 Device Hub unable to create simulator
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.
Replies
6
Boosts
5
Views
815
Activity
19h