Notarisation for dummies
-
steps 3,4 and 5 are pretty redundant I think - I never do these.
-
@Lindon Are there any steps that I missed or did I get the wrong certificates? there is nothing to modify in the certificates? I'm almost there, I'm only missing this phase ^^
-
@yall you dont need any certificates to codesign your plugins.
You need a Developer install certificate for whitebox packages to allow the install to happen correctly.
HISE Development for hire.
www.channelrobot.com -
@yall said in Notarisation for dummies:
codesign -s "Developer ID Application: myname (mycode)" "/Users/macmini/Desktop/myplugin.component" --timestamp
this looks slightly odd from my perspective:
codesign -s "Developer ID Application: myname (mycode)" "/Users/macmini/Desktop/myplugin.component" --timestamp
I always uses a specific user so not "/Users/macmini/Desktop"
but "<username>/Desktop" etc..
-
@Lindon said in Notarisation for dummies:
@yall you dont need any certificates to codesign your plugins.
Pretty sure you do. But you only need to install it into the keyring once and then never touch it again.
-
-
I just tried something. I have re-exported a new plugin and followed my steps. the plugin is now signed, the pkg too. but the notarization failed again.
-
-
@d-healey I cannot record the screen in video with my mac I do not have video editing software here.
I have no error in the terminal but simply an email from apple telling me, your application has not been notarized.I went back to the pakage application (whitebox) to affix the certificate to try, but it said to me: There is no private key associated with the certificate.
frankly I really don't understand anything and it's not that simple -
@yall You can screen record with Quicktime fyi
-
@DanH I can't because I have to blur some information you understand ^^
-
@yall - re whitebox, are you attempting to attach the correct certificate type? You need a Developer installer certicficate - once its attached to whitebox (and your whitebox project) you will see a certificate emblem in your interface (top right - black badge)
-
@Lindon yes I had already noticed the small label which somehow validates. but strangely, it is impossible for me to affix a certificate. I have the following response from whitebox>
The "Developer ID Installer: myname (7 *********)" certificate available in the keychain cannot be used to sign a package or a distribution. There is no private key associated with the certificate .
-
-
@yall you probably need to staple it first
-
-
@d-healey I cannot staple the .zip. I sent it to my beta tester. so good news my plugin is displayed as verified in the list of plugins (logic). but impossible to open it. to put it simply, logic recognizes it but when you want to create a new instrument on a track, my plugin does not exist
-
@yall = Logic is probably not the first DAW you want to try this in...
You have a unique plug-in ID assigned?
-
@Lindon what do you call assigned plugin id? so precisely if it works on logic it will work everywhere ^^ I came back to the pkg problem. it is not possible for me to affix the certificate. it tells me that it cannot be used to sign a package or distribution because there is no associated private key. this story of notarization sincerely is really a crazy thing
-
Try this out:
Hise Export plugins > Sign plugins > Build installer > Sign installer > Notarize installer > Time stamp installer.
If this doesn't fix, I recommend you to hire a mobile notary public. They can fix your issue in no time.
