-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
feat: Filter Unity telemetry BadGatewayException
on iOS native layer
#1345
Conversation
BadGatewayException
filtering to native layerBadGatewayException
on iOS native layer
|
@@ -139,6 +139,11 @@ public new CompressionLevelWithAuto RequestBodyCompressionLevel | |||
/// </summary> | |||
public TimeSpan AnrTimeout { get; set; } = TimeSpan.FromSeconds(5); | |||
|
|||
/// <summary> | |||
/// Whether the SDK should automatically filter `Bad Gateway Exceptions` caused by Unity. |
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.
Above it indicates that it does this only work for iOS. Should we indicate this in the docs here?
/// Whether the SDK should automatically filter `Bad Gateway Exceptions` caused by Unity. | |
/// Whether the SDK should automatically filter `BadGatewayException` caused by Unity on iOS. |
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.
There are a whole bunch of places these exceptions are coming from. We already filter them on the C# layer but now, with the same flag because it's the same noise, we also filter the ones coming from native iOS.
We had filtering of
BadGatewayExceptions
on the C# layer. If enabled, these need to be propagated down to the native layer as well.