Skip to content

Clearly point out missing reason for NSExceptions #3706

@philipphofmann

Description

@philipphofmann

Description

Our events should communicate when the NSException doesn't have a reason because this can lead to confusion, such as #3265. We could use a placeholder reason such as <Missing Reason> when there is none, as suggested in #3265 (comment). We have to ensure this works for unhandled NSExceptions as well as for user-reported NSExceptions via SentrySDK.captureException.

Metadata

Metadata

Labels

Breaking-changeshould go in a major release (breaks apps, changes default configs in a major way)CocoaImprovement

Projects

Status

Blocked

Relationships

None yet

Development

No branches or pull requests

Issue actions