Skip to content

Releases: bugsnag/bugsnag-js

v7.16.3

05 Apr 09:19
Compare
Choose a tag to compare

Changed

  • (react-native) Update bugsnag-android to v5.22.0
    • The number of threads reported can now be limited using Configuration.setMaxReportedThreads (defaulting to 200)
      bugsnag-android#1607
    • Improved the performance and stability of the NDK and ANR plugins by caching JNI references on start
      bugsnag-android#1596
      bugsnag-android#1601
    • Fix inconsistencies in stack trace quality for C/C++ events. Resolves a few
      cases where file and line number information was not resolving to the correct
      locations. This change may result in grouping changes to more correctly
      highlight the root cause of an event.
      bugsnag-android#1605
      bugsnag-android#1606
    • Fixed an issue where an uncaught exception on the main thread could in rare cases trigger an ANR.
      bugsnag-android#1624
    • Added Bugsnag.isStarted() to test whether the Bugsnag client is in the middle of initializing. This can be used to guard uses of the Bugsnag API that are either on separate threads early in the app's start-up and so not guaranteed to be executed after Bugsnag.start has completed, or where Bugsnag may not have been started at all due to some internal app logic.
      slack-jallen:#1621
      bugsnag-android#1640
    • Events and Sessions will be discarded if they cannot be uploaded and are older than 60 days or larger than 1MB
      bugsnag-android#1633
    • Fixed potentially thread-unsafe access when invoking Bugsnag static methods across different threads whilst Bugsnag.start is still in-flight. It is now safe to call any Bugsnag static method once Bugsnag.start has begun executing, as access to the client singleton is controlled by a lock, so the new isStarted method (see above) should only be required where it cannot be determined whether the call to Bugsnag.start has begun or you do not want to wait.
    • bugsnag-android#1638
    • Calling bugsnag_event_set_context with NULL context correctly clears the event context again
      bugsnag-android#1637

Fixed

  • (plugin-express): send the request body (if present) as event.request.body rather than event.metadata.request.body #1702
  • (plugin-restify): Include request body #1701

v7.16.2

09 Mar 11:24
Compare
Choose a tag to compare

Fixed

  • (expo): preliminary support for Expo EAS Update. Please send us feedback on how we can improve our support! kennethlynne #1686 #1695

Changed

  • (plugin-react-navigation): Allow React Navigation v6 as a peer dependency #1691

v7.16.1

02 Feb 13:15
Compare
Choose a tag to compare

Fixed

  • (react-native) Handle circular references in metadata before it's sent to the native notifier layer #1673

Changed

v7.16.0

25 Jan 13:53
Compare
Choose a tag to compare

Added

Changed

v7.15.1

18 Jan 18:06
Compare
Choose a tag to compare

Changed

v7.15.0

18 Jan 15:18
Compare
Choose a tag to compare

This release is broken and has been deprecated on npm

v7.14.2

05 Jan 14:00
Compare
Choose a tag to compare

Fixed

  • (react-native-cli): Fix Xcode build error for ejected Expo apps #1623

Changed

  • (react-native) Update bugsnag-android to v5.17.0
  • (react-native): Update bugsnag-cocoa to v6.15.1
    • Load configuration from the plist instead of using defaults when calling Bugsnag.start(withApiKey:) #1245
    • Include metadata in breadcrumbs for UIWindow / NSWindow notifications. #1238
    • Use LC_FUNCTION_STARTS to improve symbolication accuracy. #1214

v7.14.1

29 Nov 17:08
Compare
Choose a tag to compare

Fixed

  • (plugin-network-breadcrumbs): Fix a crash when request URL is not a string #1598
  • (in-flight): Fix Typescript definition exporting a type instead of a value skirsten #1587
  • (plugin-electron-net-breadcrumbs): Don't leave breadcrumbs for requests to the minidumps endpoint #1597
  • Add a default export to plugins that were missing one #1599

v7.14.0

17 Nov 13:52
Compare
Choose a tag to compare

This release adds support for reporting native crashes to @bugsnag/electron.

If you are using modules with native extensions, you can upload Breakpad symbol files to Bugsnag to symbolicate native errors.

Note: Bugsnag On-premise does not currently support uploading minidump files. This will be supported in an upcoming release.

  • (electron): Add support for reporting native crashes #1581

v7.13.3

09 Nov 09:06
Compare
Choose a tag to compare

Fixed

  • (plugin-network-breadcrumbs): Fix a crash when request data goes missing #1564

Changed

  • (expo): Add support for Expo SDK v43 foolem #1556 / #1566
  • (react-native): Update bugsnag-cocoa to v6.14.2
    • Fix missing configuration.user and manually resumed session info in unhandled errors. bugsnag-cocoa#1215
    • Disable automatic session tracking in app extensions (it was not working as intended.) bugsnag-cocoa#1211
    • Stop logging "[ERROR] Failed to install crash handler..." if a debugger is attached. bugsnag-cocoa#1210
    • Include the word "request" in network request breadcrumb messages. bugsnag-cocoa#1209
    • Prevent a crash that can occur when -[BSGURLSessionTracingProxy forwardInvocation:] calls -[NSInvocation selector]. bugsnag-cocoa#1208
    • Apply redactedKeys to breadcrumb metadata. bugsnag-cocoa#1204
  • (react-native): Update bugsnag-android to v5.15.0
    • Avoid reporting false-positive background ANRs with improved foreground detection. bugsnag-android#1429
    • Prevent events being attached to phantom sessions when they are blocked by an OnSessionCallback. bugsnag-android#1434
    • Plugins will correctly mirror metadata added using addMetadata(String, Map). bugsnag-android#1454