All Versions
Latest Version
Avg Release Cycle
12 days
Latest Release
100 days ago

Changelog History
Page 11

  • v5.22.10 Changes

    November 04, 2019

    ๐Ÿ› Bug fixes

    • ๐Ÿ›  Fix unrecognized selector crash when adding metadata
  • v5.22.9 Changes

    October 16, 2019

    ๐Ÿ› 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.
    • ๐Ÿ—„ 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.
  • v5.22.8 Changes

    October 10, 2019

    ๐Ÿ› Bug fixes

    • ๐Ÿ›  Fix use-after-free in notify() logic which could lead to a deadlock
    • โฌ‡๏ธ 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.
  • v5.22.7 Changes

    October 03, 2019

    ๐Ÿ› Bug fixes

    • ๐Ÿ‘‰ Show correct value for app.inForeground when an app launches and crashes in
      the background without ever coming to the foreground.
    • ๐Ÿ›  Fix improperly retained properties which could result in a crash due to
      premature deallocation
  • v5.22.6 Changes

    September 18, 2019

    โœจ 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
  • v5.22.5 Changes

    August 14, 2019

    ๐Ÿ› Bug fixes

    • ๐Ÿ›  Fix possible crash or deadlock arising from calling Bugsnag.notify() from
      multiple queues concurrently.
  • v5.22.4 Changes

    July 30, 2019

    ๐Ÿ› 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 Changes

    July 15, 2019

    ๐Ÿš€ 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 Changes

    June 13, 2019

    ๐Ÿ› 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
  • v5.22.1 Changes

    May 21, 2019
    • 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