Maui iOS build error(s): The xcframework sentry.bindings.cocoa\5.10.0\lib\net8.0-ios17.0\Sentry.Bindings.Cocoa.resources.zip has an incorrect or unknown format and cannot be processed.

[bruno-garcia]

Apple platform

iOS

Framework version

net9.0-*

Affected platform version

.NET 8, .NET 9, VS 17.14.6

Description

Reported originally:

• Maui iOS build error(s): The xcframework sentry.bindings.cocoa\5.10.0\lib\net8.0-ios17.0\Sentry.Bindings.Cocoa.resources.zip has an incorrect or unknown format and cannot be processed. getsentry/sentry-dotnet#4292

User's description:

When trying to build our Maui project we're getting the following 4 errors:

The xcframework C:\Users******.nuget\packages\sentry.bindings.cocoa\5.10.0\lib\net8.0-ios17.0\Sentry.Bindings.Cocoa.resources.zip has an incorrect or unknown format and cannot be processed.
Can't process the zip file 'C:\Users******..nuget\packages\sentry.bindings.cocoa\5.10.0\lib\net8.0-maccatalyst17.0\Sentry.Bindings.Cocoa.resources.zip' on this platform: the file 'Sentry-Dynamic.xcframework/ios-arm64_arm64e_x86_64-maccatalyst/Sentry.framework/PrivateHeaders' is a symlink.
Can't process the zip file 'C:\Users******..nuget\packages\sentry.bindings.cocoa\5.10.0\lib\net8.0-maccatalyst17.0\Sentry.Bindings.Cocoa.resources.zip' on this platform: the file 'Sentry-Dynamic.xcframework/ios-arm64_arm64e_x86_64-maccatalyst/Sentry.framework/Resources' is a symlink.
The xcframework C:\Users******..nuget\packages\sentry.bindings.cocoa\5.10.0\lib\net8.0-maccatalyst17.0\Sentry.Bindings.Cocoa.resources.zip has an incorrect or unknown format and cannot be processed.
Updating Visual Studio to 17.14.6 (June 2025) is the cause - I guarantee it. Everything built correctly yesterday, but clearly Microsoft have changed something in their Maui compilation that's caused this mismatch with Sentry.

Steps to Reproduce

Add Sentry.Maui to a blank app.

Initialize it with:

                .UseSentry(options =>
                {
                    //The DSN is the only required setting
                    options.Dsn = **************;

#if DEBUG             
                    options.Debug = true;
                    options.TracesSampleRate = 1.0;
#else
                    options.TracesSampleRate = 0.2;
#endif

                    //All other Sentry options
                    options.IsGlobalModeEnabled = true;
                    options.IncludeTextInBreadcrumbs = true;
                    options.IncludeTitleInBreadcrumbs = true;
                    options.IncludeBackgroundingStateInBreadcrumbs = true;
                    options.AttachStacktrace = true;
                    options.CaptureFailedRequests = true;
                });

Did you find any workaround?

Revert the Visual Studio version to 17.14.5

Build logs

Flash0ver/dotnet-macios-issues-23101

[Flash0ver]

Created a repo with repro, example and .binlog:
https://github.com/Flash0ver/dotnet-macios-issues-23101

[sethom]

That looks like the issue described here:
https://docs.sentry.io/platforms/dotnet/troubleshooting/

I ran into this same issue and it resolved whenever I disabled Hot Restart per the troubleshooting document

[bruno-garcia]

The original issue raised on the Sentry .NET SDK repo mentions:

(by the way I am aware of docs.sentry.io/platforms/dotnet/guides/maui/troubleshooting#visual-studio-hot-restart-incompatibility, but I don't have Hot Restart enabled, so that's not a problem, this is definitely caused by the VS update).

So thanks for raising that this can also happen with hotreload but it seems it can also happen unrelated to it

[rolfbjarne]

@Flash0ver

Created a repo with repro, example and .binlog: Flash0ver/dotnet-macios-issues-23101

It looks like the problem only happens when building Mac Catalyst on Windows, the iOS build works.

Could you confirm whether you see the same behavior?

[Flash0ver]

@rolfbjarne thanks for looking into this.

I thought that this error occurred on both TargetPlatforms

• -ios
• -maccatalyst

Let me get back to you on this tonight (CEST) when I'm on my Windows machinery:
I'll test all OS-specific TFMs individually.

[Flash0ver]

You're right, it does indeed only fail for Mac Catalyst, but does pass for iOS builds.

[rolfbjarne]

Thanks for confirming!

That means changing the project file to this would be a workaround:

<TargetFrameworks>net9.0-android;net9.0-ios</TargetFrameworks>
<TargetFrameworks Condition="!$([MSBuild]::IsOSPlatform('windows'))">$(TargetFrameworks);net9.0-maccatalyst</TargetFrameworks>
<TargetFrameworks Condition="$([MSBuild]::IsOSPlatform('windows'))">$(TargetFrameworks);net9.0-windows10.0.19041.0</TargetFrameworks>

That way Mac Catalyst is only enabled when not building on Windows.

I'm keeping this open, because the Mac Catalyst build failing is still a regression, and we'll fix that.

[mtanml]

@Flash0ver I'm seeing the issue for Android and iOS builds

[rolfbjarne]

@mtanml please provide an MSBuild binlog for the failures.