Compile error: strip exited with code 139

[tipa]

TLDR;

• This is a regression reported in the Xarain repo in October 2023: Regression: error : strip exited with code 139 dotnet/macios#19157
• Rolf Kvinge submitted a PR with a fix
• This has been addressed in Xcode 16.2

Package

Sentry

.NET Flavor

.NET

.NET Version

8.0.8

OS

iOS

SDK Version

4.10.2

Self-Hosted Sentry Version

No response

Steps to Reproduce

1. Install Xcode 16 using Xcodes
2. Set Xcode 16 active (sudo xcode-select -s /Applications/Xcode-16.0.0.app/Contents/Developer)
3. Install .NET 8 tools with Xcode 16 support (see here)
4. Create new iOS app (dotnet new ios)
5. Add latest Sentry SDK (v4.10.2) from NuGet
6. dotnet publish

Expected Result

The app builds

Actual Result

Error while building:
/usr/local/share/dotnet/packs/Microsoft.iOS.Sdk.net8.0_18.0/18.0.8287-xcode16/tools/msbuild/iOS/Xamarin.Shared.targets(2848,3): error : strip exited with code 139

This issue has been discussed previously here and a PR was created here (but not accepted yet).

For some reason, I was successful building my app successfully yesterday with the same tooling & Sentry version, but not today. It now consistently fails with every test project if I have the Sentry SDK added to, and it succeeds consistently when I remove it.

[jamescrosswell]

@tipa do you have your Sentry version pinned? A 4.11.0 release was made a few hours ago.

This is odd though as both the bug and the solution that you linked to seem to be part of a dotnet workload rather than part of Sentry.

[tipa]

The issue also happens for me with 4.11.0.
I agree that this totally looks like a problem of dotnet or the Apple tooling - I opened this issue because you perhaps could or would want to workaround the issue since since the it can be reproduced so easily and reliably (at least in my dev environment now, with Xcode 16). Perhaps, as more users .NET users update to Xcode 16, more people could be affected. Are you able to reproduce the problem with the steps I provided?

[bitsandfoxes]

There are a couple of new issues regarding Cocoa and Xcode 16 as well so I don't expect this to be the last of our problems.