Releases: bugsnag/bugsnag-react-native
v2.20.0
This release updates the package's Gradle build script to use api and implementation rather than the deprecated
compile syntax. If you are using v2.X of the Android Gradle Plugin, you will need to upgrade to v3.X of
the Android Gradle Plugin,
and upgrade your gradle wrapper.
-
Update deprecated compile dependencies to use implementation/api
#362 -
Remove unnecessary gradlew from android directory, reducing artefact bundle size
#363
Bug fixes
- Remove nullability annotations to workaround androidx jetifier issue
#361
v2.19.1
Bug fixes
- (iOS) Upgrade to bugsnag-cocoa v5.22.1:
- (Android) Upgrade to bugsnag-android v4.14.2
- Disable ANR detection by default #484
v2.19.0
Enhancements
- (iOS) Upgrade to bugsnag-cocoa v5.22.0:
- Add configuration option (
reportOOMs) to disable out-of-memory (OOM) event
reporting, defaulting to enabled.
bugsnag-cocoa#345 - Disable background OOM reporting by default. It can be enabled using
reportBackgroundOOMs.
bugsnag-cocoa#345
- Add configuration option (
v2.18.0
v2.17.1
Re-release that fixes packaging issue where the previous artefact included duplicate header files, preventing compilation for iOS
v2.17.0
Bug fixes
- (iOS) Prevent delivering duplicate fatal JS crash reports when using enhanced
native integration.
#337
Enhancements
- (iOS) Upgrade to bugsnag-cocoa v5.20.0:
- 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
- Persist breadcrumbs on disk to allow reading upon next boot in the event of
v2.16.0
-
(Android) Upgrade to bugsnag-android v4.13.0
Enhancements
Bug fixes
-
(Cocoa) Upgrade to bugsnag-cocoa v5.19.1
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 fromnotify()will now use theNSException
instance's call stack addresses to construct the stacktrace, ignoring depth.
This fixes an issue in macOS exception reporting wherereportExceptionis
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
-
v2.15.0
-
Add stopSession() and resumeSession() to Client #314
-
(Android) Upgrade to bugsnag-android v4.12.0
Enhancements
- Add stopSession() and resumeSession() to Client
#429
Bug fixes
- Add stopSession() and resumeSession() to Client
-
(Cocoa) Upgrade to bugsnag-cocoa v5.19.0
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
- Update workspace to recommended settings suggested by XCode 10
v2.14.0
-
(Android) Upgrade to bugsnag-android v4.11.0
Enhancements
-
[NDK] Improve support for C++ exceptions, adding the exception class name
and description to reports and improving the stacktrace quality
#412 -
Update vendored GSON dependency to latest available version
#415
Bug fixes
-
Fix cached error deserialisation where the Throwable has a cause
#418 -
Refactor error report deserialisation
#419 -
Fix unlikely initialization failure if a device orientation event listener
cannot be enabled -
Cache result of device root check
#411 -
Prevent unnecessary free disk calculations on initialisation
#409
-