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

[Dan Korneff]

that's the same code I'm using. Only difference is I'm signing the pkg made with Packages, not the .component file.
My .component file is signed and wrapped with Pace.

[Lindon]

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

that's the same code I'm using. Only difference is I'm signing the pkg made with Packages, not the .component file.
My .component file is signed and wrapped with Pace.

I'm not talking about plugins - which I can code sign - I'm talking about stand alone applications - apps.

[Lindon]

Bump, anyone built stand alone apps for MacOS and then codesigned and notarized them?

[Dan Korneff]

Gonna investigate right now

[Dan Korneff]

I just codesigned an APP using the same code. No issues here. Do you have a minimal snippit you could post so I can see if it works here?

[Lindon]

@dustbro really no I dont - its a pretty big app...I could send you the app and you could see if you can codesign it?

[Dan Korneff]

@Lindon Sure!

[hisefilo]

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

, anyone built stand alone apps for MacOS and then codesigned and notarized them?

I did. no issues. same procedure as .vst or .component

where are u stuck?

[Lindon]

@hisefilo read the first post...

[hisefilo]

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

read the first post..

have you ever successfully signed any .app ??

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