LLDB crash

And another app. Tips is crashing as well. All three apps (Tips, Mail, Safari) crash at the same point in WebKit, loading user installed Fonts. I've tried emptying my ~/library/fonts folder but that didn't help either.

Hi Kevin, I have createed 2 bugs for the above: Title: Method needed to detect if the current device supports DriverKit Bug number: FB18661587 Title: Crash when attempting to call systemExtensions(forApplicationWithBundleID bundleID: String) on iPad Pro Bug number: FB18662136 Thanks for your help on these.

To be clear, the Xcode project (and workspace) format is not documented for third-party developers, so DTS doesn’t support tools that generate or modify these formats. As to how this this is involved in the problem you’re seeing, that’s hard to say. It could just be a red herring. However, the nature of unsupported things is that they can cause all sorts of weird behaviour, so it’s quite possible that this is a factor. Two things: If you create a small test project and add these packages to it directly, does the code still crash? Please post a crash report for one of these crashes. I wanna skim through it for anything obvious. See Posting a Crash Report for advice on how to get and post the file. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Look at the backtrace of the crashing thread here: Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x7ff8089fb846 __pthread_kill + 10 1 libsystem_pthread.dylib 0x7ff808a36b16 pthread_kill + 259 2 libsystem_c.dylib 0x7ff80895573e abort + 126 3 libcoreclr.dylib 0x10fb351d9 PROCAbort + 57 4 libcoreclr.dylib 0x10fb350f9 TerminateProcess + 137 5 libcoreclr.dylib 0x10fd45de9 UnwindManagedExceptionPass1(PAL_SEHException&, _CONTEXT*) + 1081 6 libcoreclr.dylib 0x10fd45e2d DispatchManagedException(PAL_SEHException&, bool) + 61 7 libcoreclr.dylib 0x10fcb559d IL_Throw(Object*) + 445 8 ??? 0x11475fdca ??? 9 ??? 0x1139f5148 ??? 10 ??? 0x1139f4c42 ??? 11 ??? 0x1139f4981 ??? 12 ??? 0x1139f4633 ??? 13 ??? 0x113716f35 ??? 14 ??? 0x111942cf3 ??? 15 ??? 0x11193194e ??? 16 libcoreclr.dylib 0x10fdf7db1 CallDescrWorkerInternal + 124 17 libcoreclr.dylib 0x10fc57e13 MethodDescCallSite::CallTargetWorker(unsigned long long const*, unsi… 18 libcoreclr.dylib 0x10fb51588 RunMain(

I found the cause of the issue. Hopefully Apple can get this resolved in an upcoming beta release. I filed a bug report: FB18649885 Create a new iOS app project using Swift/Storyboard or Objective-C/Storyboard (I imagine a SwiftUI app would have the same issue). Edit the resulting ViewController.swift or ViewController.m. Import CoreLocation. Then in viewDidLoad, add one line: let coord = CLLocationCoordinate2DMake(40, 40) or CLLocationCoordinate2D coord = CLLocationCoordinate2DMake(40, 40); depending on your chosen language. These are just one of many possible lines of CoreLocation code that will cause the crash. Set the app's iOS deployment target to iOS 16, 17, or 18. Add a Mac Catalyst destination. Build and run the Mac Catalyst destination with Xcode 26 on a Mac with macOS 15 (or earlier I would think). The issue disappears if you have an iOS deployment target of iOS 15. The app will crash on startup due to the missing _LocationEssentials.framework.

Agreed - i was able to send one crash report before it died - phone was glitching - non responsive - rebooting before it also fully died. No way to issue crash reports on anything anymore Only device still working is my iPad as the update had not yet been applied

As said on https://github.com/facebook/react-native/issues/52394#issuecomment-3038830986 Replacing -lc++ by -lc++abi in the ld flags seems to fix the crash

Thanks for getting back to me on this one. I've been trying to do as you advised, but I'm hitting an error which gives the impression it's coming from the SystemExtensions API, but I could just be misunderstanding what it's trying to tell me. Please file a bug on this, attach the crash logs to that bug, then post the bug number back here. FYI, I'll be on vacation next week, but I'll try and take a look at this when I get back. __ Kevin Elliott DTS Engineer, CoreOS/Hardware

@DTS Engineer Ok, I followed your steps and discovered something interesting 🤓 Since my project is quite large, I initially decided to move and run the test code directly in the AppDelegate’s application(_:didFinishLaunchingWithOptions:) method. And it works! Even the UIApplication.shared.setAlternateIconName() method works as well. final class AppDelegate: UIResponder, UIApplicationDelegate { func application( _ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]? ) -> Bool { Task { _ = try! await URLSession.shared.allTasks try! await UIApplication.shared.setAlternateIconName(...) } } } Another unexplained curious thing I noticed is that after making these API calls in AppDelegate, my original code starts to work 😳 I'll provide some more information about my project, in case it helps. My project uses a modular architecture, and I use Tuist to generate the .xcodeproj and .xcworkspace files. The code that's causing the crash is located in

Thanks for pointing out my error. Unfortunately I'm still getting the same results with the correct separator: (lldb) po FileManager.default.fileExists(atPath: /private/var/mobile/Library/Mobile Documents/) true (lldb) po FileManager.default.fileExists(atPath: /private/var/mobile/Library/Mobile Documents/com~apple~CloudDocs) false (lldb) po FileManager.default.fileExists(atPath: url.path) false To try to determine that this wasn't just a LLDB issue, I updated my code slightly: func scene(_ scene: UIScene, openURLContexts URLContexts: Set) { guard let url = URLContexts.first?.url else { os_log(URL in %@ is nil, #function) return } let fileExists = FileManager.default.fileExists(atPath: url.path) fileExists is false after AirDropping a file. And of course this is happening within the method where openURLContexts is passed as an argument, and therefore the URL should be valid. So I'm still stuck at the same place.

Any help you can offer will be fantastic and greatly appreciated. Our Mac testers are getting jealous of our Windows testers. We can't have THAT!! CVRAT Crash log