CHANGELOG.md

Changelog

6.8.4 (2021-04-14)

Enhancements

• macCatalystiOSVersion is now reported for apps built with Mac Catalyst and iOS app running on Apple silicon. #1066

Bug fixes

• Fix crashes that could occur in bsg_recordException in low memory conditions. #1068

• Fix a crash in bsg_ksmachgetThreadQueueName. #1065

• Improve timestamp accuracy to fix breadcrumbs that are reported to occur after the error. #1062

6.8.3 (2021-04-07)

Bug fixes

• Catch exceptions thrown while preparing JSON for upload rather than crashing. #1063

• Prevent app hangs being reported if a debugger is attached. #1058

6.8.2 (2021-03-31)

Bug fixes

• Enable SUPPORTS_MACCATALYST in main Xcode project. #1056

• osName and osVersion now reflect the Mac's OS when running Mac Catalyst apps or iOS apps running on macOS. Fix reporting of model for Mac Catalyst apps or iOS apps running on macOS. #1055

• Uncaught exceptions thrown while handing UI events in iOS apps running on macOS are now detected. #1053

6.8.1 (2021-03-24)

Bug fixes

• Fix unreliable ordering of breadcrumbs. #1049

6.8.0 (2021-03-18)

Enhancements

• Bugsnag now detects app hangs (when the main thread is unresponsive for a period of time), alerting you of issues with your app’s responsiveness. By default, only fatal app hangs (those that end with termination by the system watchdog or being force-quit by the user) will be reported. This behaviour can be configured using the new appHangThresholdMillis configuration option. For more information see the documentation. #1039

Bug fixes

• Fix a heap buffer overflow reported by Address Sanitizer. #1043

• Fix parsing of callStackSymbols where the image name contains spaces. #1036

• Fix a possible deadlock when writing crash reports for unhandled errors. #1034

6.7.1 (2021-03-10)

Bug fixes

• Fix os_proc_available_memory runtime link error on Mac Catalyst. #1025

• Fix missing osName and osVersion for errors reported from app extensions that do not link against UIKit. #1022

• Fix incorrect freeMemory for errors reported via notify() #1021

6.7.0 (2021-03-03)

Enhancements

• Bugsnag will now identify crashes that occur whilst your app is launching, allowing you to prioritize fixing high-impact launch crashes. For more information see the documentation. #1004

Bug fixes

• Fix inaccurate app.duration after multiple calls to notify() #1014

• Fix a possible deadlock when writing crash reports for unhandled errors. #1013

Deprecated

• Bugsnag.appDidCrashLastLaunch has been deprecated in favour of Bugsnag.lastRunInfo.crashed and will be removed in the next major release.

6.6.4 (2021-02-24)

Bug fixes

• Fix possible deadlock when recording thread information for handled errors. #1011

• Fix Swift 5.4 fatal error message parsing. #1010

• Improve accuracy of jailbreak detection. #1000

6.6.3 (2021-02-17)

Bug fixes

• Fix hang after receiving signals in some cases. 1002

• Improve performance of thread recording for handled errors. #992

6.6.2 (2021-02-10)

Bug fixes

• Fix a tvOS file permission error that was introduced in 6.5.1 #996
• Fix an analyzer warning. #994
• Stop Bugsnag unregistering other signal handlers when catching a mach exception. #976

6.6.1 (2021-02-03)

Bug fixes

• Fix compiler warnings when importing Bugsnag from Objective-C sources that do not use ARC. #985
• Fix a rare crash that could occur in the event of JSON parsing failures. #987

6.6.0 (2021-01-20)

Enhancements

• The NSError's userInfo property is now included in reports. #974

6.5.1 (2021-01-13)

Bug fixes

• Fix a regression where OOM events were missing session information. #963

• Make maxPersistedEvents and maxPersistedSessions comply with the specification, with defaults of 32 and 128 respectively. #966

6.5.0 (2021-01-06)

Enhancements

• Errors may now be discarded based on their errorClass using the new discardClasses configuration option. #938

• The maxiumum number of persisted errors / events may now be configured using the new maxPersistedEvents configuration option. #936

