Mac Export - arm64 unidentified symbols

[trillbilly]

@lindon Ok, cool, thank you! Im going to read through this a bit and see what the deal is. Im sure I will be back lol

[Lindon]

@trillbilly said in Mac Export - arm64 unidentified symbols:

@lindon Ok, cool, thank you! Im going to read through this a bit and see what the deal is. Im sure I will be back lol

yeah its a bit confusing - but most of it is people struggling with their implementation - and Apple moving the requirements - its quite an old thread ...and Apple changed a few things at different points in the process - annoyingly...

[trillbilly]

@lindon Ya, there's a lot going on in the thread lol. I'm trying to dig through and decipher what I need. Ill be here for a while.

If you get to your Mac and are able to expedite my process, it would be greatly appreciated!

Just to be clear on the codesigning...

1. There is nothing I need to download in order to use this via the Terminal, correct?

2. The codesigning can be done without being App Developer (since Im creating products that do not use installer)?

[d.healey]

@trillbilly said in Mac Export - arm64 unidentified symbols:

Ya, there's a lot going on in the thread

You only need the first post.

[trillbilly]

@d-healey Ok, cool. According to that the Apple Developer ID is required, which is no biggy. Ill be trying to sign a plugin shortly. Thanks

[Lindon]

@trillbilly - yes, sorry if I gave you the impression you didnt need a developer ID - you do - to codesign stuff, but not to sell stuff..

So I'm at the Mac...so....

1. copy your plugins to the desktop (not strictly required but it makes everything a lot simpler)
2. open a terminal window...
3. type this:

codesign -s "Developer ID Application: ()" "/Users//Desktop/XXX.vst" --timestamp

so an example might be:

codesign -s "Developer ID Application: Alan Smith (1234AB4FDG)" "/Users/alan/Desktop/coolplugin.vst" --timestamp

4. hit enter and wait .....in a few moments you will be told it was successful - most errors are in the typing - make sure you include the quotes in the correct places...

To test it worked type this into the terminal window:

codesign -vvv /Users//Desktop/XXX.vst3

repeat replacing XXX.vst with XXX.component

Now you will have a couple of codesigned plugins - copy from the desktop to the correct plugin folders...

[trillbilly]

@lindon Awesome man, thanks! My daughter is home from Daycare today so I'm gonna be a little late getting to the studio today. When I get there, I'll throw this in the terminal and give it a go!

As for notarized, I can see it's a different process in the terminal. It looks like you need an auto generated password, which I believe you get from the Apple Developer Account, correct?

Just for my own sanity...

"Codesigning" is a stamp that let's Apple know the App is created by a trusted developer.

"Notarized" is ensuring the App doesn't have any virus, etc.

Are these the basic ideas of the two?

[Lindon]

@trillbilly said in Mac Export - arm64 unidentified symbols:

@lindon Awesome man, thanks! My daughter is home from Daycare today so I'm gonna be a little late getting to the studio today. When I get there, I'll throw this in the terminal and give it a go!

As for notarized, I can see it's a different process in the terminal. It looks like you need an auto generated password, which I believe you get from the Apple Developer Account, correct?

Just for my own sanity...

"Codesigning" is a stamp that let's Apple know the App is created by a trusted developer.

"Notarized" is ensuring the App doesn't have any virus, etc.

Are these the basic ideas of the two?

not quite...
DAWs should NOT open or even offer you access to non-codesigned plug-ins.

Notarizing is for stand alone applications - like a stand alone version of your product, or the installer/packager you give to users to set up your product, MacOS wont even run these stand-alones without them being notarized. All notarized products should be codesigned first, then notarized.

Dont even get me started on the Avid/PACE EDEN tool kit for AAX...

.

[trillbilly]

@lindon I'm not even concerned about AAX at the moment. As long as I can ensure VSTi and AU work and are compatible both Mac & Windows, I will be happy for the time being.

Thanks for the clarification. So in other words, if I'm not doing installers or a standalone app, which I'm doing neither, the notarization is useless and as long as the individual plugins are codesigned, they are good to go in Apples eyes?

[Lindon]

@trillbilly yep - no Notarizing needed.

[trillbilly]

@lindon said in Mac Export - arm64 unidentified symbols:

codesign -s "Developer ID Application: ()" "/Users//Desktop/XXX.vst" --timestamp

Hey man! So Im using this but getting an error like below:

error: The specified item could not be found in the keychain.

Here is my code from terminal:

codesign -s "Developer ID Application: My Name (My Number)" "/Users/mymac/Desktop/Blaque.vst3 " --timestamp

Do you spot any errors?I think I have everything in the correct place but apparently not.

[d.healey]

@trillbilly Have you added your credentials to the system keychain?

[trillbilly]

@d-healey yes, I used my account name & user ID # provided by my Apple Developer Account (I just didn't post those credentials on the forum). I also used the correct desktop path as I just dragged and dropped the VST in Terminal for this.

[d.healey]

@trillbilly said in Mac Export - arm64 unidentified symbols:

I used my account name & user ID # provided by my Apple Developer Account

Double check that your details are correct in the keychain - https://help.apple.com/xcode/mac/current/#/dev97211aeac

[trillbilly]

@d-healey ahhhh, I got you.

Apple Development, the gift that keeps on giving...

[Lindon]

@trillbilly and this:

/Users/mymac/Desktop/Blaque.vst3

is not the same as this:

/Users//Desktop/XXX.vst

unless your user name is mymac

[trillbilly]

@lindon unfortunately, mymac is the username lol. I just never changed it from what the used Mac store had made it.

I'll be back in the studio today and will get it down. Today is the day!

[trillbilly]

@lindon @d-healey Im generating certs now. I received this message after creating.

"Software Distribution Reminder
If you're generating your first Developer ID certificate, the software that you sign it with must be notarized by Apple in order to run on macOS 10.14.5 or later."

Earlier in the thread, it was mentioned notarization isn't needed for VSTs that are distributed with no installers and are not standalone apps, would this still be the case or is Apple adding a new step?

EDIT: I have also successfully code signed my VST3 & AU. Thanks Again!

Is it necessary to codesign HR1/Sample Files?

[d.healey]

@trillbilly said in Mac Export - arm64 unidentified symbols:

Is it necessary to codesign HR1/Sample Files?

No

[Lindon]

@trillbilly said in Mac Export - arm64 unidentified symbols:

@lindon @d-healey Im generating certs now. I received this message after creating.

"Software Distribution Reminder
If you're generating your first Developer ID certificate, the software that you sign it with must be notarized by Apple in order to run on macOS 10.14.5 or later."

Earlier in the thread, it was mentioned notarization isn't needed for VSTs that are distributed with no installers and are not standalone apps, would this still be the case or is Apple adding a new step?

EDIT: I have also successfully code signed my VST3 & AU. Thanks Again!

Is it necessary to codesign HR1/Sample Files?

Well thats Apple being, well Apple... welcome to being an Apple Developer: the land of moving goal posts and dodgy documentation.... you dont need to notarize anything that doesn't run stand alone....if it loads into a DAW then it needs codesigning that's all...