The app “Wi-Fi Aware Sample” on Bojie的iPhone quit unexpectedly. Domain: IDEDebugSessionErrorDomain Code: 20 Failure Reason: Message from debugger: The LLDB RPC server has crashed. You may need to manually terminate your process. The crash log is located in ~/Library/Logs/DiagnosticReports and has a prefix 'lldb-rpc-server'. Please file a bug and attach the most recent crash log. User Info: { DVTErrorCreationDateKey = 2025-09-17 10:26:56 +0000; IDEDebugSessionErrorUserInfoUnavailabilityError = Error Domain=com.apple.dt.deviceprep Code=-10 Fetching debug symbols for BojieU7684iPhone UserInfo={NSLocalizedRecoverySuggestion=Xcode will continue when the operation completes., NSLocalizedDescription=Fetching debug symbols for BojieU7684iPhone}; IDERunOperationFailingWorker = DBGLLDBLauncher; } Event Metadata: com.apple.dt.IDERunOperationWorkerFinished : { device_identifier = 00008101-001E29E01E63003A; device_isCoreDevice = 1; device_model = iPhone13,3; d
Search results for
LLDB crash
29,540 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
This has all the hallmarks a subtle memory management bug, possibly one that triggered by threading issues. These often result in weird behaviour like this. It looks like you’ve already tried ASan and TSan, which is a good. The other most popular tool for such issue is zombies. You should try that. See Standard Memory Debugging Tools for info and documentation references. One thing to note here is that ASan and TSan only work with code that you build. If the problem lies in a third-party library that you get as a binary rather than source code, these tools won’t help. And so… [quote='800689021, reidly, /thread/800689, /profile/reidly'] Removing all 3rd party libraries or frameworks … mostly worked in that the crashes went away [/quote] Did you try doing this incrementally? If you have a bunch of them, it’d be interesting to see which combinations do and don’t reproduce the problem. Finally, please post some example crash reports. I don’t need dozens, but a few that illustrate the more common
Topic:
Developer Tools & Services
SubTopic:
General
Tags:
I'm having a crash on an app that plays videos when the users activates close captions. I was able to replicate the issue on an empty project. The crash happens when the AVPlayerLayer is used to instantiate an AVPictureInPictureController These are the example project where I tested the crash: struct ContentView: View { var body: some View { VStack { VideoPlaylistView() } .frame(maxWidth: .infinity, maxHeight: .infinity) .background(Color.black.ignoresSafeArea()) } } class VideoPlaylistViewModel: ObservableObject { // Test with other videos var player: AVPlayer? = AVPlayer(url: URL(string:https://d2ufudlfb4rsg4.cloudfront.net/newsnation/WIpkLz23h/adaptive/WIpkLz23h_master.m3u8)!) } struct VideoPlaylistView: View { @StateObject var viewModel = VideoPlaylistViewModel() var body: some View { ScrollView { VideoCellView(player: viewModel.player) .onAppear { viewModel.player?.play() } } .scrollTargetBehavior(.paging) .ignoresSafeArea() } } struct VideoCellView: View { let player: AVPlayer
I am scheduling critical user notifications with a custom sound. This worked for years both on devices and in the simulator. Since Xcode 26 it crashes in simulator. Example let content = UNMutableNotificationContent() content.title = Critical content.body = Example content.sound = UNNotificationSound.criticalSoundNamed(UNNotificationSoundName(notification.aiff), withAudioVolume: 0.5) content.interruptionLevel = .critical let trigger = UNTimeIntervalNotificationTrigger(timeInterval: 10, repeats: false) let request = UNNotificationRequest(identifier: exampleCriticalNotification, content: content, trigger: trigger) UNUserNotificationCenter.current().add(request) It seems that simpler variants such as just content.interuptionLevel = .critical or just content.sound = UNNotificationSound.defaultCritical also crash. I assume that critical notifications is a small niche use case but i still hope this gets fixed. This is filed as FB20272392 with a full crash log.
Crashlog-0916-071225.log I have an app that crashes on OSX 26 only. I have a @StateObject which is an observer of the NSColorPanel. When I call let panel = NSColorPanel.shared in init(), SwiftUI will crash - apparently with an update while view is being updated. See crash log. I was able to work around it by adding let _ = NSColorPanel.shared in my AppDelegate before SwiftUI is initialized. The exact code worked fine in all previous OSX versions.
I've instilled Tahoe and Xcode 26(17A324) and the combination is virtually unusable, particularly the latter I'm no longer able to build projects reliably. My workflow is completely disrupted by a spinning beach ball so just a warning that you might want to delay until taking the plunge as I should have done. Fortunately, I have a back sequoia machine I can use instead.
Topic:
Developer Tools & Services
SubTopic:
Xcode
stopped working is unfortunately not a problem definition that anyone can give helpful suggestions for. One needs to know: what was happening, and what is now happening in details are there any errors? What are they? have you made any changes to your code? Even if it is a small change that you don't think is relevant? have you rebuilt the app since it was working. Is it a new Xcode version? Have you changed anything with the project settings? In any case, if you have not changed anything, and the same build of the app is not behaving the same on iOS 26, our engineering teams need to investigate this issue, as this might indicate a change with iOS 26. 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. Important: For feedback related to a specific framework or API, select Developer Technologies & SDKs as you
Topic:
App & System Services
SubTopic:
Core OS
Tags:
Hi everyone - I'm seeing an issue specifically on iOS26 where we instantiate a few storyboard items programmatically and pull their restoration identifier. On iOS26, these identifiers are null and cause a crash, but the assignments are on the storyboard and there has been no change to that logic. On iOS 18, for example, there is no crash and the identifiers are pulled properly. Anybody else seeing this?
When disabling the opacity slider of color panels, my app crashes with unsatisfiable layout constraints. Feel free reproduce with a minimal test project: A macOS app based on the Xcode 26.0 template with only one line added to the ViewController's viewDidLoad() function: NSColorPanel.shared.showsAlpha = false The issue doesn't occur if this property is set to true or not set at all. I just filed a corresponding bug report (FB20269686), although I don't expect any feedback from Apple ... as numerous issues I reported were never updated or commented at all (after migrating from RADARs).
Topic:
UI Frameworks
SubTopic:
AppKit
Our app has an old codebase, originating in 2011, which started out as purely Objective-C (and a little bit of Objective-C++), but a good amount of Swift has been added over time as well. Lots of Objective-C and Swift inter-op, but in general very few 3rd party libraries/frameworks. Like many other codebases of this size and age, we have a good amount of accumulated tech debt. In our case, that mostly comes in the form of using old/deprecated APIs (OpenGL primary amongst them), and also using some ‘tricks’ that allowed us to do highly customized UI popups and the like before they were officially supported by iOS, but unfortunately are still in use to this day (i.e. adding views directly to the UIWindow such that that are ‘on top’ of everything, instead of presenting a VC). Overall though, the app is very powerful and capable, and generally has a relatively low crash rate. About two months ago, we started seeing some new crashes that seemed to be totally unrelated to the code changes that wer
Hello Developer Support, I have the following code and the following crash. How can the swift data model unable to decode and yet able to display the decoded value at the same time?! What's missing here? CODE: @Model final class DisplayCache { init(point: MKMapPoint) { self.point = point } var point: MKMapPoint } CRASH SwiftData/ModelCoders.swift:1069: Fatal error: Unable to decode this value MKMapPoint(x: 74358466.66307731, y: 97927933.41833577)
The operating system is ready It is not. Xcode barely runs on macOS as it is. Xcode is the single most crash-happy app I have. It crashes on me at least 3-4 times per day, every day. Xcode on iPad would not be a pleasant experience.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Hello, I have been receiving crash reports on iOS 26 related to a view containing a UITextField. Although I have not been able to reproduce the issue locally and the exact reproduction steps are unknown, the call stack suggests the crash may be related to language or input method changes. If anyone has encountered a similar crash on iOS 26 or has any insights regarding language/input-related issues impacting UITextField behavior, your help would be greatly appreciated. The call stack from the reports is attached below. Exception NSInvalidArgumentException -[__NSPlaceholderArray initWithObjects:count:] attempt to insert nil object from objects[1] Fatal Exception: NSInvalidArgumentException 0 CoreFoundation 0xc98c8 __exceptionPreprocess 1 libobjc.A.dylib 0x317c4 objc_exception_throw 2 CoreFoundation 0xe1d7c -[__NSPlaceholderArray initWithObjects:count:] 3 CoreFoundation 0x1485d0 +[NSArray arrayWithObjects:count:] 4 UIKitCore 0xfc4d44 -[UIInlineInputSwitcher updateInputModes:withHUD:]
We have developed the driver for the ProCapture video capture card based on PCIDriverKit. The App can communicate with the driver through the UserClient API. Currently, there is an issue where, when the App starts, there is a small probability that it causes a driver crash. However, the crash stack trace does not point to our code but appears to be within the PCIDriverKit framework. We have spent several weeks debugging but still cannot identify the root cause of the crash. Could you please review the crash log and suggest any methods to help pinpoint the issue? com.magewell.ProCaptureDriver-2025-09-15-153522.ips com.magewell.ProCaptureDriver-2025-09-15-082500.ips
For anyone facing a similar issue, we found that the crash logs were not helpful. They were both misleading and lacked the necessary detail to diagnose the problem. To uncover the actual cause, we had to connect a user's personal device to Xcode and inspect the console directly. This revealed the true error, which was not captured in the standard crash reports. There really needs to be a better mechanism for users to securely share these logs with developers in cases like this, without requiring direct access to their device. In our case, the console logs indicated that corrupted data stored in the Keychain was causing the app to crash when accessed. Importantly, this had nothing to do with the didFinishLaunchingWithOptions method, despite what the crash logs initially suggested.
Topic:
App Store Distribution & Marketing
SubTopic:
General