Notarization Apple
-
@orange I would like to clarify some things. What exactly am I replacing this data with?
codesign -s "Developer ID Application: Team Name (Team ID)" "/path/plugin.component" --timestamp
developer application ID?
team Name?
(team ID)?
between devloper account, apple account, I'm lost. I certainly did not do it right. the team id I know this is something like XHEIY67HDJJD from apple developer.
Yet it seems very simple but for the first time it is a bit messy all this for a noobs like me ^^ -
@yall You will find this in your Apple developer account. It'll look exactly like the example.
Awesome Plugin Company (W68FJJHBN) -
@yall said in Notarization Apple:
@orange I would like to clarify some things. What exactly am I replacing this data with?
codesign -s "Developer ID Application: Team Name (Team ID)" "/path/plugin.component" --timestamp
developer application ID?
team Name?
(team ID)?
between devloper account, apple account, I'm lost. I certainly did not do it right. the team id I know this is something like XHEIY67HDJJD from apple developer.
Yet it seems very simple but for the first time it is a bit messy all this for a noobs like me ^^Open the Keychain Access Utility and look at your certificates that you've just created.
For example, in below image
Developer ID Application : is just for describing the certificate type, no need to do anything for this.
Team Name: John Smith. It could be your company's name too.
Team ID: RNZ541ACLZAs you see, for signing, you need to use the same name of the certificate just like in the Keychain Access Utility. So acording to this example in the image, the AU plugin signing code will be like this:
codesign -s "Developer ID Application: John Smith (RNZ541ACLZ)" "/path/plugin.component" --timestampAlso be careful about spaces, letters...etc. in the code.
NOTE: If you can't see the both 2 certificates in the Keychain Access Utility, then it means that you didn't installed certificates properly. Then go to the begining and install the certificates properly.
-
@orange @dustbro @d-healey
hello, i haven't looked into notarization yet but something weird has happened to me. a friend who serves me as a beta tester, did not manage to open a vst in ableton because I sent him by we transfer directly to the compressed file format. my instrument.vst .that did not work . I sent it back as a pkg. and strangely enough it worked straight away without a problem. he is on bigsure. the plugin is therefore not notarized. is it a fluke or is it something logical? because if it works. why bother to notarize? his mac is from late 2013 with last bigsure update. I created a package with whitebox package. without entering my apple IDs expand -
@yall Are you sure he didn't just allow it past the gatekeeper when prompted?
-
@yall Sending a project as a raw .vst .aax or .component wont work with Wetransfer. It changes the file structure from a container into a folder (or... something like that). To maintain the properties, zip up the plugins before you send.
-
@d-healey I'm pretty sure he hasn't touched anything because he doesn't know anything about it ^^ however I gave him the .vst file I will try to give it a .componant even I was surprised! the first time he tried to drag the .vst in and the apple indicated that the developer was not verified. then he deleted the .vst. and installed with a simple pkg. and ableton took it straight. I will try to send him some fx and vst plugins of all kinds to be sure.
-
@dustbro I have always sent this way it never bothered. but suppose you are right. how is it possible that bigsure allows an unverified plugin? from what I know now it is imperative to notarize them?
-
imperative to notarize them?
If you notarize the package you don't need to notarize the plugin, but you still need to codesign both.
-
yes I understand, but in this case, nothing has been notarized or coded. I just took the .VST and created a pkg and that's it. That's why I find it weird.
