Request failed with http status code 503

Additional information: kmutil rebuild frequently fails: % sudo kmutil rebuild Checking the auxiliary kernel collection... Error Domain=KMErrorDomain Code=31 Error occurred while building a collection: Cannot build collection without binaries as only 1 codeless kexts provided UserInfo={NSLocalizedDescription=Error occurred while building a collection: Cannot build collection without binaries as only 1 codeless kexts provided} Output from kmutil inspect on macOS 15.7: % kmutil inspect auxiliary kext collection at /System/Volumes/Preboot/DE1C1CE0-D3C6-403C-B5D8-56E6E003148C/boot/9334E85A7D36C17DBEE4F81854E2F1645866C0696EEA24433AC187CBE6575671EB84BD6D774A98804391CBAFCFC931CE/System/Library/Caches/com.apple.kernelcaches/kernelcache.auxkc.CAF862D59166BD22CE05B096DDC1685CA3725175A41E436AC4B1D29D8F89635C2B79BF606EDBCBDE1282FAEC5F559E73 (25966FB4-9792-D048-11B5-E51FCA0F69BB): Extension Information: com.magewell.ProCaptureDriver 1300.42.47 /Library/StagedExtensions/Library/Extensions/ProCaptureDriver

Can anyone give advice? Thanks a ton! Unfortunately, this is actually the first time I've looked at Building an Audio Server Plug-in and Driver Extension and, to be honest, that is not great sample code. Using darwinup in a shell script is not something any one should actually do. I've already filed a bug on this (r.163226098), but you're going to need to do a bit of work to end up with something reasonable. SO, what I would actually suggest is the following: Start with the sample Communicating between a DriverKit extension and a client app and get it building and running. That's our simplest sample and will let you sort out the basic build and install process. Once that's working, replace the DEXT inside that sample with the DEXT from Building an Audio Server Plug-in and Driver Extension. Once that's done, you'll have an installer app with an embedded DEXT, which is what ALL DEXT need to be shipped as anyway. Shifting to the codesign front: I would be ok for now with the local option, but XCode 16.4

Am I doing something wrong here? No, not really. I've actually seen variations of this failure across all macOS versions going back... well, basically forever. The details of EXACTLY how it plays out vary across system versions, but the basic dynamics at work here are: LaunchServices works by detecting when apps/components appear in the system, then reading the data from those components into its database. The nature of the development process means that you can easily produce new apps with a speed and volume WILDLY higher than any normal user would. The entire system is regularly interacting with the LaunchServices database at exactly the same time you're changing that configuration. ...the net result of which is that something occasionally goes wrong, leaving bad data in the database. I think I may be causing the constant unregister/register of the extension directly by rebuilding via Xcode. Or is it a problem with extensionkitservice? It's certainly a bug and, if you haven't already, please do file a bug o

Intel – macOS 15.6 ONLY: Broken. Have you tested this on: Multiple Intel machines. and/or A clean system reinstall, either by erasing the machine or by using a VM. Have you tested this on 15.7.1 (the current release)? Shifting to here: Is there a known Intel-only regression in 15.6 where FDA toggles for app-bundled daemons fail to persist? I'm not aware of any such issue and I'd expect a general FDA failure to cause significant problems. Having it be “Intel only is also quite odd, as everything that manages FDA state is at a high enough level of the system that the CPU architecture shouldn't matter. However, what I this is more likely is that there might be issues on a specific machine which would prevent FDA from sticking. Lastly, have you filed a bug on this and, if so, what's the bug number? Does launching the daemon immediately after install (triggered by a separate LaunchDaemon running an install.sh) interact with TCC/FDA persistence on Intel 15.6 specifically? Note inherently, though how it's l

I think I went to the right place to put in a feature request. It has been a while since Coded PHY was announced, so I'm sure Apple is aware of it and has a position on it. It would just be good to hear what it is. I see SoCs get significant range, in one test 500 meters (https://www.youtube.com/watch?v=ANqkKXDzWqo&t=52s One Plus Nord N10 5G phone). I also saw Direction Sounding support in another phone(https://www.youtube.com/watch?v=sx-6o64206Q Pixel 10). It would be great to hear if these innovations are coming to iPhone.

Hi Kevin — thanks for the detailed reply. Quick confirmations We’re already shipping the ES daemon as an app-bundled executable (signed, hardened, notarized). FDA is being granted through System Settings → Privacy & Security → Full Disk Access to the app bundle (per your #1), not to a bare exe. ES entitlement is present; Gatekeeper/SPCTL and codesign checks are clean. What we’re actually hitting (repro matrix) Apple Silicon (M-series) – macOS 15.6: Works. FDA toggles on and persists. ES daemon runs fine at boot. Intel – macOS ≤ 15.5: Works. Intel – macOS 15.6 ONLY: Broken. In Full Disk Access, turning the toggle On either immediately flips back Off, or appears On but flips Off after navigating away and back. When it “looks” On, the ES daemon still behaves as if FDA is not granted. This behavior is consistent across multiple Intel machines and fresh user profiles. Extra notes about launch The daemon is launched by launchd (system domain) as usual. Our installer (run by another LaunchDaemon’s install.sh) re

Hi @leokaminski07. Thanks for posting a sample project. I was able to reproduce your results here using your sample on an iPad Pro running iOS 26.0.1. Beyond turning off the Button Shapes option, I don't have any recommendations for avoiding this bug. Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a reference to your Xcode project and post the Feedback number here once you do. If you post the Feedback number here I'll check the status next time I do a sweep of forums posts where I've suggested bug reports. Bug Reporting: How and Why? has tips on creating your bug report.