You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Change version in modules/sentry-cocoa.properties from 8.39.0 to 8.41.0
Build the samples/Sentry.Samples.Maui app
Expected Result
Build completed successfully.
Actual Result
Mac (Intel):
Xamarin.Shared.Sdk.targets(1663,3): Error: clang++ exited with code 1:
Undefined symbols for architecture x86_64:
“OBJC_CLASS$_SentryCrashExceptionApplication”, referenced from:
initial-undefines
Id: symbol(s) not found for architecture x86_64
clang++: error: linker command failed with exit code 1 (use -v to see invocation)
Mac (M3):
Xamarin.Shared.Sdk.targets(1663,3): Error: clang++ exited with code 1:
Undefined symbols for architecture arm64:
“OBJC_CLASS$_SentryCrashExceptionApplication”, referenced from:
initial-undefines
Id: symbol(s) not found for architecture arm64
clang++: error: linker command failed with exit code 1 (use -v to see invocation)
Are you willing to submit a PR?
No response
The text was updated successfully, but these errors were encountered:
For non-macOS platforms (when TARGET_OS_OSX is false), the header declares SentryCrashExceptionApplication as a subclass of NSObject, but there's no implementation provided for this case.
If SentryCrashExceptionApplication is truly only meant for macOS, shouldn't the header file reflect that? Otherwise, an "empty" implementation should be provided for non-macOS platforms (like it was before #4471)?
This affects sentry-dotnet/pull/3786 and ultimately, something that can be circumvented on the dotnet-side, if need be.
Platform
iOS
Environment
Production
Installed
Manually
Version
8.41.0
Xcode Version
16.2
Did it work on previous versions?
8.39.0
Steps to Reproduce
On Mac:
modules/sentry-cocoa.properties
from8.39.0
to8.41.0
samples/Sentry.Samples.Maui
appExpected Result
Build completed successfully.
Actual Result
Mac (Intel):
Mac (M3):
Are you willing to submit a PR?
No response
The text was updated successfully, but these errors were encountered: