“LLDB crash”

I've noticed this also happening with yy yank-line. In a playground, if I yy or dd a few times in quick succession, it crashes pretty consistently. Version: 26.1.1 (24455) Build Info: IDEApplication-24455000000000000~2 (17B100) Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd [1] Coalition: com.apple.dt.Xcode [3593] Hardware Model: MacBookAir10,1 OS Version: macOS 26.1 (25B78) Release Type: User Crash Reporter Key: 834538A1-954B-4B20-397E-404B2B357970 Incident Identifier: 72206D25-CA6F-4A1A-9130-473D798C7833

Core Problem: VoIP push notifications are not delivered to the application when it is in the background or terminated. After reviewing existing discussions on the forum, I concluded that the cause might be related to CallKit not having enough time to register. Yes, that's sort of correct. I think root of the problem is actually here: private let voipRegistry = PKPushRegistry(queue: .main) private var provider: CXProvider? ...and is tied to the dynamic of how static object initialization occurs. Basically, your PKPushRegistry object is going to be created IMMEDIATELY after your AppDelegate object is created and before basically any normal app methods are called, including didFinishLaunchingWithOptions. I'm not sure how the full process plays out from there, but I think the net result is that you're losing the initial push because of the time gap between PKPushRegistry's creation and when didFinishLaunchingWithOptions is called and the rest of your initialization completes. One thing to note here is that you ca

The crash issue that @edorphy reported in FB21121092 is resolved when you build the app with the released Xcode 26.2 version that came out today, build number 17C52. This version is not the same build as the Xcode 16.2 Release Candidate, so make sure to update to the final release version. @edorphy, had a follow-up statement to me for a different but related issue: you or others may have already seen this one but just in case you haven't: FB21240249 - DeclaredAgeRange: DeclaredAgeRangeAction symbol unavailable on macOS catalyst apps causing crash - documentation says otherwise I appreciate that! I personally had not seen this report, though others within Apple have. We're looking in to it. — Ed Ford,  DTS Engineer

We attempted to run a burn-in test while connected to our MacBook Pro M4 Max, but this crashed about 10 minutes into testing. We tried to run a 2-hour burn-in on the M4 Max host while charging the battery from below 5%, running six bus-powered drives (via ATTO/Black Magic/IOmeter), hitting the RJ45 port for 2.5Gbps (via JPerf), and streaming at least 4K60Hz video content to two displays; however, the M4 Max crashed in 20minutes. If you haven't already, please file a bug on this and post the bug number back here. In the bug, please attach full panic logs as well as a sysdiagnose from the machine that panic-ed. One comment on the log picture you posted. That particular panic message (Halt/Restart Timed Out) comes from a very specific point, which you can actually see here: xnu/iokit/Kernel/IOPlatformExpert.cpp: ... IOShutdownNotificationsTimedOut( thread_call_param_t p0, thread_call_param_t p1) { #if !defined(__x86_64__) /* 30 seconds has elapsed - panic */ panic(Halt/Restart Timed Out); ... C

In my case the crash was caused indirectly by animating the viewcontrollers change inside splitViewController(_:collapseSecondary:onto:). Not sure if that's allowed by UIKit, but similarly to your case this code has worked for more than a decade without problems until 26.1. Anyway, after removing the animation the issue disappears.

Sorry for the delay responding. I’m running out of workdays for 2025, so I can’t address everything upthread. Instead, I want to post some general guidelines. If DevForums blocks you from posting reasonable content with the message “This post contains sensitive language”, I’d appreciate you filing a bug about that. For instructions on how to do that, see the end of this post. After that, you’ll need a workaround. Here’s how to use a binary search to find the problematic text: As part of the bug reporting process, you saved a copy of your post to a text file. Make a copy of that file. Open it in your text editor of choice. Select half of the file and delete it. Copy the remaining text and try to post that. If it works, undo the delete, select the other half, delete that, and go back to step 4. Make sure to click the Edit button next to your post rather than posting a second reply. If it fails, go back to step 3 and continue dividing. Eventually you’ll get down to something super small and you can usually find

Whether this entitlement is assigned on a single app or your team account would depend on the entitlement team's evaluation of your use case at the time you have made the request. This would be determined on a case by case basis, and the information you received at the time you made the request and received the entitlement would have explained your usage limitations. Best would be to contact the entitlement team and inquire about the state of your entitlement assignments. White-labelled apps could be different, depending on what you exactly mean by white-labeled. If the apps are being published by your clients directly, they will need tp apply and acquire the entitlement separately. In any case, this sounds like you would be better off contacting the entitlements team and inquire. On the technical side, you could be encountering some other issue, like a build problem not configuring the extension correctly, the extension not being launched, or crashing, etc. Using the Console app and filtering on you