LLDB crash

I'm only attempting to apply launch constraints because it seems to be the remedy to the helper/daemon crash. If there is a simpler remedy (like a new build setting I'm missing in XCode 26?) that would be even better. Mainly, I'm confused as to why building with XCode 26 and linking with macOS 26 would cause a crash with that code signing reason when previously it did not.

[quote='857581022, vojta.bohm, /thread/799368?answerId=857581022#857581022, /profile/vojta.bohm'] it's true by default on the shared URLSession which I use throughout the entire app. [/quote] Right. My suggestion was to set it to false, thereby enabling the new loading mode. If you see this crash with the new loading mode enabled, that’d be a useful datapoint. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I downloaded Runner-2025-09-11-220305.ips and used Quick Look in the Finder to get the human readable version. Here’s what I see: Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: TCC 0 This app has crashed because it attempted to access privacy-sensitive data without a usage description. The app's Info.plist must contain an NSMicrophoneUsageDescription key with a string value explaining to the user how the app uses this data. This shows that your app is trying to access the microphone but has no NSMicrophoneUsageDescription property. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I am also able to reproduce a crash using the provided code; however, it does not immediately crash for me; rather, if I select the text then it will crash (with a metal-related error). I'm running MacOS Sequoia (15.5) with XCode Version 26.0 beta 4 (17A5285i).

I see a very similar issue. The swift code has a text editor (NSTextView) and as soon as a scroll bar is added, the app crashes with an error like: [MTLDebugRenderCommandEncoder setRenderPipelineState:]:1616: failed assertion `Set Render Pipeline State Validation For color attachment 0, the texture sample count (1) does not match the renderPipelineState sampleCount (1065353216). and a similar-looking stacktrace involving MTLReportFailureand other drawing-related functions like QuartzCore (draw_shape, array_flush, draw_elements, draw etc). Possibly relevant - this is on an older intel mac with a now-unsupported GPU.

As a quick admin note, the comment feature in our forums doesn't really work very well, so I'd always recommend just posting your reply. These log message from com.apple.FSKit, category default, seem relevant. Looking at our code, I think something went wrong in your probeResource. Breaking down the log messages, these three messages are logged before calling probeResource and validates basic I/O: Successful dynamic cast of resource to bd. Got fd 3 readFirstSectorAndLog reading from 3 got rv 512 error (null) Successful read, first characters 4c4b:6000 This is logged by the reply block we pass to probeResource. The null here indicates that the FSProbeResult you returned was NULL: Returning (null) And this is logged shortly after in the same block, logging the Error probeResource returned: FSModule dev.steve.MFSLives.MFS probe: returned Error Domain=NSPOSIXErrorDomain Code=22 Invalid argument Notably, I don't see any logs from my code, so although it claims that the probe failed, it's not because of my code. So

I had the same crash happening, i managed to fix it. let me explain my use case, maybe it helps someone. I had a local database and a cloud database. The user could choose to migrate from local to cloud. During this process, I sometimes got OPs crash. I had something like this: local = try ModelContainer.local() cloud = try ModelContainer.cloud() try migrate(toCloud: true) try local.erase() //after migration, I erased the local instance. local = try ModelContainer.local() // << the fix // reinitializing the local container fixed the crash.

When building as described above, the helper crashes in such a way (Termination Reason: CODESIGNING 4 Launch Constraint Violation) that suggests I need to apply launch constraints to resolve the problem. I had not previously had launch constraints in my project.

Hi , Were having a similar issue, our company builds a web safari extension for enterprise. before iOS 26 (beta) release we would archive our extension and install to our devices no problem. since iOS 26 (beta) (we also tried in beta 4 23A5297m) the extension would archive perfectly but when installing the extension would just not run. its found in settings under safari extension, but when enabled the extension and open safari it will show error message Ext is no longer available. to rule out all code issues, we built a new project from scratch with a new bundle id, tried to archive with no problem, but when installed in an iphone 16 with iOS 26 BETA (23A5297m) same error ocurs it installs but when opening safari it will give an error message saying extension is no longer available. attached in the google drive link is a zip file of the new project, a zip file with a succesfull build of the ipa file with enterprise distribute, a video of the entire proccess and the error that the iphone gives. also attached a