Search results for

LLDB crash

29,558 results found

Post

Replies

Boosts

Views

Activity

Reply to BGContinuedProcessingTask code pauses when device is locked
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.
Aug ’25
Reply to macOS26: MenuBarExtra item not showing
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
Aug ’25
Reply to iOS 18.5 crash with iPad 7 only
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+.
Aug ’25
iOS 18.5 crash with iPad 7 only
Weirdness going on here. Our app is crashing on startup with iPad 7s running iOS 18.5. Before updating to iOS 18.5, it was working fine on iPad 7s. Even with iOS 18.5, it is working fine on every device we have tried including dozens of other iPads and iPhones. We have narrowed it down to the SquareReaderSDK. If we remove that SDK, it will launch and work without issues. But, many of our users need the SquareReaderSDK. The crash happens at app load, before appDelegate didFinishLaunchingWithOptions. So we can't figure out any way to debug the issue. Is anyone else having a similar issue? Square thinks it is an Apple issue.
4
0
88
Jun ’25
Reply to Initializing LanguageModelSession crashes app on macOS
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.
Aug ’25
Reply to Initializing LanguageModelSession crashes app on macOS
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!
Aug ’25
Reply to NWBrowser + NWListener + NWConnection
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
Aug ’25
Xcode 26 Beta Crash on iOS 18 and below – UIToolbar in XIB/Storyboard Causes
Hey everyone, Just wanted to share a critical issue we’ve encountered while testing our app on iOS 18 simulators and devices using Xcode 26 Beta 3: Crash Details We're seeing the following fatal exception during launch: NSInvalidUnarchiveOperationException Could not instantiate class named _TtGC5UIKit17UICoreHostingViewVCS_21ToolbarVisualProvider8RootView_ because no class named _TtGC5UIKit17UICoreHostingViewVCS_21ToolbarVisualProvider8RootView_ was found... The crash originates from Storyboards/XIBs that include a UIToolbar. It appears UIKit is referencing an internal SwiftUI-related class (UICoreHostingView), which isn't present at runtime — leading to immediate crashes. Affected: Apps using UIToolbar in Storyboards or XIBs Running on iOS 18 (Simulators or Devices) and below Built using Xcode 26 Beta 3 CrashLog: Fatal Exception: NSInvalidUnarchiveOperationException 0 CoreFoundation 0x11a21c __exceptionPreprocess 1 libobjc.A.dylib 0x31abc objc_exception_throw 2 CoreFoundation 0x178
2
0
254
Jul ’25
macOS 26 beta 4 and iOS 26 beta 4 - WebKit XML parser crashes parsing XHTML with namespaces
Our app, VitalSource Bookshelf, is an EPUB reader that uses a WKWebView to display book content. The EPUB content format is XHTML and uses namespaces (for the epub:type declaration). On beta 4, the webkit process repeatedly crashes when loading our content. The crash appears to be in the XML parser. Here's what's at the top of the stack trace: 0 WebCore 0x19166a878 WebCore::XMLDocumentParser::startElementNs(unsigned char const*, unsigned char const*, unsigned char const*, int, unsigned char const**, int, int, unsigned char const**) + 4968 1 libxml2.2.dylib 0x19c5a2bd0 xmlParseStartTag2 + 3940 2 libxml2.2.dylib 0x19c59e730 xmlParseTryOrFinish + 2984 3 libxml2.2.dylib 0x19c59d8e4 xmlParseChunk + 708 4 WebCore 0x191668ec8 WebCore::XMLDocumentParser::doWrite(***::String const&) + 636 5 WebCore 0x191665b78 WebCore::XMLDocumentParser::append(***::RefPtr, ***::DefaultRefDerefTraits>&&) + 304 6 WebCore 0x190105db0 WebCore::DecodedDataDocumentParser::appendBytes(WebCore::DocumentWriter
Topic: Safari & Web SubTopic: General
3
0
442
Aug ’25
Layout Engine Crash on iOS 26: NSInternalInconsistencyException
Starting with iOS 26 beta, I'm encountering an intermittent crash in production builds related to Auto Layout and background threading. This crash did not occur on iOS 18 or earlier and has become reproducible only on devices running iOS 26 betas. We have already performed a thorough audit of our code: • Verified that all UIKit view hierarchy and layout mutations occur on the main thread. • Re-tested with strict logging—confirmed all remaining layout/constraint/view updates are performed on the main thread. • No third-party UI SDKs are used in the relevant flow. Despite that, the crash still occurs and always from a background thread, during internal UIKit layout commits. Fatal Exception: NSInternalInconsistencyException Modifications to the layout engine must not be performed from a background thread after it has been accessed from the main thread. 0 MyApp 0x7adbc8 FIRCLSProcessRecordAllThreads + 172 1 MyApp 0x7adfd4 FIRCLSProcessRecordAllThreads + 1208 2 MyApp 0x7bc4b4 FIRCLSHandl
4
0
460
Jul ’25
Reply to For the property modifiers of XIB controls, should we use strong or weak?
Our code is like this: @interface LLLineMoreView() @property (strong, nonatomic) IBOutlet UIView *topLineView; @end Exception Category: mach Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000008 Crashed Thread: 0 CrashDoctor Diagnosis: Attempted to dereference garbage pointer 0x8. Thread 0 Crashed: 0 CoreFoundation 0x000000018bb3ea7c _CFXNotificationRegistrarAddObserver + [ : 368] 1 CoreFoundation 0x000000018bb3ea0c _CFXNotificationRegistrarAddObserver + [ : 256] 2 CoreFoundation 0x000000018bb3e890 CFXNotificationRegistrarAdd + [ : 576] 3 CoreFoundation 0x000000018bb3e070 _CFXNotificationRegisterObserver + [ : 248] 4 UIKitCore 0x000000018e3a39ac UILabelCommonInit + [ : 188] 5 UIKitCore 0x000000018e8133cc -[UILabel initWithCoder:] + [ : 212] 6 UIFoundation 0x000000019747aaa4 UINibDecoderDecodeObjectForValue + [ : 684] 7 UIFoundation 0x000000019747ac30 UINibDecoderDecodeObjectForValue + [ : 1080] 8 UIFoundation 0x000000019747a6f8 -[UINibDecoder d
Topic: UI Frameworks SubTopic: UIKit Tags:
Aug ’25