Post marked as Apple Recommended
I Faced same problem from few days ago in Japan. I wrote to feedback assistant FB9282952.
Post not yet marked as solved
Hi,
It seems that the DriverKit doesn't support it in Big Sur yet.
I found the comment below.
There is no support for IOSCSIArchitectureModelFamily classes like IOSCSIProtocolInterface in DriverKit yet. Support will be added in a future release. From:
https://developer.apple.com/forums/thread/650611?answerId=616563022#616563022
Our kext now works on Big Sur Beta 7.
I tested in Big Sur beta 6, and it didn't work fine.
Post not yet marked as solved
Hi,
In our kext (for the SCSI Block Command Device), we use a subclass of the IOUserClient to communicate with our user-space app.
I'm not sure you can use the same class in your kext.
The sample code is here:
https://developer.apple.com/library/archive/samplecode/SimpleUserClient/Introduction/Intro.html
Thanks,
I also have same problem.
Our kext had been worked fine until beta 2, but beta 3 couldn't load.
The Big Sur release note says that the exported symbols were changed and you need build your kext with each beta of Big Sur.
I rebuild it on beta 5 but the problem was not resolved.
Xcode 12 Beta 5 Release Notes - https://developer.apple.com/documentation/xcode-release-notes/xcode-12-beta-release-notes
Symbols exported by both xnu and Apple kernel extensions will change. Recompile your kernel extension with each update to macOS Big Sur 11 beta to ensure compatibility. (64262563)
Post marked as Apple Recommended
It seems that this problem no longer occurred in Japan.
Post marked as Apple Recommended
Same issue for me with the Developer ID Application certificate and the Developer ID Installer certificate, since about 2 days ago.
The pkgbuild and the productbuild also failed.
