@orange - cool. I will add these to my process...

@Christoph-Hart

Ok heres my process:
Step 0. build your app and plugins...

Step 1: Sign the plugin or app from desktop (copy it there):

run these commands in the terminal window:

codesign -s "Developer ID Application: your-dev-id (your-dev-id-number)" "/Users/lindon/Desktop/your.component" --timestamp

codesign -s "Developer ID Application: your-dev-id (your-dev-id-number)" "/Users/lindon/Desktop/your.vst" --timestamp
codesign -s "Developer ID Application: your-dev-id (your-dev-id-number)" "/Users/lindon/Desktop/your.vst3" --timestamp
codesign --deep --force --options runtime --sign "Developer ID Application: your-dev-id (your-dev-id-number)" "/Users/lindon/Desktop/your.app"

Validate that the code signing has happened:

codesign -vvv /Users/lindon/Desktop/yourvst.vst

Step 2: Make the installer package & Sign the package from desktop - note my white box has my dev installer certificate attached..(copy it there):

codesign -s "Developer ID Application: your-dev-id (your-dev-id-number)" "/Users/lindon/Desktop/your.pkg"

Step 3: notarize your package it should notarize your app at the same time......

—NOTE: YOU MUST TYPE THIS INTO THE TERMINAL BY HAND - IT WONT WORK CUT AND PASTE FOR ME!!!!!

xcrun altool --notarize-app -f "/Users/lindon/Desktop/your.pkg” --primary-bundle-id com.your.pkg --username "your-apple-id-NOT-your-dev_id" --password "your-altool-password"

Step 4: Wait for email from apple…

on success notification, staple your package:

xcrun stapler staple "/Users/lindon/Desktop/your.pkg"

Step 5:check if package has been signed…
codesign -vvv --deep --strict "/Users/lindon/Desktop/your.pkg”

OK this all works fine - except!!! - If I add an icon to the app after its been built then it will NOT notarize giving you the ever helpful message:

unsealed contents present in the bundle root

As yet I havent tried to notarize an app that has used the Icon.png-in-the-images-folder approach..

@andioak -- no don't do this. Inserting your own icons in a mac build will cause it to fail to notarize (well that's my experience anyway,,).

Can anyone confirm that using the "Icon.png method" produces a stand alone that will pass notarization?

@BWSounds said in Just want to see where im at..:

@d-healey
Yep it compiled and open!

@Lindon
so my next question is how do you rebuild samplemaps?

Do I add everything all over again?

Sadly yes I had to redo all the sample maps from scratch - luckily for me there were only 60+ to do...

But Like Dave says -- first build a version that loads only 1 sample map - and redo that one and see if you get the same problems.

I ended up building numerous versions -- basically recompiling every ten sample maps or so - it was tedious in the extreme...

@BWSounds well I've been here recently ---- the plugin would compile BUT reaper would tell me it wasnt valid and would reject it and pluginval would crash as soon as it tried to open the plugin.

Turns out there was something (heaven knows what) wrong with one of my samplemaps. I rebuilt them all and it works flawlessly... perhaps its that?

@ustk codesign = "works in a DAW", Notarize = "works as a standalone"

@Lunacy-Audio cool..

@ustk great. Well done. Can you let us know when its included.

It would seem that the MIDI Sources panel uses a default toggle button to represent the selected device - in a way that the MIDI Channel List doesnt....

So when I laf my toggle buttons to do what I want - it breaks the MIDI Sources panel...

see the "button" next to KeyLab 49....

Adendum - laf also seems to break the Custom Settings too - meaning they wont show up correctly...

@d-healey - what does your SDK folder look like?

--oops - didnt read further - you have a solution