We are unable to process your request

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.

Hi @sandeshfromstrykerAI Following up on this. Please submit a feedback request with a sysdiagnose so we can investigate the issue. Thanks.

I am new to the apple developer program...The software is entirely written in python and includes ffmpeg That's probably the single most difficult type of software you can try to build on a Mac. We are currently adding the signing and notarization of the app to our github workflow. Have you tried to do any of this not using a GitHub workflow? Because I hate to tell you this, but most people who experience notarization problems get stuck at a much later stage. You haven't got to the difficult part yet. I would like feedback about if there is a fundamental flaw in our approach for signing and notarizing our application, so that we can identify it. I recommend skipping all the automation stuff until you confirm that your notarized app actually runs. Notarization adds a lot of runtime checks that are particularly difficult for Python apps to pass. I would appreciate some guidelines about how long to expect this notarization step to take until we can get notarization to finish within 10s of minutes, as we have a h

You can use BGTaskScheduler, especially BGProcessingTask to perform long running actions, including CoreBluetooth data transfer, but you can't have defined schedules for background tasks. They will be run by the system whenever it is appropriate to do so, and not being run is also a possibility. You may want to read about iOS Background Execution Limits before deciding to depend on background tasks. In any case, I am not sure how this will help. With Bluetooth state restoration, and for being woken up from suspended state there is indeed a ~10 second time limit, but that is per Bluetooth event, not for the whole task you are trying to do. If you need a minute to download the whole set of data from the device, you would not be doing that all at once anyways. The device will be writing the data in pieces, and as long as the subsequent writes to a notifying characteristic happens within the ~10 second limit, your app's time will be topped up. So, as long as you take less than 10 seconds to process each