Repository navigation
Respect FilterBadGatewayExceptions when initializing in code - #2930
Merged
Merged
Conversation
bitsandfoxes
force-pushed
the
fix/badgateway-filter-manual-init
branch
2 times, most recently
from
November 9, 2026 16:19
b9e8ae8 to
fac4826
Compare
bitsandfoxes
force-pushed
the
fix/badgateway-filter-manual-init
branch
from
November 10, 2026 15:44
fac4826 to
ca6a02e
Compare
bitsandfoxes
marked this pull request as ready for review
November 11, 2026 09:21
bitsandfoxes
requested review from
a team,
jpnurmi,
limbonaut and
tustanivsky
November 11, 2026 09:22
jpnurmi
approved these changes
Nov 11, 2026
This was referenced Nov 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Setting
FilterBadGatewayExceptions = falsetakes effect when the SDK is initialized in code withSentrySdk.Init.The Bad Gateway exception filter is added to every
SentryUnityOptionswhen it's created. The check that removes it when the option is off ran only while loading the options from the configuration window, so a code-only init kept the filter regardless of the option.The check now runs in
SentryUnitySdk.Init, which both the configuration window and code initialization go through, so it also respects a value changed in the options configure callback. The Web and Socket filters stay inScriptableSentryUnityOptions, since those settings only exist in the configuration window.Test:
SentryUnity_FilterBadGatewayExceptionsDisabled_RemovesBadGatewayFilterinitializes in code with the option off and checks the filter is gone.🤖 Generated with Claude Code