Catalina has been released...

Fortune

Hello,

Now the day has come, macOS Catalina public has just been released.

Have anybody successfully manage to notarize installers?

It will be also useful to share our experiences with Catalina here.

orange

@Fortune This is my experience;

I created a .pkg installer with Whitebox Packages 1.2.6. I signed it with "productsign" and made the notarization of it in macOS Mojave 10.14.6 (XCode 10.3). Apple email says notarization is successful but when I check on Terminal, it was being rejected.
Then I updated to Catalina today, and Notarization of the same .pkg file seems successful in Catalina. When I check, it accepts. It is weird, but it looks ok for now.

I hope there won't be any problem in the future.

Natan

Hello @orange
What About The VST Plugins That Doesn't Have A Pkg Installer, And Only Available As Somthing.Component, Like Maize Generated Ones?

orange

@Natanr

For plugins, you only need to sign them digitally with Apple Developer ID ($99/year). Actually, you can't notarize plugins. But if you don't sign the plugins, they won't load in the DAW. (mabe they can work in Catalina first release, but not for the further updates). By the way I don't know if Maize Sampler is digitally signing plugins or not while exporting.

Notarization requirment is only for the apps that need "double-click" actions. So if you want to distribute your plugins with an installer (.pkg), or disc image (.dmg); this files must be noterized.

clumsybear

@orange

Do you need to sign via Apple Developer account in any case you distribute something for macOS or just for apps and audio unit plugins?

As I understand notarisation is required if I want to provide an installer or even a DMG, right? Are we talking about commercial products or is this the case for GPL licensed, freeware as well?

any guidelines or FAQ you can point me to?

arminh

@orange @clumsybear i installed catalina and build some fx vst and it work in S1, I must check AU In logic

orange

@clumsybear said in Catalina has been released...:

@orange

Do you need to sign via Apple Developer account in any case you distribute something for macOS or just for apps and audio unit plugins?

Signing covers all of the plugins, not only au plugins. Also signing plugins is not a new thing, most of the developers already have been signing their plugins and installers (vst/vat3/au/aax) for years. Notarization is a new requirment. Also from this macOS release, all of the requirments will be more important because of the Hardened Runtime.

As I understand notarisation is required if I want to provide an installer or even a DMG, right? Are we talking about commercial products or is this the case for GPL licensed, freeware as well?

I am not sure about free software but if we think about the philosophie of the notrization for Apple is about the security (malware, cracked software...etc) So free plugins should be signed at least.

d.healey

@clumsybear

is this the case for GPL licensed, freeware as well?

And GPL licensed commercial plugins too ;)

Natan

@orange Thank You Orange

As You Mentioned Above, You Already Updated Your OS to Catalina, If Possible , Do A Trial, And Bring Some Light Over The Components Only.

I Mean, Just Export A Plugin With Hise, And Try To Load It In Your DAW!
Maize Only Exports The .Components or .VST's And You Can Use The VST With A Simple Drag And Drop. No Need For Any .Pkg Or Third-Party Installers

Thanks Mate

Natan

Any Updates?

d.healey

If I build a plugin on Catalina (not that I intend to) will it also work on Mojave? And if I build one on Mojave will it work on Catalina?

orange

@d-healey said in Catalina has been released...:

If I build a plugin on Catalina (not that I intend to) will it also work on Mojave? And if I build one on Mojave will it work on Catalina?

Acording to Apple, for now, the answer of the both questions, Yes.

But since future macOS releases/updates won't support 32bit anymore, maybe 32/64 bit universal binary plugins (that was built in older macOS versions) couldn't work in the latest macOS releases. - By the way, in Catalina 32 bit only plugins don't work. Interestingly, 32/64 bit combined plugins work.

d.healey

@orange I only release 64bit anyway so that part isn't an issue. Glad to know I can just carry on as I have been (with the additional notarization crap)

Lindon

@orange - I think the answer to this part of Dave question is: "maybe"

"And if I build one on Mojave will it work on Catalina?"

tomekslesicki

Just to be sure - if I don't have an Apple Developer ID, Hise-based instruments won't work on Catalina until I sign them?

orange

@tomekslesicki For now, it is working. But acording to Apple you need to sign everything. And non-signed plugins won't work anymore in the next updates.

So I suggest signing your plugins if you don't want your users return back and say "hey my plugin doesn't work anymore".

tomekslesicki

Thanks @orange !

ustk

So I imagine that we need to sign Hise as well right?
Is there no issues, I mean, with many devs signing the same app?

Interesting thread:
https://forum.juce.com/t/confusion-on-catalina-notarization-hardened-run-time-no-changes-needed-after-all/35850/5

SampleScience

Maize Sampler recently signed/notarized its main application so the plugins created with it are Catalina ready. How do I make sure my Hise Sampler made plugins are compatible with Catalina? Is there a step by step guide on how to do it?

SampleScience

@orange said in Catalina has been released...:

For plugins, you only need to sign them digitally with Apple Developer ID ($99/year). Actually, you can't notarize plugins. But if you don't sign the plugins, they won't load in the DAW. (mabe they can work in Catalina first release, but not for the further updates). By the way I don't know if Maize Sampler is digitally signing plugins or not while exporting.

It is now with the new version. How do I sign my Hise Sampler plugins?

Catalina has been released...

55

1.7k

11.7k

101.8k