LLDB crash

The user can put you into exactly the same state using Force Quit as will crashing. The standard solution here is for the child to monitor the parent and self-terminate if the parent dies. We already implemented that. The problem is that, in the case of user force-quitting, the user inflicted that upon themselves so the the app quit unexpectedly message is nothing out of ordinary, but if a simple app update also prompts the app quit unexpectedly that doesn't sound very good.

Thanks for the post. Are you using Flutter? Have you addressed by the support channel for Flutter - the third-party resource you are using. Unless another developer in the forums has experience with the third-party and can provide assistance. However I am sure the 3rd party tool could be aware of the issue if you provide them with crash files. Have you been able to reproduce on your environment? The objective-c code you posted seems ok, is that the part of the code is crashing? Have you use Xcode to reproduce it? Thanks Albert Pascual
  Worldwide Developer Relations.

It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. The screenshot above is the iOS system's crash log Just clarify what we’re talking about here, this is an Apple crash report from iOS 26.1: Exception Type: EXC_BAD_ACCESS (SIGKILL) Exception Subtype: KERN_PROTECTION_FAILURE at 0x0000000000000000 … Thread 0 name: Dispatch queue: com.apple.main-thread Thread 0 Crashed: 0 ??? 0x0 ??? 1 Test808813 0x10058c128 -[MainViewController tableView:didSelectRowAtIndexPath:] + 100 2 UIKitCore 0x1a563bc98 -[UITableView _selectRowAtIndexPath:animated:scrollPosition:notifyDelegate:isCellMult… 3 UIKitCore 0x1a563bfbc -[UITableView _userSelectRowAtPendingSelectionIndexPath:animatedSelection:] + 255 4 UIKitCore 0x1a563c0c8 -[UITableView _userSelectRowAtPendingSelectionIndexPath:] + 215 5 UIKitCore 0x1a407d878 -[_UIAfterCACommitBlock run] + 71 … You’re concern is with that SIGKILL, where prior to iOS 18 this was a SIGSEGV. That do

Hey @bradley_7, The 'init' for 'AVCaptureExternalDisplayConfigurator' refers to the CALayer as 'previewLayer'. Does it work on any CALayer or does it need to specifically be a need to be a 'AVCaptureVideoPreviewLayer'? As noted in the previewLayer property docs: You may specify either an AVCaptureVideoPreviewLayer or another CALayer instance that displays a camera’s video preview. When I call it like this the app crashes: *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[AVCaptureExternalDisplayConfigurator initWithDevice:previewLayer:configuration:] shouldMatchFrameRate is not supported' It's unclear why this crash is occuring, is it because the CALayer is not a 'AVCaptureVideoPreviewLayer'? That exception is being thrown because isMatchingFrameRateSupported is reporting false for your external display, but your AVCaptureExternalDisplayConfiguration specified true for shouldMatchFrameRate. Also, in the past I have done extensive testing with 'AVCaptu

I'm seeing a similar crash, also started on 26.1, see below. In my case I have no instance level button var, so I'm trying to find another workaround.. Thread 0 Crashed: 0 libobjc.A.dylib 0x308a6544c objc_retain 1 UIKitCore 0x31a164490 -[_UIButtonBarItemLayout _updateItemViewSizing] 2 UIKitCore 0x31a164180 -[_UIButtonBarItemLayout _updateItemView] 3 UIKitCore 0x31a6b6dc8 -[_UIButtonBarItemLayout minimumLayoutWidthGivenMinimumSpaceWidth:] 4 UIKitCore 0x31a6b7ee8 -[_UIButtonBarItemGroupLayout recalculateLayoutWidthsGivenItemSpaceWidth:] 5 UIKitCore 0x31a6a5a24 -[_UIButtonBar _widthInfoForLayout:] 6 UIKitCore 0x31a1623b0 -[_UIButtonBar _layoutBar] 7 UIKitCore 0x31a162324 __42-[_UIButtonBarStackView updateConstraints]_block_invoke 8 UIKitCore 0x31b717a88 +[UIView(Animation) performWithoutAnimation:] 9 UIKitCore 0x31a1622cc -[_UIButtonBarStackView updateConstraints] 10 UIKitCore 0x319dc97e4 -[UIView(AdditionalLayoutSupport) _previousFittingSizeInfo] [...]

