-
-
Notifications
You must be signed in to change notification settings - Fork 206
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: incorrect use of SentryNative within a WASM app #3363
Conversation
else | ||
{ | ||
#pragma warning restore CS0162 // Unreachable code detected | ||
options.LogDebug("This doesn't look like a Native AOT application build."); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with the // TODO this probably more closely represents trimming rather than NativeAOT?
. Enabling AOT compilation and then reading this in the logs does seem odd.
Instructions and example for changelogPlease add an entry to Example: ## Unreleased
- incorrect use of SentryNative within a WASM app ([#3363](https://github.com/getsentry/sentry-dotnet/pull/3363)) If none of the above apply, you can opt out of this check by adding |
Fixes #3263 by disabling sentry-native SDK init when running under WASM AOT.
Tested manually by running the Sentry.Samples.AspNetCore.Blazor.Wasm app produced by
dotnet publish -c Release
. Proper tests could be part of #2021