Codesigning and Noterizing --- enter at your own risk....
-
@Christoph-Hart said in Codesigning and Noterizing --- enter at your own risk....:
There was an issue with iOS that rejected image files with existing EXIF data and you have to strip these before exporting but not sure if this is also the case here...
nope - not aiming at iOS (yet)
HISE Development for hire.
www.channelrobot.com -
@Lindon said in Codesigning and Noterizing --- enter at your own risk....:
not aiming at iOS (yet)
That's my next goal
-
This post is deleted! -
Maybe you guys can reply to my question. I want notorize vst plugin which i put inside pkg which will be part of DMG file. And now i have question. I must codesign and notorize every single file or i can pack everything to dmg and then just notorize and codesign this image file?
-
@arminh I'm signing my plugins, and signing/notarizing the installer.
-
@arminh a lot like @dustbro says -
as a general guideline.
- You need to codesign everything (and theres more than one way to do that..hang on)
- You need to noterize everything that will run alone - so your installer/package and any stand-alone MacOS apps you have written(not the plug-ins!)
so codesigning...
you have to do all of everything - but - if you are using whitebox packages then you can point it at your developer certificate and it (sorta) codesigns itself..
So I am using whitebox packager and I have stand alone apps in my download.. so:
- build all the plugins (VST and AU) and the stand-alone app for MacOS.
- codesign all of them
- Noterize the stand alone app
- Set up whitebox packages to use my developer certificate
- build the package (that includes the stand-alone app and the plugins)
- noterize the package
- staple the package
8.. upload to server...
-
@Lindon thanks a lot! BTW i found great app for codesign - Hancock
Download here https://github.com/JeremyAgost/Hancock/releases -
@ustk said in Codesigning and Noterizing --- enter at your own risk....:
@Lindon Have you tried to put the icon in the image folder so it is embedded right at compile time, and not manually as you described?
OK so I tried this today --- and STILL filled with fail - so this isnt a solution at all sadly.
-
@arminh How It Works?
-
@Lindon Hey my process for codesigning is :
codesign -s "Developer ID Application: ****** (*******)" -v ABSOLUTE_FILE_PATH;
then I compress the file and codesign the compressed file.
codesign -s "Developer ID Application: ****** (*******)" -v ABSOLUTE_FILE_PATH.zip;
It will then be ready for notarizing.
-
@marcLab
Thanks MateCould You Do A Video Tutorial So We Can Get The Whole Process More Clearly?
Or Posting Some Gif's And Step By Steps
Thank You -
@Natanr Absolutely! I'll find some spare time to do this as soon as possible
-
@marcLab Thanks Mark
This Will Help Lot To Get Through The Process Confidentially -
@marcLab then your process is not much different from mine, but have you found a way to change the app icon(read the post from 12th May..)?
-
Hi Guys! since @d-healey has created the Hise-Exporter, for any vst-au-standalone I make, it needs to be codesigned and notorized to share it with you guys (If you want) and friends .
Since I cannot be able to enroll to the membership and have the Apple Team ID, is there a way to codesign and Notorize in Hise without the Apple Team ID please? Thanks Guys, Almost finished with my vst.
Cant wait to share it with you guys!!
-
@nesta99
is there a way to codesign and Notorize in Hise without the Apple Team ID please?
Codesign, yes. You can self certify (I don't know anything about it though).
Notarize, no.
Share with us, sure, you don't need to codesign or notarize to do that. -
@d-healey Thanks. But then why the moment I export, my daw does not see it?
I can't figure out the mistake. I'm stuck. -
@nesta99 Maybe your DAW will only let you use notarized plugins.
