Skip to content

Releases: bugsnag/bugsnag-unity

v4.4.0

05 Apr 14:52
296e47c

Choose a tag to compare

Enhancements

Bug fixes

  • Update bugsnag-android dependency to v4.13.0:

  • Update bugsnag-cocoa dependency to v5.19.1:

    • 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 from notify() will now use the NSException
      instance's call stack addresses to construct the stacktrace, ignoring depth.
      This fixes an issue in macOS exception reporting where reportException is
      reporting the handler code stacktrace rather than the reported exception
      stack.
      bugsnag-cocoa#334

    • Fix network connectivity monitor by connecting to the correct domain
      Jacky Wijaya
      bugsnag-cocoa#332

v4.3.0

14 Mar 20:04

Choose a tag to compare

This release is the first to distribute Unity packages with and without 64-bit
ABI libraries for Android. In most cases, Bugsnag.unitypackage is the correct
package to use, as by default most Unity Android apps only can use 32-bit
binaries.

Enhancements

  • Add StopSession() and ResumeSession() to public API
    #136

  • Update bugsnag-android dependency to v4.11.0:

  • Update bugsnag-cocoa dependency to v5.19.0:

    • Add stopSession() and resumeSession() to Bugsnag
      bugsnag-cocoa#325
    • Capture basic report diagnostics in the file path in case of crash report
      content corruption
      bugsnag-cocoa#327

Bug fixes

  • Ensure session and user information is included in native crash reports
    #138
    bugsnag-cocoa#333
    bugsnag-android#439

  • [Android] Remove references to 64-bit ABIs included in the package
    #139

  • Make ErrorClass and ErrorMessage mutable on Exception. This allows for
    modifying both properties from callbacks:

    Bugsnag.Notify(exception, report => {
      report.Exceptions[0].ErrorClass = "CustomException";
      report.Exceptions[0].ErrorMessage = "something notable";
    });

    #140

  • Set severity reason when manually specifying severity as a parameter to
    Notify(). This sets the correct reason for the severity selection on the
    dashboard.
    #140

v4.2.2

26 Feb 17:18

Choose a tag to compare

Bug fixes

  • (Android) Fix a crash which could occur if large amounts of metadata or
    breadcrumbs (>500 key/value pairs) are attached at once, or if Notify() is
    called concurrently several times.
    #132

v4.2.1

21 Feb 19:51

Choose a tag to compare

Bug fixes

  • Ensure a stacktrace is attached to reports without underlying exceptions, such
    as log messages using an 'error' or 'warning' level
    #131

v4.2.0

07 Feb 19:20

Choose a tag to compare

Enhancements

  • Add support for detecting and reporting Android NDK C/C++ crashes
    #127

v4.1.3

01 Feb 19:58

Choose a tag to compare

4.1.3 (2019-02-01)

Bug fixes

  • Ensure configuration options are synced with native layer
    #124

  • Add retry delays after delivery failure to stop excess logging
    #126

v4.1.2

23 Jan 14:27

Choose a tag to compare

Bug fixes

Update bugsnag-android dependency to v4.11.0:

  • 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

v4.1.1

21 Jan 20:04

Choose a tag to compare

Bug fixes

  • Lower minimum supported iOS version to 8.0 from 9.0
  • Lower minimum supported macOS version to 10.8 from 10.11

v4.1.0

11 Jan 19:27
c536568

Choose a tag to compare

  • Update dependent libraries:
    • bugsnag-cocoa v5.17.3
    • bugsnag-android v4.10.0

Enhancements

Bug fixes

  • Fix exception parsing for Android Java exceptions to ensure correct grouping,
    "handled"-ness, and remove extraneous stack frame from the top of the
    backtrace.
  • Fix off-by-one error in event counts in the session tracking implementation

v4.0.0

20 Nov 05:24

Choose a tag to compare

This is a new major release with many features and fixes. See the upgrade
guide
for
more information on how to update your integration, or the integration
guide
to get started.

Enhancements

  • Unity/C# errors are now automatically detected and reported on Windows and any
    other Unity platform (not including native crashes)
  • Exceptions logged on background threads via the Unity Debug.Log API are
    now automatically detected and reported in additional to exceptions detected
    on the main thread.
  • Support for session and stability tracking
  • Support for logging detailed breadcrumbs