Bugsnag React Native Versions Save

Error monitoring and reporting tool for native exceptions and JS errors in React Native apps

v2.23.10

3 years ago

Bug fixes

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

  • (iOS) Move binary images store declaration from header file #725

  • (iOS) Avoid dereference null pointer in JSON serialisation #637 Naugladur

v2.23.9

3 years ago

Bug fixes

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

v2.23.8

3 years ago

Bug fixes

  • Fix missing comma in podspec headers list #456

  • (iOS) Fix an issue where an app could deadlock during a crash if unfavorable timing caused DYLD lock contention. #580

v2.23.7

4 years ago

Bug fixes

  • Add missing BugsnagPlugin.h header to podspec file #450

v2.23.6

4 years ago
  • (iOS) Fix include for RCTVersion.h to work in custom Podfiles on all versions of React Native #443

  • Add missing argument to BeforeSend type definition bugsnag-react-native#432

  • (Android) Upgrade bugsnag-android to v4.22.3

    • Allow disabling previous signal handler invocation for Unity ANRs #743
    • Avoid polling when detecting ANRs by invoking JNI from SIGQUIT handler #741
  • (iOS) Upgrade bugsnag-cocoa to 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

v2.23.5

4 years ago

Bug fixes

  • (iOS) Fix a packaging issue introduced in 2.23.3 which prevented apps using React Native 0.59 and below from building successfully #441

v2.23.4

4 years ago

Bug fixes

  • (Android) Upgrade bugsnag-android to v4.22.2
    • Fix: address CVE-2019-10101 by increasing Kotlin version to 1.3.61 #739
    • Catch throwables when invoking methods on system services #623
    • Fix possible crash when recording reports and breadcrumbs containing values using different text encodings or UTF-8 control characters, followed by a C/C++ crash. #584
    • Fix crash when calling NativeInterface.clearTab() (from an integration library) #582
    • Fix abort() in native code when storing breadcrumbs with null values in metadata #510
    • Fix potential segfaults when adding breadcrumb with NDK #546
    • Convert metadata to map when notifying the NDK observer #513
    • Prevent overwrite of signal mask when installing ANR handler #520
    • Fix possible null pointer exception when creating a breadcrumb without metadata #585

v2.23.3

4 years ago

Bug fixes

  • Use the correct android version in Notifier payload bugsnag-react-native#409
  • (Android) Upgrade bugsnag-android to v4.21.1
    • Allow overriding the versionCode via Configuration bugsnag-android#610
    • Delete cached error reports if an Exception is thrown during disk IO, preventing delivery of empty/partial reports on the next app launch. bugsnag-android#609
    • Prevent internal error reporting of FileNotFoundException during serialization bugsnag-android#605
  • (iOS) Upgrade bugsnag-cocoa to v5.22.10
    • Fix unrecognized selector crash when adding metadata bugsnag-cocoa#430
    • 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. bugsnag-cocoa#425
    • Fix use-after-free in notify() logic which could lead to a deadlock bugsnag-cocoa#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. bugsnag-cocoa#421
    • Show correct value for app.inForeground when an app launches and crashes in the background without ever coming to the foreground. bugsnag-cocoa#415
    • Fix improperly retained properties which could result in a crash due to premature deallocation bugsnag-cocoa#416

v2.23.2

4 years ago

Bug fixes

  • (Android) Upgrade bugsnag-android to v4.20.0

    • Buffer IO when reading from cached error files, improving SDK performance bugsnag-android#573
    • Fix freeDisk calculation to show free space rather than total space bugsnag-android#589
    • Fix duplicate reports possibly being sent when many launch crashes are delivered in low connectivity situations bugsnag-android#593
  • (iOS) Upgrade bugsnag-cocoa to v5.22.6

    • Ensure UIKit APIs are not called from background threads when initializing only in the JavaScript layer when using [email protected]+ #396
    • 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 bugsnag-cocoa#405 bugsnag-cocoa#412

v2.23.1

4 years ago

Bug fixes

  • (Android) Upgrade to bugsnag-android v4.19.1
    • Fix deserialization of custom stackframe fields in cached error reports #576

    • Fix potential null pointer exception if setMetaData is called with a null value