Merge pull request #12 from docsforadobe/users/colombo/signing-updating

Improve instructions and guidance around signing

Author: zlovatt

docs/intro/apple-silicon-support.md

@@ -5,10 +5,12 @@ Adobe now supports Apple Silicon effect plugins in some products running nativel
 Not all Adobe products have native Apple Silicon versions yet, but in those that do, only effect plugins with Apple Silicon implementations will be available. We recommend adding the Apple Silicon target soon in anticipation of rapid adoption of these new M1 machines.
 
 !!! note
-    In order to build a Mac Universal binary, you will need Xcode 12.2 or greater. Adobe is currently using Xcode 12.4.
+    In order to build a Mac Universal binary, you will need Xcode 12.2 or greater.
 
 To learn more about Universal binaries, please visit [https://developer.apple.com/documentation/apple-silicon/building-a-universal-macos-binary](https://developer.apple.com/documentation/apple-silicon/building-a-universal-macos-binary)
 
+Loading plugins on macOS 15+ for debugging also requires an additional signing step. See [here](debugging-plug-ins.md#signing-requirments-and-loading-unsigned-plug-ins) for details.
+
 ---
 
 ## How to add Universal Binary Support for your Plugins

docs/intro/debugging-plug-ins.md

@@ -4,21 +4,31 @@ The best way to learn the interaction(s) between After Effects and plug-ins is r
 
 Once you've got the plug-in building directly into the plug-ins folder as explained above, here's how to specify After Effects as the application to run during debug sessions:
 
-### Windows:
+### Windows
 
 1. In the Visual Studio solution, in the Solution Explorer panel, choose the project you want to debug
 2. Right-click it and choose Set as StartUp Project
 3. Right-click it again and choose Properties
 4. In Configuration Properties > Debugging > Command, provide the path to the executable file of the host application the plug-ins will be running in (this may be After Effects or Premiere Pro)
 5. From there you can either hit the Play button, or you can launch the application and later at any point choose Debug > Attach to Process...
 
-### macOS:
+### macOS
 
 1. In Xcode, in the Project Navigator, choose the xcodeproj you want to debug
 2. Choose Product > Scheme > Edit Scheme...
 3. Under Run, in the Info tab, for Executable, choose the host application the plug-ins will be running in (this may be After Effects or Premiere Pro)
 4. From there you can either hit the Play button to build and run the current scheme, or you can launch the application and later at any point choose Debug > Attach to Process.
 
+#### Signing requirments and loading unsigned plug-ins
+
+macOS versions 15+ prevent the loading of unsigned plugins. During development, you can avoid this difficulty by adding ad-hoc signing as a custom build step.
+
+`codesign --force --deep --sign - /path/to/plugin.dylib`
+
+Note: Yes, that trailing '-' after '--sign' is important.
+
+When you are ready to release, ensure that you do _not_ make changes to the plug-in package after signing, as this will invalidate said signing and prevent the plug-in from loading.
+
 ---
 
 ## Deleting Preferences