Skip to content

Releases: bugsnag/bugsnag-cocoa

v5.22.1

21 May 12:40
d611c39
Compare
Choose a tag to compare
  • Report correct app version in out-of-memory reports. Previously the bundle
    version was reported as the version number rather than the short version
    string.
    #349

  • Fix missing stacktraces in reports generated from notify()
    #348

v5.22.0

09 May 10:21
0f0334e
Compare
Choose a tag to compare

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

  • Add configuration option (reportOOMs) to disable out-of-memory (OOM) event
    reporting, defaulting to enabled.
    #345
  • Disable background OOM reporting by default. It can be enabled using
    reportBackgroundOOMs.
    #345

v5.21.0

02 May 15:59
340964c
Compare
Choose a tag to compare

Enhancements

  • Migrate version information to device.runtimeVersions
    #340
  • Add internal api for mutating session payload before sending
    #341

v5.20.0

11 Apr 12:54
6207b5b
Compare
Choose a tag to compare

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

27 Mar 11:54
Compare
Choose a tag to compare

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 from notify() will now use the NSException
    instance's call stack addresses to construct the stacktrace, ignoring depth.
    This fixes an issue in macOS exception reporting where reportException 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

v5.19.0

28 Feb 10:22
d259154
Compare
Choose a tag to compare

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
    #324

Enhancements

  • Add stopSession() and resumeSession() to Bugsnag
    #325

v5.18.0

21 Feb 13:59
Compare
Choose a tag to compare

Enhancements

  • Capture basic report diagnostics in the file path in case of crash report
    content corruption
    #327

v5.17.3

19 Dec 16:37
Compare
Choose a tag to compare

Bug Fixes

  • Fix case where notify() causes an unhandled report
    #322

  • Fix possible crash when fetching system info to append to a crash report
    #321

v5.17.2

05 Dec 14:49
Compare
Choose a tag to compare
  • Add Device time of report capture to JSON payload
    #315

v5.17.1

30 Nov 02:01
Compare
Choose a tag to compare

Bug Fixes

  • Fix stack trace resolution on iPhone XS sometimes reporting incorrect
    addresses
    #319

  • Add fatalError and other assertion failure messages in reports for
    Swift 4.2 apps. Note that this only includes messages which are 16
    characters or longer. See the linked pull request for more information.
    #320