• The maxiumum number of persisted sessions may now be configured using the new maxPersistedSessions configuration option. #943

• Bugsnag log messages are now prefixed with [Bugsnag] for easier searching & filtering. #955

Bug fixes

• Fix reliability of Swift fatal error message reporting. #948

6.4.1 (2020-12-14)

Bug fixes

• Place "unhandledOverridden" inside "severityReason" instead of at the top level. 937

6.4.0 (2020-12-08)

Enhancements

• Allow overriding the "unhandled" flag in error callbacks. #921 #912

Bug fixes

• Fix unexpected exception behavior when started without an API key. #931

6.3.0 (2020-12-02)

Enhancements

• Out Of Memory errors now include more information, including custom metadata and user information. #915 #908

• Bugsnag can now be used without UIKit, reducing memory usage in app extensions. #919

Bug fixes

• Fixed incorrect app version reported when sending crash reports from older versions of Bugsnag (before 6.2.3) #911

• Fixed a rare crash in -[BugsnagClient computeDidCrashLastLaunch] #917

6.2.6 (2020-11-25)

Bug fixes

• Error and session deliveries that fail with an HTTP error status code will now be retried if appropriate. #895

• Fixed a rare crash in BugsnagClient's network connectivity observer block. #904

6.2.5 (2020-11-18)

Bug fixes

• Fixed a rare crash due to a race condition in BugsnagSystemState. #893 #866

• Out Of Memory errors are no longer reported if a device reboot was detected. #822 #545

6.2.4 (2020-11-04)

Bug fixes

• The onCrashHandler is no longer called in the event of an OOM. #874

6.2.3 (2020-10-28)

Enhancements

• Use os_proc_available_memory() to get free memory, if available. #851

• Reduced the CPU and memory impact of leaving breadcrumbs. #853 #863

Bug fixes

• Fix for incorrect version info during edge case where version info is not manually set, and app version is changed between crashing and reporting the error. #862

• Catch and report unexpected exceptions when (de)serializing JSON data rather than crashing. #856

6.2.2 (2020-10-21)

Enhancements

• Support "foreground" duration in MacOS as well. #848

• Timestamp accuracy in reports has been increased from seconds to milliseconds. #847

• Calculation of "foreground" duration now also includes time in UIApplicationStateActive and UIApplicationStateInactive states in order to match Apple's definition of "foreground". #839

6.2.1 (2020-10-15)

Bug fixes

• Changed synchronization method when responding to dynamic library image events to a dispatch queue, which is a more bulletproof and battle-hardened approach. #837

• Fixed a deadlock which can occur when calling notify #833

6.2.0 (2020-10-07)

Enhancements

• An invalid or missing API key now causes an NSException to be thrown upon calling [Bugsnag start]. This check used to occur during configuration, and only for malformed API keys. #828

• Exception Mach code and subcode are now written to the crash report as stringified hex values instead of integers to avoid potential data loss from JSON readers that lose the lower bits from unsigned 64-bit numbers. #827

• Improved out-of-memory event detection by disabling reporting when a debugger is attached. OOM reporting is now enabled by default in debug builds. #820

6.1.7 (2020-10-01)

Bug fixes

• Re-enabled the Require Only App-Extension-Safe API build setting #823

• Fix reporting of events with more than one error #821

6.1.6 (2020-09-24)

Bug fixes

• Fix crash-on-launch (attempt to insert into immutable dictionary). #819

6.1.5 (2020-09-23)

Enhancements

• Add +[Bugsnag breadcrumbs] to allow apps to fetch the list of breadcrumbs. #813

• Disable JSON pretty-printing in KSCrash reports to save disk space and bandwidth. #802

Bug fixes

• Fix reporting of Mach exception code and subcode. #806

• Create date formatters at init time to avoid potential race conditions. #807

• Refactor OOM handler to be less suceptible to data loss on crash. #804

6.1.4 (2020-09-11)

Bug fixes

• Copy the metadata observer list rather than mutating it directly. #796

• Reorganized the project file #793

• Removed some magic values and used the const string references instead. #792

• Added BSGJSONSerializer, which ensures no exceptions get thrown (NSErrors get returned instead) #791

