Search results for

LLDB crash

29,562 results found

Post

Replies

Boosts

Views

Activity

The async/await API crashes in Xcode 16.3 and later
We use several UIKit and AVFoundation APIs in our project, including: setAlternateIconName(_:completionHandler:) getAllTasks(completionHandler:) loadMediaSelectionGroup(for:completionHandler:) Moreover, we use the Swift Concurrency versions for these APIs: @MainActor func setAlternateIconName(_ alternateIconName: String?) async throws var allTasks: [URLSessionTask] { get async } func loadMediaSelectionGroup(for mediaCharacteristic: AVMediaCharacteristic) async throws -> AVMediaSelectionGroup? Everything worked well with these APIs in Xcode 16.2 and earlier, but starting from Xcode 16.3 (and in 16.4), they cause crashes. We've rewritten the APIs to use completion blocks instead of async/await, and this approach works. Stack traces: setAlternateIconName(_:completionHandler:) var allTasks: [URLSessionTask] { get async } loadMediaSelectionGroup(for:completionHandler:) Also, I attached some screenshots from Xcode 16.4.
6
0
269
Jul ’25
Reply to The async/await API crashes in Xcode 16.3 and later
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
Jul ’25
Reply to App works fine in development but crashes in hardened runtime
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(
Jul ’25
Reply to Xcode 26 running Mac catalyst app crashes on dynamic loading with failure to find _LocationEssentials framework
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.
Jul ’25
打开显示HUD图形后,应用崩溃
hi everyone, 我们发现了一个和Metal相关崩溃。应用中使用了Metal相关的接口,在进行性能测试时,打开了设置-开发者-显示HUD图形。运行应用后,正常展示HUD,但应用很快发生了崩溃,日志主要信息如下: Incident Identifier: 1F093635-2DB8-4B29-9DA5-488A6609277B CrashReporter Key: 233e54398e2a0266d95265cfb96c5a89eb3403fd Hardware Model: iPhone14,3 Process: waimai [16584] Path: /private/var/containers/Bundle/Application/CCCFC0AE-EFB8-4BD8-B674-ED089B776221/waimai.app/waimai Identifier: Version: 61488 (8.53.0) Code Type: ARM-64 Parent Process: ? [1] Date/Time: 2025-06-12 14:41:45.296 +0800 OS Version: iOS 18.0 (22A3354) Report Version: 104 Monitor Type: Mach Exception Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KERN_PROTECTION_FAILURE at 0x000000014fffae00 Crashed Thread: 57 Thread 57 Crashed: 0 libMTLHud.dylib esfm_GenerateTriangesForString + 408 1 libMTLHud.dylib esfm_GenerateTriangesForString + 92 2 libMTLHud.dylib Renderer::DrawText(char const*, int, unsigned int) + 204 3 libMTLHud.dylib Overlay::onPresent(id) + 1656 4 libMTLHud.dylib CAMetalDrawable_present(void (*)(),
1
0
94
Jul ’25
How to play Vorbis/OGG files with swift?
Does anyone have a working example on how to play OGG files with swift? I've been trying for over a year now. I was able to wrap the C Vorbis library in swift. I then used it to parse an OGG file successfully. Then I was required to use Obj-C++ to fill the PCM because this method seems to only be available in C++ and that part hangs my app for a good 40 seconds to several minutes depending on the audio file, it then plays for about 2 seconds and then crashes. I can't get the examples on the Vorbis site to work in objective-c and i tried every example on github I could find (most of which are for iOS - I want to play the files on mac) I also tried using Cricket Audio framework below. https://github.com/sjmerel/ck It has a swift example and it can play their proprietary soundbank format but it is also supposed to play OGG and it just doesn't do anything when trying to play OGG as you can see in the posted issue https://github.com/sjmerel/ck/issues/3 Right now I believe every player that can play OGGs o
2
0
4k
Jul ’25
Xcode Cloud unable to execute iOS tests
All tests build and run locally just fine. Xcode Cloud can build my code, but always fails to run tests with the below errors. How can I even begin to troubleshoot this? I think my setup is pretty straightforward. Just a simple test plan that execute some unit tests with Swift Testing. Run command: 'xcodebuild test-without-building -destination 'platform=iOS Simulator,id=1EB80431-1A0B-4AD8-8EA6-968EA09C3F23' -resultBundleVersion 3 -resultBundlePath /Volumes/workspace/resultbundle.xcresult -resultStreamPath /Volumes/workspace/tmp/resultBundleStream679e7ce9-a095-4be5-8dfa-4c9df982e547.json -IDEPostProgressNotifications=YES -DTDKDisableSymbolCopying=YES -test-timeouts-enabled YES -maximum-test-execution-time-allowance 1800 -hideShellScriptEnvironment -maximum-parallel-testing-workers 8 -testProductsPath /Volumes/workspace/TestProducts.xctestproducts' (6378) encountered an error (Early unexpected exit, operation never finished bootstrapping - no restart will be attempted. (Underlying Error: Test crashed
2
0
560
Jan ’25
Reply to Detect if the current device supports DriverKit?
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
Topic: App & System Services SubTopic: Core OS Tags:
Jul ’25
Reply to The async/await API crashes in Xcode 16.3 and later
@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
Jul ’25
URL in scene openURLContexts does not exist
I'm trying to update an old iOS app to use the UIScene architecture, and I've run into a problem I'm hoping somebody can help me fix. When I try to share a file with my app by AirDrop from another device, the URL that I'm getting from the urlContexts argument does not exist on the device. Here's the code I'm using in my SceneDelegate class to get things going: func scene(_ scene: UIScene, openURLContexts URLContexts: Set) { guard let url = URLContexts.first?.url else { os_log(URL in %@ is nil, #function) return } // check that it's the proper file type guard url.pathExtension == fileExtension.replacingOccurrences(of: ., with: ) else { return } ... } When I set a breakpoint after populating the url property, checking its existence in the Xcode Console reveals the enclosing folder does not exist: (lldb) po url.path /private/var/mobile/Library/Mobile Documents/com~apple~CloudDocs/Downloads/Seattle Times 2025-04-30 10.dbsud (lldb) po FileManager.default.fileExists(atPath: URL(filePath: /private/
Topic: UI Frameworks SubTopic: UIKit Tags:
2
0
91
Jul ’25