XCode discards Codesigning-Result of embedded Framework

Question

Created May ’21

Replies 1

Boosts 0

Participants 2

Sparkle.framework gets signed by an Archive pre-action script defined in my Release scheme:

Code Block LOCATION="${BUILT_PRODUCTS_DIR}"/"${FRAMEWORKS_FOLDER_PATH}"
codesign --verbose --timestamp --force --deep -o runtime --sign "${CODE_SIGN_IDENTITY}" "$LOCATION/Contents/Frameworks/Sparkle.framework/Versions/A/Resources/AutoUpdate.app"
codesign --verbose --timestamp --force -o runtime --sign "${CODE_SIGN_IDENTITY}" "$LOCATION/Contents/Frameworks/Sparkle.framework/Versions/A"

xcodebuild however seems to ignore the signing results (ie none of Sparkle's files are signed in the resulting archive) when running xcodebuild with the following arguments:

Code Block xcodebuild -scheme Release -configuration Release -archivePath App.xcarchive archive

Notarizing my app therefore fails.

What am I doing wrong here? I also tried signing using a Run Script phase during build, which resulted in No such file or directory errors.

Boost

Answer 1

DTS Engineer OP

Apple

May ’21

You should talk to the Sparkle folks about how best to integrate it with modern versions of Xcode. The process you’re currently using is likely to run into problems because of their nested code arrangement.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0