Open danoli3 opened 5 months ago
Currently all the static binaries within the framework are signed via:
XCFRAMEWORK_PATH="${LIBS_DIR_REAL}/${1}/lib/${TYPE}/$1.xcframework"
# Loop over each .a file found within the xcframework
find "$XCFRAMEWORK_PATH" -type f -name "*.a" | while read -r lib_a; do
echo "Securing $lib_a..."
lipo -info "$lib_a"
xcrun codesign --sign - "$lib_a" || true
. "$SECURE_SCRIPT"
secure "$lib_a" "$VERSION" "$DEFINES"
done
This method, and this is mostly okay however this is the error in the Super Mega Multiplatform Workplace project I'm building for macOS:
And these errors do go away once accepting unsigned xcframework.
Also just for Sanity, again. This does not occur in any of the current Xcode Projects just the new one
Looks like we need Apple Developer / Distribution Signing @ofTheo
https://developer.apple.com/documentation/xcode/creating-a-multi-platform-binary-framework-bundle
This is only required for when using Multiplatform Target it seems however best to get this sorted now!
Current PR xcframeworks no issues. Best we set this up though! Here's some guides
Changes can be made once added to Apothecary. Refer to Project Generator - https://github.com/openframeworks/projectGenerator/tree/master/scripts
Or guide: https://localazy.com/blog/how-to-automatically-sign-macos-apps-using-github-actions
Then add to actions workflow when needed:
I would recommend making a new signing cert for Distribution and Developer so we can test both for these binaries. Again this is just to validate to developers we built it here, its signed from here, and to our best ability is the most secure it can be :)