Releases: bugsnag/bugsnag-cocoa
v5.22.1
v5.22.0
This release disables background out-of-memory termination reporting by default,
as it may be confusing that foreground and background grouped together and are
not necessarily at the same level of importance during triage.
Enhancements
v5.21.0
v5.20.0
Enhancements
- Persist breadcrumbs on disk to allow reading upon next boot in the event of an
uncatchable app termination. - Add
+[Bugsnag appDidCrashLastLaunch]
as a helper to determine if the
previous launch of the app ended in a crash or otherwise unexpected termination. - Report unexpected app terminations on iOS as likely out of memory events where
the operating system killed the app
v5.19.1
Bug fixes
-
Fix generating an incorrect stacktrace used when logging an exception to
Bugsnag from a location other than the original call site (for example, from a
logging function or across threads). If an exception was raised/thrown, then
the resulting Bugsnag report fromnotify()
will now use theNSException
instance's call stack addresses to construct the stacktrace, ignoring depth.
This fixes an issue in macOS exception reporting wherereportException
is
reporting the handler code stacktrace rather than the reported exception
stack.
#334 -
Fix network connectivity monitor by connecting to the correct domain
Jacky Wijaya
#332