Be notified of new releases
Create your free GitHub account today to subscribe to this repository for new releases and build software alongside 36 million developers.Sign up
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.
- Persist breadcrumbs on disk to allow reading upon next boot in the event of an
uncatchable app termination.
+[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
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 from
notify()will now use the
instance's call stack addresses to construct the stacktrace, ignoring depth.
This fixes an issue in macOS exception reporting where
reporting the handler code stacktrace rather than the reported exception
Note for Carthage users: this release updates the Xcode configuration to the settings recommended by Xcode 10.
- Update workspace to recommended settings suggested by XCode 10
- Add stopSession() and resumeSession() to Bugsnag