Skip to content

Releases: bugsnag/bugsnag-cocoa

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

v5.17.0

26 Sep 01:05
Compare
Choose a tag to compare

Enhancements

  • Capture trace of error reporting thread and identify with boolean flag
    #303

Bug Fixes

  • Prevent potential crash in session delivery during app teardown
    #308

v5.16.4

14 Sep 00:20
Compare
Choose a tag to compare

Bug Fixes

  • Ensure NSException is captured when handler is overridden
    #313

  • Fix mach handler declaration and imports. This resolves an issue where signal
    codes were less specific than is possible.
    #314

  • Only call previously installed C++ termination handler if non-null. Fixes an
    unexpected termination if you override the handler with null before
    initializing Bugsnag and then throw a C++ exception and would like the app to
    continue after Bugsnag completes exception reporting.

v5.16.3

14 Aug 14:42
3cee5b9
Compare
Choose a tag to compare

Bug Fixes

  • Deregister notification observers and listeners before application termination #301

v5.16.2

17 Jul 15:48
Compare
Choose a tag to compare

Bug fixes

  • Fix a regression in session tracking where app version was set to nil
    #296

  • Fix a regression in session tracking which caused the first session HTTP
    request to be delivered on the calling thread when automatic session tracking
    is enabled
    #295

v5.16.1

11 Jul 17:17
Compare
Choose a tag to compare

Bug Fixes

  • Respect appVersion override when serialising KSCrash report #292

v5.16.0

02 Jul 10:56
b5f5ae9
Compare
Choose a tag to compare

This release alters the behaviour of the notifier to track sessions automatically.
A session will be automatically captured on each app launch and sent to https://sessions.bugsnag.com.

If you use Bugsnag On-Premise, it is now also recommended that you set your notify and session endpoints via config.setEndpoints(notify:sessions:). The previous properties used to configure this, config.notifyURL and config.sessionURL, are now readonly and therefore no longer assignable.

  • Enable automatic session tracking by default #286

Bug Fixes

  • Handle potential nil content value in RegisterErrorData class #289

v5.15.6

30 May 17:46
Compare
Choose a tag to compare

Bug Fixes

  • Ensure device data is attached to minimal reports #279
  • Enforce requiring API key to initialise notifier #280

v5.15.5

25 Apr 10:41
efe07ee
Compare
Choose a tag to compare

Bug Fixes

  • Changes report generation so that when a minimal or incomplete crash is recorded, essential app/device information is included in the report on the next application launch. #239
    #250

  • Ensure timezone is serialised in report payload.
    #248
    Jamie Lynch

v5.15.4

22 Feb 10:40
Compare
Choose a tag to compare

This release adds additional device metadata for filtering by whether an error
occurred in a simulator (#242)
and by processor word size (#228).

Bug Fixes

  • Ensure error class and message are persisted when thread tracing is disabled
    #245
    Jamie Lynch
  • Re-add app name to the app tab of reports
    #244
    Jamie Lynch
  • Add payload version to report body to preserve backwards compatibility with
    older versions of the error reporting API
    #241
    Jamie Lynch