fix: Release Builds with Trimming enabled crashing on launch with NLog Integration#3743
fix: Release Builds with Trimming enabled crashing on launch with NLog Integration#3743jamescrosswell merged 9 commits intomainfrom
Release Builds with Trimming enabled crashing on launch with NLog Integration#3743Conversation
… the Setup Extensions of the LogManager to prevent NLog types form getting trimmed
|
@jamescrosswell About #3698, do you think my PR would be problematic for other platforms? Or can we go ahead with this change for now? |
Not sure I follow. This PR is to address #3698 right? I can't see anything in the PR (yet) that is platform specific. Have you had a chance to test this out yet, to make sure it resolves the issue? It's another one that's hard to test in unit tests due to the need to enable trimming. |
|
@jamescrosswell Sorry, about that. The PR is for #3680, but you mentioned in #3698 that we needed to bump the NLog and I did this here as part of the fix.
Yes it's all good, I'm just waiting for your input to mark this PR as reviewable |
If you're waiting for input on this PR, you should mark it ready for review... or is there another discussion I'm neglecting somewhere? |
Ah I see, no I don't think we need to change the way the options are structured if this PR resolves the original issue. Changing the options would be quite complex - definitely couldn't be done in a point release (would have to happen in a major version bump) so best to keep separate from this PR. |
Sounds good. Well, there you have it! 😁 |
Release Builds with Trimming ON Crashing on Launch when using NLog Integration and FailedRequestStatusCodes OptionsRelease Builds with Trimming enabled crashing on launch with NLog Integration
jamescrosswell
left a comment
There was a problem hiding this comment.
Looks great. Thanks @bricefriha !
|
|
||
| - Fixed ArgumentNullException in FormRequestPayloadExtractor when handling invalid form data on ASP.NET ([#3734](https://github.com/getsentry/sentry-dotnet/pull/3734)) | ||
| - ArgumentNullException in FormRequestPayloadExtractor when handling invalid form data on ASP.NET ([#3734](https://github.com/getsentry/sentry-dotnet/pull/3734)) | ||
| - Crash when using NLog with FailedRequestStatusCodes options in a Maui app with Trimming enabled ([#3743](https://github.com/getsentry/sentry-dotnet/pull/3743)) |
There was a problem hiding this comment.
MAUI is all caps. Maui is a city in Hawaii
Instructions and example for changelogPlease add an entry to Example: ## Unreleased
- `Release` Builds with Trimming enabled crashing on launch with NLog Integration ([#3743](https://github.com/getsentry/sentry-dotnet/pull/3743))If none of the above apply, you can opt out of this check by adding |
This PR aims to fix #3680, an issue that causes a crash when using NLog with FailedRequestStatusCodes options in a MAUI app with Trimming enabled in
Release.Note
we needed to update Nlog to 5.2 to be able to use
RegisterTypefor this fixworth mentioning: #3698