I'm trying to deploy to a company. Therefore, it is distributed using the Developer ID. Please refer to the inquiry below. This is my current situation. https://developer.apple.com/forums/thread/700227

To deploy, I use various functions of App id of Identifiers (Extension , Endpoint-security etc). However, when I try to deploy through Developer ID through the archive in Xcode, I always get an error because the provisioning file does not match. Please tell me how to solve it

When we get an answer, we will share it with each other by commenting on the thread.

Yes I still haven't solved this problem. Do you know how?

Yep that's right I asked the same question. But the problem still occurs. I've tried it as an account owner and as an administrator, but they all have the same symptoms.

I've been trying a lot to fix the issue where the certificate is not showing up and I've been to a lot of sites. Also, it turns out that other people besides me also have this problem. https://stackoverflow.com/questions/71100475/macos-unable-to-create-provisioning-profile-to-distribute-outside-the-mac-app

In order to sign using your Developer ID, you need to create a provisioning file for it, right? Naturally, I proceeded as follows to create a custom provisioning on the developer site with the provisioning file. MAC PC Create .CSR Generate certificate Account -> Certificates, Identifiers & Profiles -> Certificates -> Add -> Option: Software(Developer ID Application) -> Attach and create .CSR created on MAC PC Create provisioning file Account -> Certificates, Identifiers & Profiles -> Profile -> Add -> Option: Distribution(Developer ID) -> Enter the Bundle ID and the following screen will be displayed. I created the certificate, but it says it doesn't exist. Why is this? Also, my MAC PC logged in is not the owner id of the Apple Developer site and I have the admin role in it. In other words Apple Developer Site Account: A My MAC login account: B

Feel free to ignore the comments I left above. The case is an error with the extension app, and it is considered normal, not an error with the actual app. I also encountered the following problem: I've read all the documentation to fix the issue, but I can't confirm any idea why this is happening? Case 1 I had an existing Apple Development signed app for distribution. Command : codesign -dvvv --entitlements - /Users/MyUserID/Desktop/release/SystemExtensions.app Command : codesign -dvvv --entitlements - /Users/MyUserID/Desktop/release/SystemExtensions.app/Contents/Library/SystemExtensions/My.Domain.SystemExtensions.Extension.systemextension Command : security cms -D -i /Users/MyUserID/Desktop/release/SystemExtensions.app/Contents/embedded.provisionprofile Command : security cms -D -i /Users/MyUserID/Desktop/release/SystemExtensions.app/Contents/Library/SystemExtensions/My.Domain.SystemExtensions.Extension.systemextension/Contents/embedded.provisionprofile However, in order to distribute the app, as mentioned above, you must sign with Developer ID Applications to avoid being blocked by the gatekeeper. Therefore, I re-signed, and the result of code signing is as follows. Command : codesign -s "Developer ID Application: My Team (Team_id)" --options=runtime --force /Users/MyUserID/Desktop/release/SystemExtensions.app/Contents/Library/SystemExtensions/My.Domain.SystemExtensions.Extension.systemextension Command : codesign -s "Developer ID Application: My Team (Team_id)" --options=runtime --force /Users/MyUserID/Desktop/release/SystemExtensions.app Command : codesign -dvvv --entitlements - /Users/MyUserID/Desktop/release/SystemExtensions.app Command : codesign -dvvv --entitlements - /Users/MyUserID/Desktop/release/SystemExtensions.app/Contents/Library/SystemExtensions/My.Domain.SystemExtensions.Extension.systemextension embedded.provisionprofile properties are the same as before sign. And when I run the app, the following error occurs. Also, the square red box is the log being taken by my app. What could be causing this error? Was it my fault? ======================================================================================= Case 2 As I saw in Case 1, the entitlement property before and after signing is different, so when re-signing, I put the --preserve-metadata=entitlements option to bring the entitlement property as it is. Command : codesign -dvvv --entitlements - /Users/MyUserID/Desktop/release/SystemExtensions.app Command : codesign -dvvv --entitlements - /Users/MyUserID/Desktop/release/SystemExtensions.app/Contents/Library/SystemExtensions/My.Domain.SystemExtensions.Extension.systemextension Command : security cms -D -i /Users/MyUserID/Desktop/release/SystemExtensions.app/Contents/embedded.provisionprofile Command : security cms -D -i /Users/MyUserID/Desktop/release/SystemExtensions.app/Contents/Library/SystemExtensions/My.Domain.SystemExtensions.Extension.systemextension/Contents/embedded.provisionprofile Command : codesign --preserve-metadata=entitlements --force --verbose -s "Developer ID Application: My Team (Team_id)" --options=runtime --force /Users/MyUserID/Desktop/release/SystemExtensions.app/Contents/Library/SystemExtensions/My.Domain.SystemExtensions.Extension.systemextension Command : codesign --preserve-metadata=entitlements --force --verbose -s "Developer ID Application: My Team (Team_id)" --options=runtime --force /Users/MyUserID/Desktop/release/SystemExtensions.app After that, if you check the information, you can see that everything is normal as shown below. Command : codesign -dvvv --entitlements - /Users/MyUserID/Desktop/release/SystemExtensions.app Command : codesign -dvvv --entitlements - /Users/MyUserID/Desktop/release/SystemExtensions.app/Contents/Library/SystemExtensions/My.Domain.SystemExtensions.Extension.systemextension embedded.provisionprofile properties are the same as before sign. Then, when you run it, an error different from Case1 is displayed as shown below.