We are unable to process your request

@Engineer this is not working for me. I have placed a .contextignore file next to my .xcworkspace file, it's contents look like this: CHANGELOG.md *.generated.swift *.mockingbird.swift However I'm still getting files that match these globs in my project context requests

So, let me start here: Why are all logs attributed to the kernel? Because that's where the logs came from. More specifically, the os_log function you are calling in DriverKit is not the same os_log function that exists in userspace. It actually does IPC into the kernel, which then logs out through the kernel’s logging infrastructure. Why would logs from 100% user-space code like ExternalMethod and StaticPingPong be attributed to the kernel process? I think the term user-space is deeply misleading when it comes to DriverKit. While it’s true in the basic technical sense, it is DEEPLY misleading when it comes to the practical relationship a DEXT has with the rest of the system. Practically speaking, your DEXT has very little connection to the larger system. It talks the kernel through the underlying DEXT infrastructure and it talks to user space through IOUserClient. That's ALL that exists, so the direct answer is that it's logging through the kernel because that's the only way it can log. WHY it works

I’m writing to follow up on our pending enrollment request for our organization. I would greatly appreciate your assistance in reviewing our case and providing any guidance or next steps needed to complete the process.

Thank you for your post and apologies for the delay. We recommend that you contact the developer account support team. For your question, please contact the Apple Developer Program Support Team. https://developer.apple.com/help/account/ If that request is with a team other than the Apple Developer Program Support Team, please get in touch with them through http://developer.apple.com/contact. Please make sure to mention that you were referred to them by DTS. We hope this information is helpful to you. Albert Pascual
  Worldwide Developer Relations.

Thank you for sharing the post and the video demonstrating the issue. Additionally, I appreciate the bug report. Could you reproduce the issue on iOS 26.1 beta 4? You can see the status of your feedback in Feedback Assistant. There, you can track if the report is still being investigated, has a potential identifiable fix, or has been resolved in another way. The status appears beside the label Resolution. We're unable to share any updates on specific reports on the forums. For more details on when you'll see updates to your report, please see What to expect after submission. Albert Pascual
  Worldwide Developer Relations.

The error message says: Please submit a bug report (https://swift.org/contributing/#reporting-bugs) and include the crash backtrace. Please follow through on that — it is extremely important so that the root cause of this issue in the compiler is addressed. Please share your report number here for reference. Further down, the message says: 3. While evaluating request ExecuteSILPipelineRequest(Run pipelines { PrepareOptimizationPasses, EarlyModulePasses, HighLevel,Function+EarlyLoopOpt, HighLevel,Module+StackPromote, MidLevel,Function, ClosureSpecialize, LowLevel,Function, LateLoopOpt, SIL Debug Info Generator } on SIL for MLProject) 4. While running pass #90956 SILFunctionTransform CopyPropagation on SILFunction @$s5MLProject23MLProjectTextRowObservationCyACSayAA0bD0CGcfc. for 'init(_:)' (at /Users/Desktop/xcode/MLProject/src/Frameworks/MLProject/MLProject/OCRScanner/MLProjectTextObservation.swift:135:5) Bullet point 3 shows this is the complier running some of its optimization passes on the named in

The audio recorded by clicking the Bluetooth device button is noise. The method called by Bluetooth devices is (requestBeginTransmitting), which enables AVAudioEngine recording in the (channelManager: PTChannelManager, didActivate audioSession: AVAudioSession) method. First off, I want to clarify that possible background activation paths here: The user pushes the talk button using the systems on screen UI. The app is Bluetooth authorized and adds directly calls requestBeginTransmitting() because of a BLE event from a proprietary accessory. The app has set setAccessoryButtonEventsEnabled(...) to true and the user sends non-HFP* remote control event to the PTT system. The standard example of this is pressing the play button on an A2DP/HFP Bluetooth accessory that's currently in playback mode. *HFP events are automatically handled by the system through the standard delegate system. Expanding on #3, this is how the PTT system provides its own support for the experience many PTT apps had previously implemented tha

Since we're talking about debuggers here, I just want to say that having DWARF (1) in your user name is excellent — thanks for the chuckle! that's actually funny; i never made that connection myself 🙈. [quote='862513022, DTS Engineer, /thread/804250?answerId=862513022#862513022'] As to attaching your custom debugger to a process with devicectl, this is not possible with the currently available commands provided by that tool. Our folks who work on the tooling around that command are interested in hearing what your needs are, so please send them some information on the type of functionality you need through Feedback Assistant. Once you've done that, please post the FB number here for reference. [/quote] Thanx! i have logged a feedback as FB20753296 just now. Please don't hesitate to let me know if i can provide any more specifics or details to make this more actionable. Getting this functionality would really help us out a lot. Thanx for your attention to the matter, marc

While there is no roadmap or timeline we can share, making a feature request with a Feedback Report will always help the teams understand the use cases developers are asking for, and will help future planning.