Mac Export - arm64 unidentified symbols

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

[trillbilly]

@lindon Awesome, thanks again, all the help is appreciated!

[trillbilly]

@d-healey Thanks! Your help and knowledge is always appreciated!

[Sawer]

Hello!
Trying to export An AU plugin but I'm having the same issue as @trillbilly


I tried to change the architecture to 64bit and uncheck the "Support 32 bit" option in Hise settings, but no result. Any idea please?

[d.healey]

@nesta99

[trillbilly]

@nesta99 You have to go back into the "Autogenerated Projucer" file and uncheck ARM in the Xcode Architectures. Then save and run in IDE to finish compile.

[Sawer]

@trillbilly @d-healey Thanks , sorted out. Now I’m dealing with Codesign / Notarization issue. My plugin can’t be visible on Logic . I have the developer account but still not working. Any thing I’m missing out?

[trillbilly]

@nesta99 I won't be back to the studio until Monday but I just had a post on it that a few people chimed in on. It's a bitch at first but once you get one done, it's easy.

Once I'm back to the studio I can post the directions again.

[Sawer]

@trillbilly Thanks so much man!