I'm currently observing a problem similar to this thread https://developer.apple.com/forums/thread/737334
The difference is that this is happening after updating a system extension.
Basically same error, sysextd complains it can not check that the system extension is notarized: macOS Error 3 + Error code=-67050.
I think macOS (Sequoia 15.3.2 or 15.7.2 if it matters) is wrong in this case for the following reasons:
- when using spctl assess -t install, the system extension is reported to be correctly notarized.
- when restarting the Mac, the updated system extension is correctly checked and staged.
- if I run spctl assess before sysextd tries to check the system extension, it works.
I'm currently thinking of 2 reasons why the check does not work:
- sysextd is somehow trying to work with a cached assessment that has become invalid after the system extension was updated.
- macOS needs way more time between the update of the files and the request to update the staged extension. I tried adding a 5-second delay. This does not seem to work or at least reliably.
I tried just touching the system extension, no positive result. Unfortunately, in macOS Sequoia, it is not possible anymore to reset-default using spctl and see if it solves the issue, at least the next time the update is performed.
[Q] Is there some magic operation that would help macOS correctly check the notarization of an updated system extension?
My response on that other thread still applies here. Can you reproduce this on a clean machine? Or are you only seeing this on specific Macs?
Specifically, I recommend that you run this test:
- Install your target OS in a VM.
- Take a snapshot of the clean VM for the benefit of future tests.
- Install your product as a user would.
- Update your product as a user would.
Does that reproduce the problem?
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"