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

[Lindon]

OK so I'm trying to codesign (not got to notorizing yet) an AU plugin and a standalone app.

lets just take the app first , apparently this is sorta what you need to run

codesign --deep --force --options runtime --sign "Developer ID Application: Your Name" "Application.app"

when I run this codesign (cryptically as usual) tells me:

unsealed contents present in the bundle root

Has anyone got a repeatable way to codesign mac apps built using HISE?

[d.healey]

This is the build script Christoph sent me a couple of years ago. It has some codesigning stuff which I haven't tested yet but I expect it will work...

[Lindon]

@d-healey OK thanks but whihc of these two commands is correct?

codesign -s "$APPLE_CERTIFICATE_ID" "$standalone_project"
codesign -dv --verbose=4 "$standalone_project"

[Lindon]

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

@d-healey OK thanks but whihc of these two commands is correct?

codesign -s "$APPLE_CERTIFICATE_ID" "$standalone_project"
codesign -dv --verbose=4 "$standalone_project"

sorta answering this myself.. so the first is supposed to code sign and the second tell you that it is... @d-healey if you are hoping this will work - I think you are in for a disappointment.....fails in exactly the way described above.

No surprises really the codesigning requirements have moved on even over the last couple of months - you will need the --timestamp flag in there in any case...

[d.healey]

A quick google indicates that unsealed contents present in the bundle root is a common issue, so I don't think there is necessarily anything wrong with the command you've been using.

[Lindon]

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

A quick google indicates that unsealed contents present in the bundle root is a common issue, so I don't think there is necessarily anything wrong with the command you've been using.

yes I did the same google search before I came here...but the fix is less than helpful..Apple say:

...if a bundle has a Contents or Versions directory at its top level, there may be no other files or directories alongside them. The one exception is that alongside Versions, there may be symlinks to files in Versions/Current.

SO either we have to find a codesign command work around - or HISE has to build apps in a different way.

[Dan Korneff]

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

as anyone got a repeatable way to codesign mac apps built using HISE?

I've signed my AU plugs made in HISE without any issues. Lemme check my code and see if anything differs from yours.

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