• Guard against non-string metadata map keys #790

• Quiet some Analyzer false positives #789

• Avoid crash reporting OOMs if nil provided as codeBundleId #784

6.1.3 (2020-08-17)

Bug fixes

• Persist user when set on client #770

• Avoid sharing global crash context when recording thread information for handled errors #766

• Respect bundle version set from config #762

• (React Native) Call react native observer with initial user/context values #768

• (React Native) Populate app/device metadata fields for RN errors #763

6.1.2 (2020-07-21)

Bug fixes

• Ensure foreground stats are recorded for handled errors #755

• Synchronize access to sessions being delivered in de-duplication code #756

• Removed non-thread safe date formatter #758

6.1.1 (2020-07-16)

Bug fixes

• Improve performance of thread capture #723 #727 #728

• Improve thread-safety of breadcrumb count #743

• Fix JSON serialisation of strings with control characters #739

• Disable reporting of notable addresses from registers for handled errors #741

6.1.0 (2020-07-06)

Enhancements

• Add support for Swift Package Manager #729

6.0.1 (2020-06-29)

Bug fixes

• Move binary images store declaration from header file #725

• Make stacktrace properties for error/thread readwrite #722

• Fix incorrect string comparison of thread names in Mach exception handling #721

• Address unterminated string in thread gathering logic #720

6.0.0 (2020-06-22)

This version contains many breaking changes. It is part of an effort to unify our notifier libraries across platforms, making the user interface more consistent, and implementations better on multi-layered environments where multiple Bugsnag libraries need to work together (such as React Native).

Please see the upgrade guide for details of all the changes and instructions on how to upgrade.

Enhancements

• Allow starting Bugsnag from PList #676

• The comparison of redacted keys is now case-insensitive #653

• Unified the three main XCode projects #633

• Alter default session background timeout to 30s #581

• Support loading configuration from values in Info.plist. #582

• Add unhandledRejections to BugsnagErrorTypes #567

• Rename Bugsnag start methods #566

• Rename OnSend to OnSendError #562

• Add onCrashHandler data to BugsnagEvent metadata #564

• Rename BugsnagUser properties #560

• Make BugsnagOnErrorBlock return BOOL rather than void #555

• Make BugsnagPlugin take BugsnagClient as param #558

• Make user editable on BugsnagEvent #557

• Add getter for Bugsnag.context #554

• Make BugsnagUser properties readonly #556

• Add sendThreads property to BugsnagConfiguration #549

• Hide additional methods from public API #552

• Move codeBundleId from configuration to non-public client property #548

• Add structured app/device fields to BugsnagSession #546

• Add redactedKeys for removing sensitive values from metadata #540

• Move endpoint configuration to class #542

• Make all callbacks return boolean values #534

• Add originalError property to BugsnagEvent #541

• Remove attachCustomStacktrace from public API #547

• Create structured BugsnagError class #533

• Create structured BugsnagThread class #532

• Convert event.device from NSDictionary to a structured class #526

• Create structured BugsnagStackframe class #528

• Convert event.app from NSDictionary to a structured class #520 #600

• Make BugsnagClient a public interface #517

• Remove unused APIs from Bugsnag interface #514

• Enforce that config.maxBreadcrumbs must be between 0-100 #511

• Add unhandled property to BugsnagEvent #512

• Rename notifyReleaseStages to enabledReleaseStages #509

• Remove unused APIs from BugsnagSession interface #506

• Rename setUser/user interface on Bugsnag and BugsnagConfiguration #505

• Rename config.notifierType to config.appType #504

• Remove unused APIs on BugsnagEvent interface #498

• Allow addition/removal of OnBreadcrumb callbacks #508

• Remove unused APIs from BugsnagMetadata interface #501

• Remove unused APIs from BugsnagConfiguration interface #496

• Remove unused APIs from BugsnagBreadcrumb interface #502

• Remove notify method variants from public api on Bugsnag #497

• Remove leaveBreadcrumbWithBlock from public api on Bugsnag #491

• BugsnagNotifier is now BugsnagClient #480

• Remove setSuspendThreadsForUserReported, setReportWhenDebuggerIsAttached, setThreadTracingEnabled, setWriteBinaryImagesForUserReported from public API. #468

