Search results for

LLDB crash

29,546 results found

Post

Replies

Boosts

Views

Activity

Reply to Apple Watch notifications while in sleep focus
Our engineering teams need to investigate this issue, as this might indicate an issue with OS 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 your Topic, then select the specific technology and relevant OS. For feedback related to Xcode, App Store Connect, or other developer tools and resources, select Developer Tools & Resources as your Topic, then select the specific tool or resource.
Topic: Community SubTopic: Apple Developers Tags:
1w
Reply to How do I use IOUserSCSIPeripheralDeviceType00?
First off, here: Here's my current personality dictionary. With this dictionary, the driver crashes, presumably in its init. One thing I strongly recommend during early bring-up is that your driver should do as LITTLE as possible. Basically, you can log data... and nothing else. I might not even call super. The problem here is that until you've got a foundation that works in the most BASIC sense (doesn't crash), you'll end up wasting time looking at what you THINK is the problem without actually knowing what's wrong. In any case, this is wrong: IOClass IOSCSIPeripheralDeviceType00 And should be: IOClass IOUserSCSIPeripheralDeviceType00 IOSCSIPeripheralDeviceType00 is the base class driver for mass storage devices. What you want is IOUserSCSIPeripheralDeviceType00, which is the DEXT support driver for SCSIPeripheralDriverKit. In more concrete terms, in the kernel IOUserSCSIPeripheralDeviceType00 is a subclass of IOSCSIPeripheralDeviceType00 which includes a bunch of additional callout hooks w
Topic: Developer Tools & Services SubTopic: Xcode Tags:
1w
Reply to ManagedSettings doesn't block Live Activities in the Dynamic Island
@Engineer This is not a crash but a UX issue, which I'd consider a bug for most if not all Shielding use cases. From my perspective the point of Shielding an app is to not distract or disclose anything from that app to the user. This works as expected for notifications, Live Activities in the Activity Centre, Widgets and the UI itself - with this one exception. I'd expect Live Activities to be shielded just like all other UI elements and notifications of the app. In our use case it provides a very high risk exposing the result which we're trying to protect the user from. Currently we've added a warning text that suggests the user should disable live activities for apps that risks spoiling the result, but obviously that's not the optimal behaviour.
Topic: App & System Services SubTopic: Widgets & Live Activities Tags:
1w
KVO crashes in older OS-Versions not replicable in Sequoia
Greetings, With MacOS 15 Sequoia, Apple updated key-value-observations in such a way, that an unremoved observation by a now deallocated object will no longer cause an exception, when the observed object triggers said observation. While this is fundamentally a positive change, the issue comes with the fact, that this change affects systems based on the version of their operating system and not the version of the operating system of the build system. Many of our customers use old operating system versions and old hardware - meaning they can't easily update. Since we need to use up to date Xcode versions to develop for newer systems, our developers tend to have rather new OS versions. This means, that we are increasingly facing bugs which only happen in customer systems but not in most developer (or QA) systems. Currently, we still can use earlier OS versions with Xcode to fix these bugs, but once the used Xcode versions no longer support MacOS 14 or below this will become a major hurdle. Are there known soluti
Topic: App & System Services SubTopic: General Tags:
3
0
495
1w
Reply to How do I use IOUserSCSIPeripheralDeviceType00?
Hi Kevin, thanks for your reply. Sorry for the delay, I was out for a while. Here's my current personality dictionary. With this dictionary, the driver crashes, presumably in its init. The crashed thread has OSMetaClassBase::Invoke(RPC) in its stack trace, none of the code appears to be mine. I can see my driver as an object in the IORegistry called driver - I use SetName late in my Start_Impl() to give it a globally unique name, so I crash before this. I also tried setting IOProviderClass to IOSCSIPeripheralDeviceNub, but my driver didn't appear to load at all then. As you can see, I changed the name of IOPropertyMatch so that it won't be considered, but I would prefer to match on USB vendor and product ID, rather than a name. Does the property I'm trying to match on have to be a property of the provider, or a property of the provider or any of its parents? And is IOPropertyMatch always considered, regardless of family, or are only some family-dependent property keys considered? O
Topic: Developer Tools & Services SubTopic: Xcode Tags:
1w
Reply to NSDocument doesn't autosave last changes
I tried this implementation to autosave changes before quitting the app, but it doesn't work since NSDocument.hasUnautosavedChanges is unexpectedly false. I now get the impression that perhaps a document would be saved automatically before quitting, but there is an issue with how NSTextView marks a document as edited. I would appreciate any insight into this issue. func applicationShouldTerminate(_ sender: NSApplication) -> NSApplication.TerminateReply { let edited = documents.filter({ $0.hasUnautosavedChanges }) if edited.isEmpty { return .terminateNow } var remaining = edited.count for document in edited { document.autosave(withImplicitCancellability: false) { [self] error in if let error = error { presentError(error) } else { remaining -= 1 if remaining == 0 { NSApp.reply(toApplicationShouldTerminate: true) } } } } return .terminateLater }
Topic: UI Frameworks SubTopic: AppKit Tags:
1w
[iOS 26][SDK 26] Application never received providerDidBegin(_:) delegate
Observed few times that providerDidBegin(_:) delegate never called for the complete app session after app init(as part of this CXProvider registered) which was built with SDK 26 and running on iOS 26. This issue observed multiple times with our testing. Since there is no providerDidBegin:, client is marking CallKit as not ready and never report any calls for VoIP APNS and ended up in app crash due to [PKPushRegistry _terminateAppIfThereAreUnhandledVoIPPushes] Please refer for sysdiagnose logs : FB19778306
Topic: App & System Services SubTopic: General Tags:
7
0
115
1w
Reply to disable-library-validation entitlement makes app unlaunchable
TN3125 is correct in saying that the hardened runtime entitlements are unrestricted, that is, their used doesn’t have to be authorisation by a profile. I’m not sure what’s going with your app but this is working for me: Using Xcode 16.4 on macOS 15.6.1, create a new project from the macOS > Command Line Tool target. In Signing & Capabilities > Hardened Runtime, check the Disable Library Validation box. Build and run; the program runs just fine. Dump the entitlements of the built executable: % codesign -d -vvv --entitlements - Test799497 … CodeDirectory v=20500 size=630 flags=0x10000(runtime) … … [Dict] [Key] com.apple.security.cs.disable-library-validation [Value] [Bool] true … The runtime flag indicates that the hardened runtime is enabled, and the com.apple.security.cs.disable-library-validation entitlement disables library validation. Moreover, this is a command-line tool, and thus it has no provisioning profile. Please repeat the above, just to make sure that we’re on the same page. As to your m
Topic: Code Signing SubTopic: Entitlements Tags:
1w
Foundation Models framework dyld symbol errors after macOS 26 Beta 2 - LanguageModelSession constructor missing
Foundation Models framework worked perfectly on macOS 26 Beta 2, but starting from Beta 3 and continuing through Beta 6 (latest), I get dyld symbol errors even with the exact code from Apple's documentation. Environment: macOS 26.0 Beta 6 (25A5351b) Xcode 26 Beta 6 M4 Max MacBook Pro Apple Intelligence enabled and downloaded Error Details: dyld[Process]: Symbol not found: _$s16FoundationModels20LanguageModelSessionC5model10guardrails5tools12instructionsAcA06SystemcD0C_AC10GuardrailsVSayAA4Tool_pGAA12InstructionsVSgtcfC Referenced from: /path/to/app.debug.dylib Expected in: /System/Library/Frameworks/FoundationModels.framework/Versions/A/FoundationModels Code Used (Exact from Documentation): import FoundationModels // This worked on Beta 2, crashes on Beta 3+ let model = SystemLanguageModel.default let session = LanguageModelSession(model: model) let response = try await session.respond(to: Hello) What I've Verified: FoundationModels.framework exists in /System/Library/Frameworks/ Framework is properl
Topic: Machine Learning & AI SubTopic: Foundation Models
1
0
593
1w
iOS 26 PB5 CarPlay possibly crashing car's infotainment system
This is purely speculation (but I have reason to believe it is the case) because I'm trying to narrow it down but, has anyone reported CarPlay in iOS 26 Beta potentially crashing vehicle infotainment systems? I have a 2025 Jeep Wrangler which is running UConnect 5. I can't prove it is the case but since updating to IOS 26 PB, I've been noticing that my infotainment system in my vehicle has been freezing, locking up, and resetting upon boot. I can't narrow this down to the phone causing it, but I can't rule it out as of now. I know that most of our infotainment units that offer CarPlay are typically running off Android, but is there a possibility that the iOS Beta is crashing our infotainment units upon connection? Again, I am just posting this to see if a) anyone can confirm that yes CarPlay can crash the Android backend of infotainment units or b) if anyone has experienced odd issues with CarPlay and their vehicle's infotainment system either freezing, crashing, or rebooti
Topic: Community SubTopic: Apple Developers Tags:
1
0
303
1w
Reply to The new navigationLinkIndicatorVisibility modifier crashes on < iOS 26
Seeing this crash in beta 8 (Xcode beta 7). Symbol not found: _$s7SwiftUI17EnvironmentValuesV33_navigationIndicatorVisibilityABIAA0G0OvpMV Referenced from: <35BAAD44-14F4-3B6C-8568-3E8B57A526ED> My call site: var allMerchantsSection: some View { Section { ForEach(model.paginatedMerchants.items) { merchant in NavigationLink(value: MerchantDestination.merchant(merchant)) { CardCell( image: .remote(url: merchant.info.bannerUrl), text: merchant.info.merchantName, description: nil, chipText: nil ) .navigationLinkIndicatorVisibility(.hidden) } .listRowBackground(Color.backgroundPrimary) .listRowSeparator(.hidden) .onAppear { if model.canLoadMore, merchant == model.paginatedMerchants.items.last { model.paginatedMerchants.currentPage += 1 } } } } header: { Text(All Merchants) } } made a feedback report: FB20108722
Topic: UI Frameworks SubTopic: SwiftUI
1w
Reply to App mysteriously crashing in CFNetwork.LoaderQ queue
Assuming that your crash reports can be trusted [1], the key failure here is in _dispatch_source_set_runloop_timer_4CF, which definitely rings some bells. Check out my response on this thread. IMPORTANT That response suggest a potential workaround, and I’d love to hear back from you as to whether that helps or not. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Your crash reports make it clear that you have third-party crash reporter installed (to wit, in your firs crash report, frame 2 of thread 10), and it’s not uncommon for third-party crash reports to mess up the Apple crash reporter. I talk about that issue in great detail in Implementing Your Own Crash Reporter. However, in this case I think it’s reasonable to trust the crash report because the crash is so familiar.
Topic: Programming Languages SubTopic: Swift Tags:
2w
Reply to ICEcard app closes when try to Face Scan via app
You’ve post a lot of links but none of them lead to a crash report )-: I’m looking for a file with either the .crash or the .ips extension. For advice on how to get that, follow the links in Posting a Crash Report. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App & System Services SubTopic: General Tags:
2w
Reply to Issue with App Crashing After Download from App Store
Thank you very much for your feedback and suggestions. As an additional note, my development environment is Visual Studio 2022, and the app was developed as a multi-platform application for iOS and Android. I am not entirely sure how I resolved the issue, but with the latest update it no longer occurs. The app now starts in the App Store environment just as it does in the TestFlight environment and no longer crashes. I made two changes during the process: re-downloaded all certificates (Distribution, Developer, Provisioning Profile) and added them again on my Mac. re-integrated all additional packages. After these steps, I uploaded the updated version to the TestFlight environment and subsequently submitted it for review in the App Store.
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
2w