Also look under the "Other Installed Platforms" section in Xcode settings. It is those platforms that are taking up space in /Library/Developer/CoreSimulator. You can remove, from Xcode, the one that you don't need.

There are 3 projects in a workspace. The main project and two separate projects for two static libraries. Both static libs depend on a framework, a regular framework not a XCFramework. Everything is built from scratch, I own all the source code. The code for the framework is in a swift module. I set "DWARF with dSYM" on all the three projects, it was DWARF only for the libs, but no luck. I can debug the source code from the main project, it works just fine. However, the two static libraries contain the majority of the functionality and I can't debug it. I was adding logs here and there but it takes a lot of time.

Sorry, this Xcode16 just sucks. I've lost another half a days fiddling around with no luck, I just don't know what to do, and where. The project is big and in order to recreate the functionality, and the lldb bug, I have to build a whole new project, which will end up resembling the original one, minus some functionalities, so I dropped this route. The issue appears in one of the projects's internal static library. Now, I pause the execution at some breakpoint, run the "po" command and promptly get the "Couldn't realize Swift AST type of self". Then I run "swift-healthcheck", check the health log file, find the error below and conclude that the issue is in the static lib "***". SwiftASTContextForExpressions(module: "***", cu: "AllParts.swift")::LoadOneModule() -- Missing Swift module or Clang module found for "***", "imported" via SwiftDWARFImporterDelegate. Hint: Register Swift modules with the linker using -add_ast_path. Then I added "-add_ast_path" on the "Other Linker Flags" of the final executable, and now I get an error in Xcode saying "Unknown argument -add_ast_path". The static lib build settings have no "Other Linker Flags", and I don't know where else I should add this flag?! I mention that the I get a message in the console warning about empty dSYM file, but the executable is built with "DWARF with dSYM File", I triple checked it. warning: (arm64) /Users/SomeUser/Library/Developer/Xcode/DerivedData/SW-ajoovsaqjdvysgbbrebnfmoxycwm/Build/Products/Debug-maccatalyst/SW.app/Contents/MacOS/SW empty dSYM file detected, dSYM was created with an executable with no debug info. I'm not sure what you are asking here "Does that file reference UIKit types but is missing an import declaration?". Yes, it uses UIKit types but there is an "import UIKit" directive at the begining of the file where the breakpoint is.

The same, even with the latest Xcode, 16.2.

It seems that I'm missing something cause it doesn't work for me. Whenever I use this code: VStack { Button(action: {}) { Text("Short") .frame(maxWidth: .infinity) } Button(action: {}) { Text("Long title") .frame(maxWidth: .infinity) } } I get this: Then I added the "buttonStyle" over the whole button thinking that it'll extend the style to the whole button, but I only get a blue tint over the default length buttons, like this: VStack { Button(action: {}) { Text("Short") .frame(maxWidth: .infinity) } .buttonStyle(.borderedProminent) Button(action: {}) { Text("Long title") .frame(maxWidth: .infinity) } .buttonStyle(.borderedProminent) }

So ******* complicated to align and stretch two views, which would otherwise be easy to implement using UIStackView or AutoLayout.

Hi @eskimo, do you have any update on this? It's impossible to debug using two devices and a single cable, when unplugging one and plugging the other one, debugging continues on the former device. Is such a scenario illegal, and does Apple want us to stop doing it?

Same here... I've turned off the Mac and iPhone's wifi/bluetooth, restarted the Mac and Xcode, nothing works. This Xcode 15 is the buggiest of them all.

Thanks, I forgot to mention that I accepted the agreement prior to having this error.

I have also created the IPA manually and tried to upload it using Transporter app, but I got the following error. I did try to upload several times, and each time I get a different value in the error, so it looks like it's not because of the IPA itself. The provided entity includes an attribute with an invalid value (409) n/a (ID: a6e0572b-f67d-4add-bfae-dc9bde052be6)

