Codesigning and Noterizing --- enter at your own risk....

[Lindon]

@hisefilo said in Codesigning and Noterizing --- enter at your own risk....:

@Lindon said in Codesigning and Noterizing --- enter at your own risk....:

read the first post..

have you ever successfully signed any .app ??

nope...

[hisefilo]

@Lindon then I recommend you to compile and sign any simple .app made on Hise or just some other you already compiled. Run this and post the output

codesign --deep --force --options runtime --sign "Developer ID Application: YOUR ID NAME  (YOUR TEAM ID - SOMETHING LIKE 2349FR983UQIWEUR)" [path to .app file]

[Lindon]

OK more exploration, and I have my problem/solution - actually my solution is to ask Apple "What the ****?"

If you get the error message I outlined in my first post....

So this has NOTHING to do with HISE....

It seems to only occur when you have modified the icon that the app uses: right click on the app, select Get Info, click the app image, paste in some other jpeg

-- if you do this (in order that your Mac App looks nice) - then it WONT codesign.... you have to have the base default iconography in your app.

So :

Apple: What the **** were you thinking?

Now on to attempting to notarize...

[Dan Korneff]

@Lindon Glad you finally figure it out!

[ustk]

@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?

[Lindon]

@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 if I put it in the images folder in my project how does HISE know which image is the one to use for the app?

[ustk]

@Lindon You just name it icon.png and Hise does the rest ;)

[Lindon]

@ustk said in Codesigning and Noterizing --- enter at your own risk....:

@Lindon You just name it icon.png and Hise does the rest ;)

Cool - didnt know that.

[Christoph Hart]

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...

[Lindon]

@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)

[Dan Korneff]

@Lindon said in Codesigning and Noterizing --- enter at your own risk....:

not aiming at iOS (yet)

That's my next goal

[arminh]

This post is deleted!

[arminh]

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?

[Dan Korneff]

@arminh I'm signing my plugins, and signing/notarizing the installer.

[Lindon]

@arminh a lot like @dustbro says -

as a general guideline.

1. You need to codesign everything (and theres more than one way to do that..hang on)
2. 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:

1. build all the plugins (VST and AU) and the stand-alone app for MacOS.
2. codesign all of them
3. Noterize the stand alone app
4. Set up whitebox packages to use my developer certificate
5. build the package (that includes the stand-alone app and the plugins)
6. noterize the package
7. staple the package
   8.. upload to server...

[arminh]

@Lindon thanks a lot! BTW i found great app for codesign - Hancock
Download here https://github.com/JeremyAgost/Hancock/releases

[Lindon]

@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.

[Natan]

@arminh How It Works?

[marcLab]

@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.

[Natan]

@marcLab
Thanks Mate

Could 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