[quote='868455022, bims, /thread/806594?answerId=868455022#868455022, /profile/bims'] I already feel bad asking you again [/quote] No worries. It gives me a good excuse to brush up on my debugging skills (-: [quote='868455022, bims, /thread/806594?answerId=868455022#868455022, /profile/bims'] It turns out that MTE and Malloc Stack Logging cannot be enabled at the same time. [/quote] Bah. This isn’t super surprising, and it’s the sort of thing I’d know if I had an iPhone 17 to play with. It’s definitely time to ping my boss about that. [quote='868455022, bims, /thread/806594?answerId=868455022#868455022, /profile/bims'] Unfortunately, I didn't really understand where/what to look for in Xcode. [/quote] OK. Lemme run you through a non-MTE example: Using Xcode 26.1 on macOS 15.7.1, I created an iOS app with two buttons wired up to these two methods: var memory: UnsafeMutableRawPointer? = nil func mallocAction() { self.memory = malloc(1024) } func freeAction() { free(self.memory) } In the scheme editor, I enabled

I uploaded a new version to TestFlight and here is my symbolicated crash report. My application always crashes shortly after launch. Can my symbolicated crash report help to find the issue? Original crash report: Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: SIGNAL 6 Abort trap: 6 Terminating Process: ProjectiOS [695] Triggered by Thread: 0 Thread 0 name: Thread 0 name: Thread 0 Crashed: 0 libsystem_kernel.dylib 0x000000023a1f00cc __pthread_kill + 8 1 libsystem_pthread.dylib 0x00000001ecb44810 pthread_kill + 268 (pthread.c:1721) 2 libsystem_c.dylib 0x000000019c3d7f64 abort + 124 (abort.c:122) 3 ProjectiOS 0x0000000105b6ef34 0x104b9c000 + 16592692 4 ProjectiOS 0x0000000105a2fbc8 0x104b9c000 + 15285192 5 libsystem_platform.dylib 0x00000002a5c47158 _sigtramp + 56 (sigtramp.c:116) 6 libsystem_pthread.dylib 0x00000001ecb44810 pthread_kill + 268 (pthread.c:1721) 7 libsystem_c.dylib 0x000000019c3d7f64 abort

Thank you for the crash file. However, it appears that the crash file is not symbolicated from your symbol file. The crash occurred in thread 0, but there are 16 frames for the project ProjectiOS without symbols. Kindly submit a comprehensive crash report, adhering to the guidelines outlined in Posting a Crash Report. https://developer.apple.com/forums/thread/688669 Hope this helps Albert Pascual
  Worldwide Developer Relations.

I'd need to dig through our code to be sure of all the details; however, this is what's mostly likely going on: Now this is where things go wrong. On macOS 15, our app seems to be gracefully terminating (we attached it with lldb, and it shows that our app returns with 0 when we click Continue“), which is fine. This is likely the classic macOS app lifecycle, which involves your app receiving an AppleEvent and then choosing to exit. Strictly speaking, your app wasn't terminated— the system asked it to quit, and it eventually chose to exit (it wasn't not required to). However, for macOS 26, though, it seems that TestFlight just directly SIGKILLs our app. This sounds like the sudden app termination lifecycle, as described here. In that approach, your app is responsible for telling the system when it can't be killed, and the system is allowed to terminate your app any other time. The link above has the full details on that. However... (indicated by lldb), which means that all of our app's child p

Thank you for the answer and explanation Greg, much appreciated. The 'init' for 'AVCaptureExternalDisplayConfigurator' refers to the CALayer as 'previewLayer'. Does it work on any CALayer or does it need to specifically be a need to be a 'AVCaptureVideoPreviewLayer'? I tried to use it on a CALayer like this: func setupDisplayConfigurator() { if #available(iOS 26.0, *) { // Fetch Video Input guard let videoInput = videoInput else { return } // Fetch CALayer for window in additionalWindows { print(window: (window) | (window.rootViewController?.view.layer)) } guard let layer = additionalWindows.first?.rootViewController?.view.layer else { return } // Create Display Config let config = AVCaptureExternalDisplayConfiguration() config.shouldMatchFrameRate = true // Create Configurator let configurator = AVCaptureExternalDisplayConfigurator(device: videoInput, previewLayer: layer, configuration: config) } } The CALayer is coming from an array of UIWindow: private var additionalWindows: [UIWindow] = [] When I call it

Hello Allen, Thanks for your post and your crash stack trace. To investigate and resolve the crash, please follow these steps: Fully symbolicate the crash report. See Adding Identifiable Symbol Names to a Crash Report. Match the crash report to a common pattern. Based on the pattern, take specific actions to further investigate the crash. See Identifying the Cause of Common Crashes. For additional help investigating why your app crashed, please refer to the following resources: Analyzing a Crash Report Diagnosing Issues Using Crash Reports and Device Logs Understanding Crashes and Crash Logs If you are still unable to resolve the crash: Send us the fully symbolicated Apple crash report from step 1. Please do not send crash logs generated by third-party analytics libraries. Tell us the specific debugging actions you took in step 2. If your issue persists after following these s

Phew, I already feel bad asking you again 😅 It turns out that MTE and Malloc Stack Logging cannot be enabled at the same time. But I've tried to enabled Malloc Stack Logging, and then get delayed crash somewhere else. Unfortunately, I didn't really understand where/what to look for in Xcode. I tried to hit the 'Memory Graph Debug' but then the crash context seemed to get lost... most likely I am doing it wrong... A little context of our app: An UIPageViewController where you can swipe left/right to see the next/previous image. An UIViewController that has a TileImageView subview TileImageView that shows an image. This view is using CATileLayer. When draw(rect:) is called for a specific tile, we either show a cached tile or send a network request to a local server for the tile data. When the network response is received (callback in draw(rect:) we call the view's draw(rect:) to update with tile. Now if I scroll through the pages the crash may occur. As stated before this code was wo

[quote='868298022, bims, /thread/806594?answerId=868298022#868298022, /profile/bims'] Looking at the ips-file I found that it does not show the finding that Xcode show [/quote] Right. Xcode has MTE smarts beyond what the human readable crash report shows. To see the underlying data, open the JSON crash report and search for memoryErrorReport. With some reformatting you get this: memoryErrorReport : { faultAddress:0x0c00000d9de112c0, blamedAllocation: { size:48, allocationTrace:…, deallocationTrace:…, isFreed:true, address:0x0c00000d9de112c0 }, errorType:use-after-free }, The allocationTrace and deallocationTrace backtraces need further massaging. I did a hack-ish job of that and have included the results at the end of this post. I wanted the JSON crash report so that I could run it through some internal tools. I was able to do the first part of that today. I was hoping it might point me at some known bugs. It did, but those were resolved a while bug and thus are unlikely to be the c