Ad Hoc Code Sign Error OSX

[DanH]

@matt_sf ok gotcha. Thanks loads for the help. Definitely more time consuming than using @d-healey 's app!!

If only we could find the issue...

[DanH]

@matt_sf are you on Mojave as well?

[Matt_SF]

@danh nope, catalina

[d.healey]

@danh said in Ad Hoc Code Sign Error OSX:

If only we could find the issue...

Probably a problem with the template generator in HISE, should be an easy fix

[DanH]

@d-healey As in it's setting the Runtime to the wrong setting?

[Matt_SF]

@danh I can't check it now but search for the setting here :

HISE/hi_backend/backend/ProjectTemplate.cpp
HISE/hi_backend/backend/StandaloneProjectTemplate.cpp

I'll try to test it tonight and see if it works

[Matt_SF]

@danh It couldn't be simpler : go into these files :

HISE/hi_backend/backend/ProjectTemplate.cpp
HISE/hi_backend/backend/StandaloneProjectTemplate.cpp

and search for hardenedRuntime=\"1\".

Change 1 to 0, recompile HISE and you're done, it's working just fine :thumbs_up:

[orange]

AFAIK, the Hardened Runtime is a must for the notarization. So disabling it isn't a good way to go.

There should be a fix without disabling it.

[Matt_SF]

@orange ok thanks for the info ! I'll try to notarize a plugin later to see what happens. If really this isn't the solution, we'll still be able to compile projects by loading the projucer file in xcode, so this is not a big issue.

[Matt_SF]

@orange

compile projects by loading the projucer file in xcode

Just thought that setting the value to 0 instead of 1 = setting the parameter to 'disabled' in the projucer file, so both solutions are the same. I'll take a look later

[DanH]

@matt_sf just tested. Making the changes you suggested works and notarizes ok. I used @d-healey's app to do so. Hopefully this fixes it :) :crossed_fingers:

[d.healey]

@orange I believe you can enable it during notarization but doing it during compilation makes xcode go funky.

[Lindon]

OK, So I'm getting this too now on :

HISE 14th Feb build
MacOS Mojave
Intel chip
XCode 10.2.1

..I will go set the flag... but I think it probably needs doing as a default...

[d.healey]

@lindon said in Ad Hoc Code Sign Error OSX:

but I think it probably needs doing as a default...

Yes I agree @Matt_SF can you make a pull request for this?

[orange]

@d-healey Apple says:

"To upload a macOS app to be notarized, you must enable the Hardened Runtime capability."

You can also read these:

Notarizing macOS software before distribution | Apple Developer Documentation

Give users even more confidence in your macOS software by submitting it to Apple for notarization.

Apple Developer Documentation (developer.apple.com)

Hardened Runtime | Apple Developer Documentation

Manage security protections and resource access for your macOS apps.

Apple Developer Documentation (developer.apple.com)

@danh said in Ad Hoc Code Sign Error OSX:

@matt_sf just tested. Making the changes you suggested works and notarizes ok.

Have you checked it on the computers of the other users? Does it pass the notarization in these computers too?

Also since it works, for now, it doesn't mean that you won't get any errors in the forthcoming macOS versions or on the other users. Because Apple suggests using the Hardened Runtime enabled.

[DanH]

@orange I might be wrong but isn't it the case that you can't notarize a component / vst. You notarize the .pkg that you supply them in.

[DanH]

@d-healey said in Ad Hoc Code Sign Error OSX:

can you make a pull request for this?

I'd perhaps urge caution - on Big Sur my other machine didn't have an issue, so this could potentially break on more recent versions of osx.

In fact why don't I test that now...

[orange]

@danh said in Ad Hoc Code Sign Error OSX:

@orange I might be wrong but isn't it the case that you can't notarize a component / vst. You notarize the .pkg that you supply them in.

The Hardened Runtime requirement is for the executables mainly. So standalone apps (exported from the Hise) will definately need it. But I believe that it could be needed for the plugins too.

[d.healey]

@orange You don't need to do it through XCode. If you codesign via the command line (which is what my app does) you can use --options runtime to enable the hardened runtime during signing.

[Matt_SF]

@danh said in Ad Hoc Code Sign Error OSX:

In fact why don't I test that now...

I'm not available right now, but if you want we can exchange test plugins this evening to see what happens...

EDIT : if that works I'll make a pull request