• Fixes typo in BSG_KSCDeleteOnSuccess enumeration #317

• Add a breadcrumb when Bugsnag first starts with the message "Bugsnag loaded" #445

• BugsnagMetaData is now BugsnagMetadata, including the configuration and event fields #450

• BugsnagCrashReport is now BugsnagEvent #449

• Add a configuration option to filter breadcrumbs by type. Use config.enabledBreadcrumbTypes to enable or disable particular types of breadcrumbs from being captured. #476

• Added a designated initializer to BugsnagConfiguration and removed functionality from the default convenience init() to ensure that apiKey has a value set. The apiKey must now be a correctly formatted one to be accepted.

  • Swift: BugsnagConfiguration(_ apiKey)
  • Objective C: [[BugsnagConfiguration alloc] initWithApiKey:]

  #446 #492

• Support editing breadcrumbs within an Event as objects. Breadcrumbs can now be inspected and modified from callbacks, for example:

  Bugsnag.notifyError(error) { event in
      event.breadcrumbs?.forEach({ crumb in
          if crumb.message == "something specific" {
              crumb.message = "[redacted]"
          }
      })
  }

  #474

• Bugsnag.addAttribute:value:tab: is now Bugsnag.addMetadataToSection:key:value: #454

• [Bugsnag clearTab:] is now [Bugsnag clearMetadataInSection:] (Swift: Bugsnag.clearMetadata(section:)) #457

• Renamed callback functions in the Configuration class:

  • beforeSendBlocks is now onSendBlocks (add using config.add(onSend: { ... }))
  • beforeSendSessionBlocks is now onSessionBlocks (add using config.add(onSession: { ... }))

• Added [Bugsnag clearMetadataInSection:withKey:] (Swift: Bugsnag.clearMetadata(section:key:)) #462

