warning: changes being made to the file will invalidate the code signature

[gabors]

MUXSDKStats 4.8.1
MuxCore 5.5.1

Using SPM

Build warning

/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/strip -D -S -no_atom_info /Users/gabor/Library/Developer/Xcode/DerivedData/Screeners-fbzbdqgslszigydfrilfmdsrybwh/SourcePackages/artifacts/stats-sdk-objc/MuxCore/MuxCore.xcframework/ios-arm64_x86_64-simulator/MuxCore.framework/MuxCore -o /Users/gabor/Library/Developer/Xcode/DerivedData/Screeners-fbzbdqgslszigydfrilfmdsrybwh/Build/Products/Debug-iphonesimulator/WBDScreeners.app/Frameworks/MuxCore.framework/MuxCore/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/gabor/Library/Developer/Xcode/DerivedData/Screeners-fbzbdqgslszigydfrilfmdsrybwh/SourcePackages/artifacts/stats-sdk-objc/MuxCore/MuxCore.xcframework/ios-arm64_x86_64-simulator/MuxCore.framework/MuxCore (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/gabor/Library/Developer/Xcode/DerivedData/Screeners-fbzbdqgslszigydfrilfmdsrybwh/SourcePackages/artifacts/stats-sdk-objc/MuxCore/MuxCore.xcframework/ios-arm64_x86_64-simulator/MuxCore.framework/MuxCore (for architecture arm64)

[CFKevinRef]

1. What is the version of Xcode?
2. Can you provide more of the build log? In general I would not expect Xcode to try to strip a signed binary.
3. Do you have "Strip Debug Symbols During Copy" enabled in the project settings?

For what it's worth, on Xcode 16.4 when I enable "Strip Debug Symbols During Copy" in an SPM project I get a different message about MuxCore: "warning: not stripping binary because it is signed: ..."

[gabors]

Xcode Version 16.4 (16F6)
This warning appears when running the Mac Catalyst version of the build. The regular iOS build is fine.
This warning does not appear when using previous mux-stats-sdk-avplayer 4.7.0 and stats-sdk-objc 5.4.1

COPY_PHASE_STRIP is set to NO

I've attached the build log

Build WBDScreeners-ios_2025-08-14T14-46-40.txt

[CFKevinRef]

This seems to be a result of each framework being code-signed, instead of just the top-level XCFramework bundle. This is safe to ignore for now, and the next release of MuxCore will remove the extra code signature leading to this message.

[gabors]

Thanks. I'll wait for the next release then. When can we expect it?

[CFKevinRef]

We're preparing one now, and it should be available in the next day or two. I'll ping here once it's public.

[gabors]

@CFKevinRef I just tried the newly released MuxCore 5.6.0
The build warning is gone when running a Mac Catalyst build.

But now it still showed up when building the iOS and tvOS apps. These also appeared with MuxCore 5.5.1.

Attaching build logs

Build WBDScreeners-tvos_2025-08-21T14-53-50.txt
Build WBDScreeners-ios_2025-08-21T14-51-07.txt

[CFKevinRef]

Both of these are simulator builds. It seems that even when code signing is disabled, Xcode still inserts a basic code signature when building a framework for simulator. I've manually removed that code signature for the next MuxCore release (no date planned at the moment).

[gabors]

Why was this not an issue with the previous mux release?

[CFKevinRef]

It's still not clear to me why your project is trying to strip third party dependencies, but I would be interested to know what you find out.

[gabors]

I am still facing this build warning for iOS and tvOS but not Mac Catalyst.
This is preventing us from updating to this new release. The prior release had no issues.

My pseudo project structure is as follows, maybe it will help you @CFKevinRef:

PROJECT
MyApp

TARGETS
MyApp-ios (this target is for iOS, iPadOS and Mac Catalyst
MyApp-tvos
MyAppKit (this is a framework target with shared code used in both iOS and tvOS targets)

MUXSDKStats swift package is referenced under Frameworks & Libraries of MyAppKit, because that is where it is used.

MUXSDKStats swift package is also referenced under Frameworks & Libraries of MyApp-ios, this was necessary because otherwise the Mac Catalyst app crashes on startup, being unable to find MUX libraries.

If there is a cleaner way to integrate MUXSDKStats, please let me know, would be very much appreciated.

[CFKevinRef]

If I understand correctly, this may not be a valid project setup, or at least not one that is handled well by the tools. Xcode is effectively trying to embed the MUXSDKStats product and dependencies to both the app and the library.

To help here we did recently enable mergeable library support for MuxCore. If you enable the "Create Merged Binary" build setting on the MyAppKit target, the resulting framework will have MuxCore as part of its binary. At this point you can remove MUXSDKStats from the app target. The official docs have more info.