LLDB crash

rootView.subviews is empty, while with iOS 18 : (lldb) po rootView.subviews ▿ 3 elements - 0 : > ▿ 1 : > - 2 : >

Hi, For your information, in Xcode 26 beta 5, the crash report provides some interesting new information. The crash occurred same with 'shared memory' Exception Subtype: KERN_PROTECTION_FAILURE at 0x000000038851ffd0 Exception Codes: 0x0000000000000002, 0x000000038851ffd0 VM Region Info: 0x38851ffd0 is in 0x38850c000-0x389a0c000; bytes after start: 81872 bytes before end: 21938223 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL shared memory 3884fc000-38850c000 [ 64K] rw-/rw- SM=SHM ---> shared memory 38850c000-389a0c000 [ 21.0M] rw-/rw- SM=SHM mapped file 389a0c000-38a8d8000 [ 14.8M] r-x/rwx SM=COW Object_id=c949d43b Termination Reason: SIGNAL 10 Bus error: 10 Terminating Process: exc handler [75426] However, the crash point provides even more information. 0 ??? 0x38851ffd0 ??? 1 RuntimeInternal 0x243f29ff8 _withConformanceCache(for:do:) + 240 2 ReflectionInternal 0x2428d7004 _typesThatConform(to:) + 148 3 PreviewsInjection 0x24178d7f0 0x241736000 + 358384 4 Preview

This is a recurring crash issue. Has anyone else encountered it?

The documentation does say The system can terminate a continuous background task abruptly depending on run-time conditions Of course both the documentation and the API are in pre-release state and the final state could be different than what you are expecting. In any case, this is something our engineering teams should investigate. We'd greatly appreciate it if you could open a bug report, include crash logs and sample code or models that reproduce the issue, and post the FB number here once you do. Bug Reporting: How and Why? has tips on creating a successful bug report.

We are using the Qt framework indeed. Do they bypass NSApplicationMain? I think so, but I'm not sure. I have posted on their forum to confirm this, and I’ll let you know. I believe so; however, the easiest way to check this for yourself is to add an abort() call at some point after your app is done launching. Then, just look at the crash log to see what's there. This is what that looks like for a basic AppKit app: Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x18e8a3388 __pthread_kill + 8 1 libsystem_pthread.dylib 0x18e8dc8cc pthread_kill + 296 2 libsystem_c.dylib 0x18e7e5c60 abort + 124 3 NSApplication_EventMonitor 0x104814cd8 -[AppDelegate applicationDidFinishLaunching:] + 44 (AppDelegate.m:19) 4 CoreFoundation 0x18e9bd62c __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 148 5 CoreFoundation 0x18ea4cce8 ___CFXRegistrationPost_block_invoke + 92 6 CoreFoundation 0x18ea4cc2c _CFXRegistrationPost + 436 7 CoreFoundation 0x18e98ca78 _CFXNotificationPo

I've submitted a ticket for my instance of the issue: FB19445364 (iOS 16 Simulators crash due to iOS 17 symbols - Xcode 26 beta 5)

Another update in case someone finds this useful in the future. If we create a new blank project, absolutely nothing in it, and we import the SquareReaderSDK, the app will crash on launch for iOS 18.5+ with iPad 7. No other devices, iPads or iPhones crash. And iOS versions less than 18.5 also don't crash. So there is definitely something weird about iPad 7s with iOS 18.5+.

@DTS Engineer Thank you for the hints. I was building with Xcode 26 Beta 3 and running on macOS 26 Beta 5 (not 4 as stated in my original message). I updated to Xcode 26 Beta 5 and it no longer crashes!

I can't reproduce the crash by running your code snippet @itsramensam provided with Xcode 26 Beta 5 + iOS 26 Beta 5. I tried building the Apple sample with Xcode 26 Beta 5 as well. I got several errors because several symbols had been changed on Beta 5. I went ahead to change the code to make it build. After that, the sample was up and running for me on my macOS / iOS 26 Beta 5 device. I am wondering if you tested with macOS / iOS 26 Beta 5. Because of the symbol changes, building with Xcode 26 Beta 5 and running on macOS / iOS 26 Beta 4 / 3 may trigger the crash. Best, —— Ziqiao Chen  Worldwide Developer Relations.

Also facing this issue when trying to initialize LanguageModelSession in our project when using Xcode 26 Beta 5. I had no issues using Beta 3 version. When running the FoundationModels sample projects and a basic SwiftUI project, I am also crashing at launch with the following error. I am on macOS Sequoia 15.5 running Xcode 26 Beta 5 on and iPhone 16 - iOS 26 device. Thank you!

I can confirm that this is also happening on iOS when building with Xcode 26.0 beta 5. The sample code below crashes at let session = LanguageModelSession() with EXC_BAD_ACCESS: struct ContentView: View { var body: some View { VStack {} .padding() .onAppear { let session = LanguageModelSession() } } }

Hello, I'm back revisiting this and have some findings to report. When I tried to create a group as seen below let descriptor = NWMultiplexGroup(to: endpoint) guard let identity = networkingService.importIdentityFromPKCS12() else { print([browseResultsChangedHandler] could not import identity) continue } do { let parameters = try NWParameters(identity: identity) let group = NWConnectionGroup(with: descriptor, using: parameters) group.stateUpdateHandler = { _ in } group.newConnectionHandler = { _ in } group.start(queue: .global()) networkingService.addGroup(deviceID, group) } catch { } Note that endpoint comes from browser's browseResultsChangedHandler Identity comes from me importing a SecIdentity from the user's p12 Parameters has the identity in it so that QUIC works. My app crashes when it tries to create the group and I see the following error nw_group_descriptor_allows_endpoint Endpoint 1B1654DF-62B5-4B29-9495-C4965E8E99FF._captadoh._udp.local. is of invalid type for multiplex group -[NWConcrete

Facing the same issue: FB19085434. Separate thread with more crash logs.