Hello, It seems like the Kernel Debug Kit for macOS 15.0.1 (24A348) is missing from the list of downloads at developer.apple.com. It would be great if you could add them to the list of available downloads.
When trying to rebuild the kernel it fails with the following error message:
Error Domain=KMErrorDomain Code=34 "Missing Developer Kit: As of macOS 13.0, you will need to install a KDK matching your build 24A348 to rebuild kernel collections." UserInfo={NSLocalizedDescription=Missing Developer Kit: As of macOS 13.0, you will need to install a KDK matching your build 24A348 to rebuild kernel collections.}
But my macOS version is 15.0.1. Is there a workaround for this?
Hello, It seems like the Kernel Debug Kit for macOS 15.0.1 (24A348) is missing from the list of downloads at developer.apple.com. It would be great if you could add them to the list of available downloads.
If you haven't already, please file a bug on this then post the bug number back here.
But my macOS version is 15.0.1. Is there a workaround for this?
I haven't looked into this in any great detail, however, I believe the check here uses the "ProductBuildVersion" inside the "SystemVersion.plist" file you'll find inside the contents of each KDK. In theory at least, changing that value to "24A348" would bypass that check. HOWEVER, the primary point of this check is simply to prevent creating non-functional configuration where the kernel and the rest of the system can't really work correctly. That means:
-
It's entirely possible that you'd just fall at some later point when the actual "work" had started.
-
If the process succeeds, you may just end up with a broken system that won't boot.
-
If the system boots, it's entirely possible that you're running a configuration that either reintroduces previously addressed bugs or creates entirely new bugs that could never actually occur on a real system.
Basically, this is the sort of thing I might on a dedicated test machine if I couldn't think of any other way to investigate a critical issue. It might get you the critical information you need or it might be a pointless waste of your entire day.
If you decide to do this, be aware of the issues above and don't be surprised (or file bugs) if something break. I would only do this on a dedicated test device (or VM) and I would specifically avoid doing anything beyond what was specifically required by whatever you're trying to test.
__
Kevin Elliott
DTS Engineer, CoreOS/Hardware