Trying to build a .NET for iOS binding project results in build errors with "The name '_CodeSignature' is reserved and cannot be used."

[brunck]

Apple platform

iOS

Framework version

Other

Affected platform version

.NET 8, .NET 9

Description

I created a NuGet package with .NET for iOS bindings for an .xcframework. I have to build these xcframeworks myself from source to shorten their path due to the Windows long path error in Visual Studio.

Trying to consume this package in a .NET MAUI iOS app which is then submitted to TestFlight results in errors like NSUnderlyingError = "Error Domain=IrisAPI Code=-19241 \"Asset validation failed\" UserInfo={status=409, detail=Missing or invalid signature. The bundle 'x' at bundle path 'y.framework' is not signed using an Apple submission certificate.

So assuming that the .xcframework needs to be signed first, I code-sign it after I build the xcframework.

But then trying to build the binding project (which generates the NuGet package on build) I get build errors stating "The name '_CodeSignature' is reserved and cannot be used."

Is this a bug on the .NET end, and/or do I have to somehow extract the .xcframework after building the NuGet package without code signing, code-sign, then put the NuGet package back together?

Steps to Reproduce

1. Build .NET for iOS binding project with a code-signed xcframework native reference

Did you find any workaround?

No

Build logs

No response

[rolfbjarne]

So assuming that the .xcframework needs to be signed first, I code-sign it after I build the xcframework.

No, the (xc)framework is signed when building the app that consumes the framework.

Trying to consume this package in a .NET MAUI iOS app which is then submitted to TestFlight results in errors like NSUnderlyingError = "Error Domain=IrisAPI Code=-19241 \"Asset validation failed\" UserInfo={status=409, detail=Missing or invalid signature. The bundle 'x' at bundle path 'y.framework' is not signed using an Apple submission certificate.

Either the framework wasn't signed at all, or it was signed using an incorrect certificate.

Can you get an MSBuild binlog for the build that produces such an error? That should show if/how the framework was signed.

[brunck]

Since I'm building everything myself, and the settings are set to not sign the various frameworks that I'm building, I assume that the .frameworks are not ever signed at all. Do I need to sign those before creating xcframeworks with them?

[brunck]

Here is a binlog:

msbuild.binlog.zip

[rolfbjarne]

Trying to consume this package in a .NET MAUI iOS app which is then submitted to TestFlight results in errors like NSUnderlyingError = "Error Domain=IrisAPI Code=-19241 \"Asset validation failed\" UserInfo={status=409, detail=Missing or invalid signature. The bundle 'x' at bundle path 'y.framework' is not signed using an Apple submission certificate.

Which framework(s) exactly is TestFlight complaining about?

[brunck]

Error Domain=IrisAPI Code=-19241 \"Asset validation failed\" UserInfo={status=409, detail=Missing or invalid signature. The bundle 'com.datadogqh.Datadog' at bundle path 'Payload/sevendaytimer.app/ios-arm64_arm64e/DatadogCore.framework' is not signed using an Apple submission certificate.

Not sure why it's complaining about just that one.