It even crashes in the release version. Translated Report (Full Report Below) ------------------------------------- Process: Xcode [2147] Path: /Applications/Xcode.app/Contents/MacOS/Xcode Identifier: com.apple.dt.Xcode Version: 15.0 (22265) Build Info: IDEApplication-22265000000000000~3 (15A240d) Code Type: ARM-64 (Native) Parent Process: launchd [1] User ID: 501 Date/Time: 2023-09-24 11:08:28.8476 +0300 OS Version: macOS 13.5.2 (22G91) Report Version: 12 Anonymous UUID: AC134C1E-4270-BC50-46BA-0FC5F300594C Time Awake Since Boot: 590 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: archive info plist lock Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6 Terminating Process: Xcode [2147] Application Specific Information: abort() called com.apple.main-thread Application Specific Signatures: NSInvalidArgumentException Application Specific Backtrace 0: 0 CoreFoundation 0x00000001a3543154 __exceptionPreprocess + 176 1 DVTFoundation 0x0000000102713e30 DVTFailureHintExceptionPreprocessor + 388 2 libobjc.A.dylib 0x00000001a30624d4 objc_exception_throw + 60 3 CoreFoundation 0x00000001a362d9b8 -[__NSCFString characterAtIndex:].cold.1 + 0 4 CoreFoundation 0x00000001a363ac10 -[__NSPlaceholderDictionary initWithCapacity:].cold.1 + 0 5 CoreFoundation 0x00000001a3456ae0 -[__NSPlaceholderDictionary initWithObjects:forKeys:count:] + 320 6 CoreFoundation 0x00000001a3456974 +[NSDictionary dictionaryWithObjects:forKeys:count:] + 52 7 IDEFoundation 0x0000000108a55ac8 -[IDEArchiveDistributionRecord dictionaryRepresentation] + 296 8 IDEFoundation 0x0000000108a37180 __31-[IDEArchive setDistributions:]_block_invoke + 16 9 DVTFoundation 0x000000010270bb2c -[NSArray(DVTFoundationClassAdditions) dvt_arrayByApplyingBlock:] + 224 10 IDEFoundation 0x0000000108a37110 -[IDEArchive setDistributions:] + 84 11 Foundation 0x00000001a440ad94 -[NSObject(NSKeyValueObservingPrivate) _changeValueForKeys:count:maybeOldValuesDict:maybeNewValuesDict:usingBlock:] + 604 12 Foundation 0x00000001a4434f00 -[NSObject(NSKeyValueObservingPrivate) _changeValueForKey:key:key:usingBlock:] + 64 13 Foundation 0x00000001a444e42c _NSSetObjectValueAndNotify + 284 14 IDEFoundation 0x0000000108a36f08 __36-[IDEArchive addDistribution:error:]_block_invoke + 156 15 libdispatch.dylib 0x00000001a323c400 _dispatch_client_callout + 20 16 libdispatch.dylib 0x00000001a324b97c _dispatch_lane_barrier_sync_invoke_and_complete + 56 17 DVTFoundation 0x0000000102758014 DVTDispatchBarrierSync + 148 18 DVTFoundation 0x00000001027342b4 -[DVTDispatchLock performLockedBlock:] + 60 19 IDEFoundation 0x0000000108a36d30 -[IDEArchive addDistribution:error:] + 200 20 IDEFoundation 0x00000001086dc2f0 __35-[IDEDistributionUploadStep upload]_block_invoke.115 + 116 21 DVTFoundation 0x0000000102757330 __DVT_CALLING_CLIENT_BLOCK__ + 16 22 DVTFoundation 0x0000000102757b08 __DVTSyncPerformBlock_block_invoke + 68 23 CoreFoundation 0x00000001a34ca1d4 __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 28 24 CoreFoundation 0x00000001a34ca0e8 __CFRunLoopDoBlocks + 364 25 CoreFoundation 0x00000001a34c958c __CFRunLoopRun + 2432 26 CoreFoundation 0x00000001a34c84b8 CFRunLoopRunSpecific + 612 27 HIToolbox 0x00000001acd1adf0 RunCurrentEventLoopInMode + 292 28 HIToolbox 0x00000001acd1ac2c ReceiveNextEventCommon + 648 29 HIToolbox 0x00000001acd1a984 _BlockUntilNextEventMatchingListInModeWithFilter + 76 30 AppKit 0x00000001a66ef97c _DPSNextEvent + 636 31 AppKit 0x00000001a66eeb18 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 716 32 DVTKit 0x0000000102fd8a9c -[DVTApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 300 33 AppKit 0x00000001a66e2f7c -[NSApplication run] + 464 34 DVTKit 0x0000000102fd7cbc -[DVTApplication run] + 60 35 AppKit 0x00000001a66ba3cc NSApplicationMain + 880 36 dyld 0x00000001a3093f28 start + 2236 Application Specific Backtrace 1: 0 CoreFoundation 0x00000001a3543154 __exceptionPreprocess + 176 1 DVTFoundation 0x0000000102713e30 DVTFailureHintExceptionPreprocessor + 388 2 libobjc.A.dylib 0x00000001a30624d4 objc_exception_throw + 60 3 CoreFoundation 0x00000001a362d9b8 -[__NSCFString characterAtIndex:].cold.1 + 0 4 CoreFoundation 0x00000001a363ac10 -[__NSPlaceholderDictionary initWithCapacity:].cold.1 + 0 5 CoreFoundation 0x00000001a3456ae0 -[__NSPlaceholderDictionary initWithObjects:forKeys:count:] + 320 6 CoreFoundation 0x00000001a3456974 +[NSDictionary dictionaryWithObjects:forKeys:count:] + 52 7 IDEFoundation 0x0000000108a55ac8 -[IDEArchiveDistributionRecord dictionaryRepresentation] + 296 8 IDEFoundation 0x0000000108a37180 __31-[IDEArchive setDistributions:]_block_invoke + 16 9 DVTFoundation 0x000000010270bb2c -[NSArray(DVTFoundationClassAdditions) dvt_arrayByApplyingBlock:] + 224 10 IDEFoundation 0x0000000108a37110 -[IDEArchive setDistributions:] + 84 11 Foundation 0x00000001a440ad94 -[NSObject(NSKeyValueObservingPrivate) _changeValueForKeys:count:maybeOldValuesDict:maybeNewValuesDict:usingBlock:] + 604 12 Foundation 0x00000001a4434f00 -[NSObject(NSKeyValueObservingPrivate) _changeValueForKey:key:key:usingBlock:] + 64 13 Foundation 0x00000001a444e42c _NSSetObjectValueAndNotify + 284 14 IDEFoundation 0x0000000108a36f08 __36-[IDEArchive addDistribution:error:]_block_invoke + 156 15 libdispatch.dylib 0x00000001a323c400 _dispatch_client_callout + 20

Bug report sent as well. Is there any hope that Apple will ever fix this? User of my app are complaining that they can't access 3rd party storage, and I keep telling that to wait for Apple since more that 3 years.

It's a big mess of "Cannot open" and "Install command line tools" :(. I keep pressing "Open Anyway", it keeps telling me "Cannot open because unverified blah blah...". Then it tries for hours to install command line tools... and I'm still at it. Guys, do you still have a Quality Control Dept at Apple or did you fire them all?

Did you find a solution?

Finally found the issue, one of the projects in my workspace had an older version deployment target.