Kevin-san, Thank you for sharing the information and coordinating with the Apple engineers. You are absolutely correct—my initial procedure was using a development embedded.provisionprofile. Following the URL you provided, I retried the DriverKit signing and notarization process, and the status now shows as “Accept.” At this point, I believe this is the best approach. I truly appreciate all the guidance and support you’ve given me!

I built Dext with a development ID and successfully re-signed and notarized it. This time, I only notarized the Driverkit, and plan to do the installer app later. Here are the steps I tried: Signed the build using Apple Development in Xcode Re-signed the build product Zipped the build product Notarized using xcrun notarytool submit, which returned Accept. Below is a sample re-signing command. codesign \ --sign $CODE_SIGN_IDENTITY \ --entitlements <entitlement-file> \ --options runtime \ --verbose \ --force \ build/Release/<my-driver>.app I'll probably need to eventually create an installer app and notarize it, but I think I've temporarily resolved the recent issue of not being able to sign with a Developer ID in Xcode. If you have any issues from an engineering perspective, please let me know.

My current goal is to ship the PCIe DriverKit. I want my customers to be able to install our DriverKit without having to disable SIP or anything like that. I tried the following value as suggested, and the build did indeed pass. <string>0xFFFFFFFF&amp;0x00000000</string> After checking the contents of the downloaded provisioning file again, I was able to clarify the problem. The value in the file created in App Development wasn't set properly. Created a provisioning file with DriverKit App Development and checked the value of IOPCIPrimaryMatch. <string>0xFFFFFFFF&amp;0x00000000</string> Created a provisioning file with the Distribution Developer ID and checked the value of IOPCIPrimaryMatch. <string>0x00001916&amp;0x0000FFFF</string> Why is there a difference between the Apple Development value and the Developer ID value? My account belongs to a corporate account. Is this related? Also, when I check your post, it seems like I've never created a provisioning file. That's strange. Is the local file on my PC invalid? As I mentioned at the beginning, I found the following article and was aiming to sign using Apple Development. https://developer.apple.com/forums/thread/743021 However, according to the URL you provided, would manual signing using a provisioning file created with a Distribution Developer ID be better? Actually, I was having trouble with manual signing, and that's when I found the above article.

Thank you for your reply. I understand that the following is a reserved character in XML: "&amp;" Below are the current expected and actual values. Driverkit expected value <string>0x00001916&amp;0x0000FFFF</string> Provisioning file contents <string>0x00001916&amp;0x0000FFFF</string> Entitlements file contents <string>0x00001916&amp;0x0000FFFF</string> I'm not sure why Xcode "Signing Certificate" status is "Failed" with the above configuration. It doesn't seem to me that Driverkit and the provisioning file expect "&" as the expected value. Based on the above, isn't it Xcode that expects "&"? I'm suspicious of Xcode's behavior. I'm worried that resubmitting the authorization request won't improve the situation. Is my understanding incorrect?

Thank you for your reply. I'm sorry for the late response, as I was working on another issue. I understand that I need to resubmit. I would like some advice on how to submit the application before resubmitting. Based on my current understanding, since it's XML, I believe the following value is correct: <string>0x00001916&amp;0x0000FFFF</string> However, currently, if I enter "&", the "Signing Certificate" status displays "Failed." Based on the current situation, does this mean that when resubmitting, I'm required to enter the following value, including "&"? <string>0x00001916&amp;0x0000FFFF</string> There's one thing that concerns me. I checked the contents of the provisioning file I downloaded from the URL you provided. I thought the current issue was occurring because it didn't contain "&". However, when I actually looked at the file, I found that it did contain "&". $ security cms -D -i mep_DeveloperID_2030_DextPCIe2.provisionprofile -o test.plist $ cat test.plist <dict> <key>IOPCIPrimaryMatch</key> <string>0x00001916&amp;0x0000FFFF</string> </dict> The provisioning file appears to me to have the correct value. If you could tell me the correct value for IOPCIPrimaryMatch in this situation, I will resubmit my authorization request.

Your answer is helpful. My previous question was strange because I didn't consider posting it in HTML. As a result, I wasn't able to properly communicate what I wanted to say. The symptoms I'm experiencing are as follows: With the following settings, the "signing certificate" status in Xcode shows as failed. <key>IOPCIPrimaryMatch</key> <string>0x00001916&amp;0x0000FFFF</string> The error message is as follows: doesn't include the com.apple.developer.driverkit.allow-any-userclient-access entitlement and doesn't match the entitlements file's value for the com.apple.developer.driverkit.transport.pci entitlement. With the following settings, the "signing certificate" status error in Xcode disappears, and building and driver installation succeed. However, the driver cannot be assigned to the device. <key>IOPCIPrimaryMatch</key> <string>0x00001916&0x0000FFFF</string> To check for any minor errors in my work, I reverted to a "sign to run locally" environment and tried the following values. All errors disappeared, and my drivers and software worked correctly. <key>IOPCIPrimaryMatch</key> <string>0x00001916&amp;0x0000FFFF</string> What I wanted to convey in my previous post was that I think I should include this "amp;", but when I do, the "signing certificate" status in Xcode shows as failed. Why is that? I tried the values ​​you provided, and the problem was exactly the same as before, so I'd really appreciate an answer.