As master was recently updated to JUCE 6.1.3, I was trying to build a few things with that new version, and I noticed the following:
(1) When I run my release script after the build (to prepare all binaries, manual, presets, etc… and create my installer package), I am now getting these warnings:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/strip: warning: changes being made to the file will invalidate the code signature in: /Users/ktanghe/Documents/Code/SampleSumo/KTSoundProjects/SoundProjects/Applications/Plugins/SaltyGrain/Builds/MacOSX/build/Release/SaltyGrain.component/Contents/MacOS/SaltyGrain (for architecture x86_64)
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/strip: warning: changes being made to the file will invalidate the code signature in: /Users/ktanghe/Documents/Code/SampleSumo/KTSoundProjects/SoundProjects/Applications/Plugins/SaltyGrain/Builds/MacOSX/build/Release/SaltyGrain.component/Contents/MacOS/SaltyGrain (for architecture arm64)
This happens when my release script does this:
xcrun strip -S -x “$AUBinary”
So I symbol-strip the binaries, then do a few things, and then later in the script I sign them with codesign.
This used to work fine in 6.1.2 without these warnings, and it looks like for some reason the Xcode project is now set to sign my binaries (I can see a line “Sign SaltyGrain.component 0.1 seconds” in the build log), whereas it wasn’t before the update to JUCE 6.1.3.
In the Projucer, the “Code-Signing Identity” is still empty (and I actually didn’t change anything to the .jucer setup file, I only opened it and re-saved the project in the newly built Projucer).
(2) I also noticed that the AAX build also seems to get signed now (“Sign SaltyGrain.aaxplugin 0.1 seconds” in the build log), and that happens after the post-build script, in which I call wraptool for the AAX target of my plugin. Doesn’t this break the wraptool signing now?