• Added Bugsnag.getMetadata(_ section). The behaviour is: calling with a valid section name will return the metadata for that section if it exists, or nil if it does not exist. Other, similar functionality (e.g. BugsnagConfiguration.getTab() has been renamed and had usage aligned with this change. #459

• Added Bugsnag.getMetadata(_ section: key:) #463

• Add a per-Event apiKey property. This defaults to the global BugsnagConfiguration value but can be overridden in event passed to the Bugsnag.notify() callback. #458

• Added Bugsnag.context, replicating the BugsnagConfiguration property. This is mutable and may be changed at any point. Changes are propagated to the BugsnagConfiguration property. #466

• Bugsnag.stopSession() is now Bugsnag.pauseSession(). This renaming has also been applied to the BugsnagNotifier and BugsnagSessionTracker classes. #464

• Add a breadcrumb when network connectivity changes #448

• Breadcrumbs now take a message parameter that can now be arbitrarily long. This simplifies breadcrumb creation using Bugsnag.leaveBreadcrumb(string) so that the value is prominently displayed and is not truncated. #433

• Add metadata accessor methods to BugsnagEvent #465

• Added a user-configurable enabledErrorTypes property to BugsnagConfiguration. The BugsnagErrorTypes property allows users to choose which types of events are reported. If automatic crash detection is disabled this value is ignored. User-generated notify() events are reported in all cases. #477 #561

• Internal logging has been unified. Where before two preprocessor macros were required to configure both Bugsnag and KSCrash portions, now the Bugsnag BSG_LOG_LEVEL macro is sufficient to configure both. This should be set on the Bugsnag framework build target. Further configuration instructions can be found in the BugsnagLogger.h header. #472

• Added a method to allow merging supplied and existing Event metadata. BugsnagMetadata.addMetadataToSection:values: allows Event callbacks to modify Event metadata en-mass. Supplied metadata should be a JSON-serializable dictionary. The resulting Event metadata is the result of applying the following rules to the existing metadata for each supplied value:

  • Non-null values replace any existing key/value pair.
  • Null values remove a key/value pair.
  • Invalid values are logged and ignored. #470

• Remove Bugsnag.configuration()?. All access to the configuration object should be performed prior to calling Bugsnag.start().

• User information is now persisted between application runs by default. When set a users' email, id and name are set on BugsnagConfiguration they are stored in the User Defaults and restored if an application is restarted. The values are also copied to the configuration metadata. #469 #590

• Added callback-free method to leave breadcrumbs: [Bugsnag leaveBreadcrumbWithMessage:metadata:andType] (Swift: Bugsnag.leaveBreadcrumb(_, metadata:, type:)) #482

• Added removeOnSessionBlock() methods to both Bugsnag and BugsnagConfiguration to allow removal of callbacks run when a session starts. #483

• Added addOnSendBlock:, removeOnSendBlock: to BugsnagConfiguration. #485 #485

• Enhanced device orientation change breadcrumbs. These are now reported with "from" and "to" values in a form consistent with the Android notifier. #486

• The metadata interface is now consistent across the Bugsnag, BugsnagMetadata, BugsnagConfig, BugsnagClient and BugsnagEvent classes. #513

• BugsnagClient now takes a shallow copy of the configuration passed in on initialisation. #524

• The bundleVersion property is available on BugsnagConfiguration allowing overriding the default plist value. #550

• Deliver each event in a separate request to avoid exceeding payload size limit #424

5.23.3 (2020-06-05)

Bug Fixes

• Fix DYLD lock mechanism preventing compilation on iOS <10. #675

5.23.2 (2020-05-13)

Bug Fixes

• Fixed an issue where an app could deadlock during a crash if unfavourable timing caused DYLD lock contention. #580

5.23.1 (2020-04-08)

Bug fixes

• Fix possible report corruption when using notify() from multiple threads when configured to skip capturing/reporting background thread contents (generally only Unity games). #442

• Added several additional event fields (codeBundleId, osName, modelNumber, locale) that were missing from the OOM reports. #444

• Bugsnag now correctly records a new session if it is returning to the foreground after more than 60 seconds in the background. #529

• Increased the detail in handled event breadcrumbs #493

• NSWorkspaceScreenSleep/Wake notifications now use the correct notification center. #525

• Device Charging status was being incorrectly reported as a number rather than a boolean. Device charging status is represented as a four-valued enum. If the device is plugged in it reports as charging, even if it is at 100%. Any other values are reported as not charging. #551

5.23.0 (2019-12-10)

This release removes support for reporting 'partial' or 'minimal' crash reports where the crash report could not be entirely written (due to disk space or other issues like the device battery dying). While sometimes the reports could point in the right direction for debugging, they could also be confusing or not enough information to pursue and close the issue successfully.

This release also renames a few configuration properties to align better with the intended use and other Bugsnag libraries, so people who use more than one platform can easily find related functionality in a different library. The old names are deprecated but still supported until the next major release. #435

• Bugsnag.setBreadcrumbCapacity() is now setMaxBreadcrumbs() on the BugsnagConfiguration class. In addition, the default number of breadcrumbs saved has been raised to 25 and limited to no more than 100.
• BugsnagConfiguration.autoNotify is now named BugsnagConfiguration.autoDetectErrors
• BugsnagConfiguration.autoCaptureSessions is now named BugsnagConfiguration.autoDetectSessions

5.22.10 (2019-11-04)

Bug fixes

• Fix unrecognized selector crash when adding metadata #430

5.22.9 (2019-10-16)

Bug fixes

• Fix a packaging issue when using Carthage, introduced in 5.22.7. Note: There is a remaining known issue when updating/building the bugsnag-cocoa dependency with Carthage, the project will build three times before completing successfully. This issue will be resolved in a subsequent patch release. #423

• Deprecate config.reportBackgroundOOMs property - designating any app termination as a possible error condition can cause a lot of false positives, especially since the app can die for many genuine reasons, especially when running only in the background. #425

5.22.8 (2019-10-10)

Bug fixes

• Fix use-after-free in notify() logic which could lead to a deadlock #420
• Reduce severity of log message about thread status from 'error' to 'debug' as it does not necessarily indicate a problem and is only used for debugging. #421

5.22.7 (2019-10-03)

Bug fixes

• Show correct value for app.inForeground when an app launches and crashes in the background without ever coming to the foreground. #415
• Fix improperly retained properties which could result in a crash due to premature deallocation #416

5.22.6 (2019-09-18)

Enhancements

• Support disabling crash reporting after initialization by setting Bugsnag.configuration.autoNotify. Previously this value was ignored after Bugsnag.start() was called, but is now used to update whether crash reports will be detected and sent. This interface can be used for crash reporting opt-out flows. #410

Bug fixes

• Ensure UIKit APIs are not called from background threads if Bugsnag.start() is called in the background #409
• Fix bug in notifyReleaseStages where if the release stage of a build was changed after start(), only the initial value was used to determine whether to send a report #405 #412

5.22.5 (2019-08-14)

Bug fixes

• Fix possible crash or deadlock arising from calling Bugsnag.notify() from multiple queues concurrently. #401

5.22.4 (2019-07-30)

Bug fixes

• Support adding pre-delivery metadata to out-of-memory reports #393
• Fix erroneously reporting out-of-memory events from iOS app extensions #394
• Fix erroneously reporting out-of-memory events when an iOS app is in the foreground but inactive #394
• Fix erroneously reporting out-of-memory events when the app terminates normally and is issued a "will terminate" notification, but is terminated prior to the out-of-memory watchdog processing the notification #394
• Fix memory leak in notify() Carolina Aguilar #395

5.22.3 (2019-07-15)

This release disables reporting out-of-memory events in debug mode, to reduce false positives.

Bug fixes

• Fix incrementing unhandled counts when using internal notify() API. This resolves discrepancies in stability scores for users of bugsnag-react-native after receiving unhandled JavaScript events.
• Fix JSON parsing errors in crash reports for control characters and some other sequences

5.22.2 (2019-06-13)

Bug fixes

• Fix trimming the stacktraces of handled error/exceptions using the depth property. Paul Zabelin #363
• Fix crash report parsing logic around arrays of numbers. Metadata which included arrays of numbers could previously had missing values. #365

5.22.1 (2019-05-21)

• 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

5.22.0 (2019-05-09)

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

5.21.0 (2019-05-01)

Enhancements

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

5.20.0 (2019-04-11)

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

5.19.1 (2019-03-27)

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

5.19.0 (2019-02-28)

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

5.18.0 (2019-02-21)

Enhancements

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

5.17.3 (2018-12-19)

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

5.17.2 (2018-12-05)

• Add Device time of report capture to JSON payload #315

5.17.1 (2018-11-29)

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

5.17.0 (2018-09-25)

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

5.16.4 (13 Sept 2018)

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.

5.16.3 (14 Aug 2018)

Bug Fixes

• Deregister notification observers and listeners before application termination #301

5.16.2 (17 Jul 2018)

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

5.16.1 (11 Jul 2018)

Bug Fixes

• Respect appVersion override when serialising KSCrash report #292

5.16.0 (02 Jul 2018)

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

5.15.6 (30 May 2018)

Bug Fixes

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

5.15.5 (25 Apr 2018)

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

5.15.4 (21 Feb 2018)

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-addapp 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

5.15.3 (23 Jan 2018)

Bug Fixes

• Remove chatty logging from session tracking #231 Jamie Lynch
• Re-add API key to payload body to preserve backwards compatibility with older versions of the error reporting API #232 Jamie Lynch
• Fix crash in iPhone X Simulator when reporting user exceptions #234 Paul Zabelin
• Improve capture of Swift assertion error messages on arm64 devices, inserting the assertion type into the report's errorClass #235

5.15.2 (11 Jan 2018)

Bug Fixes

• Fix default user/device ID generation on iOS and tvOS devices
• Fix mach exception detection

5.15.1 (09 Jan 2018)

• Misc Session Tracking fixes and enhancements

5.15.0 (05 Jan 2018)

• • Adds support for tracking sessions and overall crash rate by setting config.shouldAutoCaptureSessions to true. In addition, sessions can be indicated manually using [Bugsnag startSession] #222

5.14.2 (15 Dec 2017)

Bug Fixes

• Fix possible crash when reading invalid JSON files from disk #220 #218

5.14.1 (29 Nov 2017)

• Fix encoding of control characters in crash reports. Ensures crash reports are written correctly and delivered when containing U+0000 - U+001F #214 Jamie Lynch

5.14.0 (23 Nov 2017)

• Use BSG_KSCrashReportWriter header rather than KSCrashReportWriter for custom JSON serialization

5.13.5 (21 Nov 2017)

• Remove misleading information (address, mach, signal) from non-fatal error reports

5.13.4 (16 Nov 2017)

• Fix buffer overflow for reports with large metadata
• Treat warnings as errors

5.13.3 (06 Nov 2017)

• Fix build on older versions of XCode

5.13.2 (02 Nov 2017)

• Fix thread safety issue in breadcrumbs API
• Allow setting device ID in report to null
• When notifying of NSError, use the code and domain as the default context
• Fix for wrong report context in some unhandled errors

5.13.1 (26 Oct 2017)

• Additional method prefixing
• Prevent possible memory leak in connectivity check

5.13.0 (12 Oct 2017)

• Update podspec iOS version to 8.0
• Updated example apps to Swift 4
• Report error message for Swift's fatalError, preconditionFailure, assertionFailure, and assert.

5.12.1 (04 Oct 2017)

• Fix duplicate symbols in KSCrash when Sentry library included in project

5.12.0 (02 Oct 2017)

• Fix fatalError not producing crash report
• Update library's calculation of stack frame depth
• Reduced build warning count
• Track difference between handled and unhandled exceptions #164 Jamie Lynch

5.11.2 (15 Sep 2017)

• Fixed wrong tag in Cocoapods spec

5.11.1 (14 Sep 2017)

• Fixed issue with header file visibility

5.11.0 (14 Sep 2017)

• Update example apps to use Swift 3 syntax
• Discard duplicate automatic breadcrumbs recording orientation changes
• Map NSNotification keys in breadcrumbs into more human-readable strings
• Attempt to send reports stored on disk when connection regained
• Forked KSCrash library
• Improve performance in Bugsnag.notifyError Eric Denman

5.10.1 (08 Jun 2017)

Bug fixes

• Fix warning generated by checking for existence of a property guaranteed when deployment target is iOS 8.0+ Scott Berrevoets #147

5.10.0 (22 May 2017)

Enhancements

• Sanitize attached metadata to remove objects which cannot be serialized as JSON directly, logging during removal
• Make breadcrumb functionality available for background operations

Bug fixes

• Lower effective deployment targets from iOS 8 and OS X 10.10 to iOS6 and OS X 10.8

5.9.0 (08 May 2017)

Enhancements

• Adds methods to BugsnagCrashReport for appending metadata, simplifying making the most common changes from a callback block #145

Bug fixes

• Fix linking failure when using Bugsnag with Carthage on tvOS #139

5.8.0 (21 Apr 2017)

This release downgrades the dependent KSCrash version to 1.8.13, reverting the change to the signature of KSCrashReportWriter.addJSONElement() in 5.7.0. This change only affects users setting a custom onCrash handler to be executed at crash time.

Enhancements

• Increases the number of crash reports stored on disk before cycling
• Make logging configurable by setting BSG_LOG_LEVEL. Default is BSG_LOGLEVEL_INFO, and available values include WARN and ERR variants.

Bug fixes

• Fixes deadlock which can occur when repeatedly calling notify #143
• Fixes periodic issue where no report is captured at all
• Fixes issue where a report written at crash time cannot be deserialized from disk at send time.

5.7.0 (30 Jan 2017)

This release updates the dependent KSCrash version to 1.11.2, which changes the signature of KSCrashReportWriter.addJSONElement() to include whether to close the JSON container.

Enhancements

• Add support for customizing the NSURLSession used when sending error reports to Bugsnag #127

5.6.5 (7 Nov 2016)

Bug fixes

• Fix assignment of beforeSendBlocks to incorrect property name Spike Brehm #125

5.6.4 (7 Nov 2016)

Miscellaneous

• Expose app, appState, device, deviceState, and error to crash report callback blocks

5.6.3 (21 Oct 2016)

Bug fixes

• Fix autoNotify: Disabling unhandled exception capturing only sends user-reported exceptions via Bugsnag.notify()

5.6.2 (10 Oct 2016)

Bug fixes

• Update imports to be compatible with KSCrash 1.8.8+
• Lock KSCrash dependency to 1.8.13 to reduce instability

5.6.1 (05 Oct 2016)

Miscellaneous

• Include thread type in payload to match new payload specification

5.6.0 (26 Sep 2016)

Enhancements

• Add support for attaching a custom stacktrace to an error report
• Upgrade required version of KSCrash

5.5.0 (14 Sep 2016)

Enhancements

• Add "Require Only App-Extension-Safe API" flag for iOS App Extension support
• Send requests via NSURLSession by default

5.4.2 (17 Aug 2016)

Bug fixes

• Fix a condition where bug reports would be sent multiple times

5.4.1 (27 Jul 2016)

Bug fixes

• Fix breadcrumb type for table events
• Add error message and severity to error breadcrumbs
• Make breadcrumbs accessible from background queues

5.4.0 (22 Jul 2016)

Enhancements

• Add support for automated breadcrumb collection for common events and the new breadcrumbs API #112

• Add support for Apple TV #113

• Add ability to customize error reports via notify:block #110

• Add support for sending reports for NSError instances via notifyError: and notifyError:block: #110

• Add crash time to the "Device" tab of error reports #110

5.3.0 (15 Jul 2016)

Bug fixes

• Fix intermittent crashes via NSZombie detection being enabled by default #111 KSCrash#160

5.2.1 (16 June 2016)

Add Carthage support

5.2.0 (2 June 2016)

Bug Fixes

• Catch JSON (de)serialization exceptions thrown from NSJSONSerialization

Enhancements

• Add nullability annotations
• Remove logging when no reports were sent

5.1.0

Bug Fixes

• Fix build failure when building with frameworks #101

Enhancements

• Add support for iOS Application Extensions #100

5.0.2

Bug Fixes

• Fix typo in updated payload date format. Should instead use RFC 3339 format

5.0.1

Bug Fixes

• Fix header issue when linking to Bugsnag via CocoaPods from within another pod #98 #99
  • Related to: CocoaPods#4420

5.0.0

This release includes an upgrade to KSCrash 1.0.0, as well support for running alongside other KSCrash-dependent libraries. Crash handling for heap corruption and link register overwriting has also been improved.

NOTE: The minimum supported iOS and OS X versions have been updated to 6.0 and 10.8 respectively.

Bug Fixes

• Fix for occasional crash when logging from a failed network request #67

• Fix conflict when used alongside other KSCrash-dependent libraries #41 #52 #72 #91 #94

• Fix for failed crash reports being deleted instead of resent #76

Enhancements

• Bitcode support #78

• Include breadcrumbs in uncaught exception reports #78 #86

• Include severity in uncaught exception reports #86

• Add pre- and post-crash hooks, for modifying or rejecting crash reports #17 #47 #34 #88

• Swift demangling support #70 #96

4.1.0

• Breadcrumbs support.
• Send notifications with current configuration rather than that in the report.

4.0.9

• Protect against nil named exceptions

4.0.8

• Reduce deployment target to 4.3
• Catch less crashes on OSX

4.0.7

• Fix compilation on arm64 under Unity

4.0.6

• Uncaught exceptions in OSX are now marked as warnings

4.0.5

• Fix buffer over-read in JSON parser

4.0.4

• Build OSX framework as part of release

4.0.3

• In dealloc remove notifier from notifications

4.0.2

• Make metaData access thread-safe

4.0.1

• Fix warning while compiling KSCrash on OS X

4.0.0

• Rewrite to use KSCrash as a solid foundation

3.1.3

• Add [Bugsnag notify:withMetaData:atSeverity:] to public API

3.1.2

• Prepare 'severity' feature for release

3.1.1

• Package BugsnagReachability in package for reliability

3.1.0

• Disable dsym uploading on iphonesimulator builds
• Send better diagnostics with a better format

3.0.1

• Remove Pods from repo.
• Fix XCode5 Warnings.
• Publicise the notifier method.

3.0.0

• Complete rewrite to support symbolication.
• Support iOS and OSX.