v5.23.0

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

v5.22.10

Bug fixes

• Fix unrecognized selector crash when adding metadata
  #430

v5.22.9

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 in Xcode 11 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

v5.22.8

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

v5.22.7

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

v5.22.6

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

• 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

v5.22.5

Bug fixes

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

v5.22.4

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

v5.22.3

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

v5.22.2

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