The xcframework sentry.bindings.cocoa\5.0.1\lib\net8.0-ios17.0\Sentry.Bindings.Cocoa.resources.zip has an incorrect or unknown format and cannot be processed.

[imsam67]

Package

Sentry

.NET Flavor

.NET

.NET Version

9.0.102

OS

iOS

SDK Version

5.0.1

Self-Hosted Sentry Version

No response

Steps to Reproduce

When I try to build my .NET MAUI app targeting .NET 9, I get the following error message and the build fails.

The xcframework C:\Users\sam.nuget\packages\sentry.bindings.cocoa\5.0.1\lib\net8.0-ios17.0\Sentry.Bindings.Cocoa.resources.zip has an incorrect or unknown format and cannot be processed.

Any suggestions on how to address this issue?

Expected Result

The app should just build

Actual Result

Fails with the message above

[jamescrosswell]

Hi @imsam67 - thanks for getting in touch.

I don't see the same behaviour here. Is there any chance you could provide a small sample app that demonstrates this behaviour?

[rodolfoBee]

Same issue has been reported via support.

[mads195]

We have the same issue (reported via support as per @rodolfoBee comment above) albiet .NET 8. but wanted to add some info about this issue that we've discovered. We've been chatting with a couple of others on Discord too but in the interests of consolidated info, will update here.

Our main dev environments are Win11P boxes, Visual Studio 2022 v17.12.4. We replicated this issue with a directly connected iPhone 13 running iOS 18.1.1. The issue always occurs when running debug to a directly connected iPhone.

The issue does not occur when debugging/building to a simulator hosted on a Mac (where the Win11P box is connected to that Mac. The issue also does not occur when debugging/building the App directly on the Mac to an iPhone which is connected to that Mac. Both Android and iOS builds (local) work when local simulator is selected.

We've tried with and without Hot Reload enabled (Debug > Options > Debugging > XAML Hot Reload) but no effect on the outcome.

Hopefully some of that is useful! It's something to do with the environment and does seem to center around debugging on a directly connected device.

[jamescrosswell]

@aritchie is this something you'd be able to look into?