Version 3.3.0

Version 3.3.0

• BacktraceReport stack trace now includes the file name of the stack frame.
• Performance improvements:
  • JSON algorithm performance improvements - avoid analyzing data types.
  • improved library attributes management.
  • improved Unity logs management.
• Support for Low Memory error reports on Android and iOS (these are sometimes referred to as OOM or Out Of Memory errors). If a low memory situation is detected, backtrace-unity will attempt to generate and submit a native error report to the Backtrace instance. The report will have the error.type value of Low Memory.
• New support for hang detection on Android and iOS. If a game experiences non responsiviness after 5 seconds, backtrace-unity will generate an error report to the Backtrace instance. The report will have the error.type value of Hang.

Version 3.2.6

Version 3.2.6

• BacktraceClient will apply sampling only to errors lacking exception information.
• Fixed annotations nullable value.
• Renamed BacktraceUnhandledException classifier to error.
• Fixed nullable environment annotation value.

Version 3.2.4

Version 3.2.4

• Fixed Backtrace-Unity NDK integration database path.

Version 3.2.3

Version 3.2.3

• Backtrace offline database will now store 8 reports by default. Previously this was not set by default.
• HTTP client communication improvements
• Improvements in UPM
• Updated symbolication strategy on iOS crashes

Version 3.2.2

Version 3.2.2

• Fixed native iOS attributes

Version 3.2.1

Version 3.2.1

• Android stack trace parser improvements,
• Fixed Android NDK initialization when database directory doesn't exist,
• Added Privacy section to Readme

Version 3.2.0

Version 3.2.0

• This release adds the ability to capture native iOS crashes from Unity games deployed to iOS. The Backtrace Configuration now exposes a setting for games being prepared for iOS to choose Capture native crashes. When enabled, the backtrace-unity client will capture and submit native iOS crashes to the configured Backtrace instance. To generate human readable callstacks, game programmers will need to generate and upload appropriate debug symbols.
• Added default uname.sysname attributes for some platforms. The following is the list of uname.sysname platforms that can be populated. list "Android, IOS, Linux, Mac OS, ps3, ps4, Samsung TV, tvOS, WebGL, WiiU, Switch, Xbox". Note 'Switch' had previously been reported as 'switch'
• Added a new attribute 'error.type' that allows developers to quickly filter error reports based on the type of error - The list includes "Crash, Message, Hang, Unhandled Exception, Exception".
• Updated Android NDK libraries used by Unity plugin.

Version 3.2.0-release candidate 3

Version 3.2.0-release candidate

• This release adds the ability to capture native iOS crashes from Unity games deployed to iOS. The Backtrace Configuration now exposes a setting for games being prepared for iOS to choose Capture native crashes. When enabled, the backtrace-unity client will capture and submit native iOS crashes to the configured Backtrace instance. To generate human readable callstacks, game programmers will need to generate and upload appropriate debug symbols.
• Added default uname.sysname attributes for some platforms. The following is the list of uname.sysname platforms that can be populated. list "Android, IOS, Linux, Mac OS, ps3, ps4, Samsung TV, tvOS, WebGL, WiiU, Switch, Xbox". Note 'Switch' had previously been reported as 'switch'
• Added a new attribute 'error.type' that allows develo

Version 3.1.2

Version 3.1.2

• BacktraceData allows to edit list of environment variables collected by BacktraceAnnotations
• SourceCode object description for PII purpose
  Annotationsclass exposes EnvironmentVariableCache dictionary - dictionary that stores environment variables collected by library. For example - to replaceUSERNAME` environment variable collected by Backtrace library with random string you can easily edit annotations environment varaible and Backtrace-Untiy will reuse them on report creation.

Annotations.EnvironmentVariablesCache["USERNAME"] = "%USERNAME%";

Also you can still use BeforeSend event to edit collected diagnostic data:

  client.BeforeSend = (BacktraceData data) =>
  {
      data.Annotation.EnvironmentVariables["USERNAME"] = "%USERNAME%";
      return data;
  }

Version 3.2.0-release candidate 2

Version 3.2.0-release candidate

This release adds the ability to capture native iOS crashes from Unity games deployed to iOS. The Backtrace Configuration now exposes a setting for games being prepared for iOS to choose Capture native crashes. When enabled, the backtrace-unity client will capture and submit native iOS crashes to the configured Backtrace instance. To generate human readable callstacks, game programmers will need to generate and upload appropriate debug symbols.