“DTiPhoneSimulatorErrorDomain Code 2”

I re-wrote the code after much experimentation, some time ago, and solved the issue. Please ignore.

Based on the documentation, this is intended to quickly terminate the app during logout or system shutdown. I'm not sure why we wrote it that way, but I believe that description is somewhat misleading. What sudden termination actually does is change how an app is expected to handle quit. The standard quit flow is that an app receives kAEQuitApplication, which then lets in opt in/out of exiting through applicationShouldTerminate(). Sudden termination reverses that approach. When sudden termination is enabled, the system quits your app by directly terminating it without any notice or warning. Your app is then responsible for telling the system NOT to do that by using disableSuddenTermination()/enableSuddenTermination(). You can read more about it here, but my guess is that it's probably not a factor. That's primarily because it's hard to send kAEQuitApplication to an FBA (Faceless Background App) unless you really dig into the system, but also because I believe we start with sudden termination disabled, so your

Is it only with objC code or Swift as well ? Xcode 26.5: In new iOS storyboard project I can connect IBOutlets from the Assistant editor in Swift...looks fixed there. Connection bubbles show. But in Objective-C the connection bubbles are completely gone from source files so in ObjC the problem is not fixed, actually worse. You can connect from the Connections Inspector though, but Xcode won't display connection status in ObjC source. So for me, because I still use ObjC the problem is worse. Hope that's not intentional. That would be very very negative evolution. You mean typing xibs by hand doesn't make you more productive!? 😂

Your collectionBehavior is close — canJoinAllApplications is the right option for spanning other apps' Spaces — but two other pieces are missing for floating above full-screen apps: 1. Accessory activation policy. macOS doesn't layer regular foreground apps above other apps' full-screen Spaces. Overlay utilities like DropOver use NSApplicationActivationPolicyAccessory, which removes the Dock icon and app menu bar (most overlay utilities add a menu bar status item in their place) and lets the app's windows appear above full-screen content from other apps. In your app delegate's applicationDidFinishLaunching: NSApp.setActivationPolicy(.accessory) 2. NSPanel with .nonactivatingPanel. An NSWindow activates its app when ordered front, which can cause a full-screen app to exit its Space. An NSPanel with the .nonactivatingPanel style mask doesn't. Full panel setup: let panel = NSPanel( contentRect: NSRect(x: 200, y: 200, width: 260, height: 140), styleMask: [.nonactivatingPanel, .titled, .closable]

Hello, thank you for the insights and the links; I am already reviewing the documentation to implement the necessary fixes. To provide more context on my scenario: the app communicates with a scale via TCP protocol. The scale creates its own dedicated Wi-Fi network exclusively for local network data transmission. The workflow is as follows: as soon as the app connects, the scale starts continuously sending data strings in the format: C, 050.1,c,N,000.0,. The app is only supposed to receive and process these values. Regarding the disconnection issue: the scale is dropping the TCP connection. The hardware developer (scale side) analyzed their logs and identified that the scale is receiving strange character sequences, such as ggggggggggfdhj. According to them, these strings are originating from the app. The critical point is that, in my iOS logs, I cannot find any record of the app sending this data, whether voluntarily or involuntarily. Since my code does not use unsafe pointers, as you observed, I am

Hi Kevin, Thank you for your guidance on the UserProcessBundledParallelTasks architecture and IPC optimization. After several adjustments, our DEXT driver is now running stably. We have completed a comprehensive performance comparison between Bundled Mode and Legacy Mode. Below is a summary of our findings. Following your suggestion, we analyzed the console logs during 4K Random I/O stress tests (iodepth=32). By analyzing approximately 6,363 calls, we confirmed that the kernel actively performs command batching: Results: Slots per Call (Count) Frequency Observation 1 Slot 5,654 Standard/Low load; kernel dispatches immediately. 2 Slots 628 Active Batching initiated under increased pressure. 3 - 4 Slots 75 Sustained high-concurrency batching. 5+ Slots 6 High-load peaks (Max observed: 11 slots per call). This data confirms that the batching mechanism effectively reduces the number of RPC/IPC calls to the DEXT when the system is under pressure. We conducted benchmarks using fio on RAID 5 array (4 HDDs) c