[PLAT-6261] Detect uncaught objc exceptions on Mac Catalyst and iOSAppOnMac #1053
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.
Goal
iOS apps running on Mac Catalyst or on Macs with Apple Silicon were not having uncaught exceptions reported when thrown from a UI event handler.
The normal mechanisms we use to detect exceptions (
NSUncaughtExceptionHandler
orstd::terminate_handler
) are not triggered due to the way AppKit has historically dealt with exceptions.Changeset
Bugsnag now hooks into
-[NSApplication reportException:]
to detect uncaught exceptions.Testing
Tested using a sample project targeting Mac Catalyst and on a Mac mini with Apple silicon.