Posts

Post not yet marked as solved
5 Replies
Hi,we do have a similar problem on that. First I do get the same error message. Anyway regarding your answer I will try to sign the whole zip that we are delivering our framework to our customers for macOS applications. We do package also iOS Framework, Windows etc. libraries etc in our zip. How does this affect the stapling process?In a second case we do also deliver a .unitypackage - which is a somehow special tar format that includes our dynamic library named as a libXXX.bundle for beeing used as a plugin for the creation of mac apps and beeing used in the unity editor. We already deliver it signed. Anyway our customers claim that they have to create a security exception when creating a new project with our library inside. I was already able to notarize the libXXX.bundle file sucessfully. Anyway how would I accomplish stapling the whole archeive before deploying it. Or would I need to rely at least to the fact that the user is connected to the internet for verification?Thanks and best regards