Version 3.0.1

Version 3.0.1

• The BacktraceDatabase class will now create database directory before final database validation. Previously, when directory didn't exist, BacktraceDatabase was disabled.
• The BacktraceDatabase field now allows users to pass interpolated string in Database options. Developer can use ${Application.dataPath} or ${Application.persistentDataPath} to set path to database.
• The backtrace-unity library will generate screenshot image files in .jpg format.
• Optimizations in ANR watchdog and BacktraceLogManager initialization - The Backtrace client will now create a class instance of BacktraceAnrWatchdog class, instead of creating instance via static class method. The BacktraceLogManager (class responsible for storing log data) will be initialized in CaptureUnityMessages.

Version 3.0.0

Version 3.0.0

New Features

• The backtrace-unity library (Backtrace) now allows detection of ANR (Application not responding) events on Android devices.
• Unhandled exception output from the Unity runtime and executables is now prominently displayed in the Debugger.
• Backtrace will try to guess unhandled exception classifier based on exception message/stack trace.
• Backtrace now allows you to add Unity player.log file as an attachment.
• Backtrace now allows you to add a screenshot as an attachment when an exception occured.
• Backtrace now allows you to capture last n lines of game logs. You can define how many lines of logs Backtrace should store by settings Collect last n number of logs property in the Unity editor.
• Backtrace will capture any native Unity Engine crash dumps on Windows OS.
• Backtrace will capture and index native metadata from the Android OS as Backtrace Attribuces, including vm, system.memory, and device details.
• Backtrace allows you control whether or not a report should send via the BeforeSend event. If you return a null value from a BeforeSend event, Backtrace will discard the report and not send.

General Improvements

• BacktraceClient, BacktraceReport, BacktraceData, BacktraceData and BacktraceDatabase now allow users to pass attributes in dictionary form with string key and string values. Attributes must now be provided with the Dictionary<string, string> data structure to allow the serializer to be as fast as possible.
• Removed dependancy on 3rd party JSON.NET library to reduce the size of the package. Backtrace-unity now provides it's own serializer for BacktraceReport usage.
• Further reduction in size of Backtrace.Unity assembly with BacktraceJObject.
• BacktraceDatabase won't try to deserialize BacktraceReport anymore - because of that, callback api won't return BacktraceReport object in BacktraceResult.
• BacktraceDatabase won't use anymore Add method with BacktraceReport parameter. Instead, BacktraceDaatabase will use Add method with BacktraceData parameter. Previous Add method is deprecated and will be removed in next major release.
• Support has been improved for parsing unhandled exception output from the Unity runtime and Unity executables.

NOTE: When migrating from previous releases, there is an API change that developers will want to uptake for attribute submission. Specifically, attribute definitions previously used a signature
attributes: new Dictionary<string, object>() { { "key", "value" } },
In this release, we made a change to require a string for the value instead of an object for faster performance.
attributes: new Dictionary<string, string>() { { "key", "value" } },

Bug Fixes

• Annotation name typo - updated children from childrens

3.0.0-release-candidate

Version 3.0.0

New Features

• The backtrace-unity library (Backtrace) now allows detection of ANR (Application not responding) events on Android devices.
• Unhandled exception output from the Unity runtime and executables is now prominently displayed in the Debugger.
• Backtrace will try to guess unhandled exception classifier based on exception message/stack trace.
• Backtrace now allows you to add Unity player.log file as an attachment.
• Backtrace now allows you to add a screenshot as an attachment when an exception occured.
• Backtrace will now allow you to capture last n lines of game logs. You can define how many lines of logs Backtrace should store by settings Collect last n number of logs property in the Unity editor.
• Backtrace will send the native Unity exception that caused a crash of game on Windows OS.
• Backtrace allows you control whether or not a report should send via the BeforeSend event. If you return a null value from a BeforeSend event, Backtrace will discard the report and not send.

General Improvements

• BacktraceClient, BacktraceReport, BacktraceData, BacktraceData and BacktraceDatabase now allow users to pass attributes in dictionary form with string key and string values. Attributes must now be provided with the Dictionary<string, string> data structure to allow the serializer to be as fast as possible.
• Removed dependancy on 3rd party JSON.NET library to reduce the size of the package. Backtrace-unity now provides it's own serializer for BacktraceReport usage.
• Further reduction in size of Backtrace.Unity assembly with BacktraceJObject.
• BacktraceDatabase won't try to deserialize BacktraceReport anymore - because of that, callback api won't return BacktraceReport object in BacktraceResult.
• BacktraceDatabase won't use anymore Add method with BacktraceReport parameter. Instead, BacktraceDaatabase will use Add method with BacktraceData parameter. Previous Add method is deprecated and will be removed in next major release.
• Support has been improved for parsing unhandled exception output from the Unity runtime and Unity executables.

NOTE: When migrating from previous releases, there is an API change that developers will want to uptake for attribute submission. Specifically, attribute definitions previously used a signature
attributes: new Dictionary<string, object>() { { "key", "value" } },
In this release, we made a change to require a string for the value instead of an object for faster performance.
attributes: new Dictionary<string, string>() { { "key", "value" } },

Bug Fixes

• Annotation name typo - updated children from childrens

Version 2.1.6

Version 2.1.6

• Handling special case for string reports fingerprint when stack trace is empty.

Version 2.1.5

Version 2.1.5

• Backtrace Unity plugin UI improvements - added tooltips, headers and collapsible menu for advanced options.
• Changed Client-side deduplication menu,
• BacktraceClient now allows you to choose what type of fingerprint Backtrace should generate for reports without stack trace. Use normalized exception message allows you to use a normalized exception message to generate fingerprint, instead of stack trace.
• Added exception source code information to exception and message type of reports.

3.0.0-alpha2

Version 3.0.0

New Features

• The backtrace-unity library now allows detection of ANR (Application not responding) events on Android devices.
• Unhandled exception output from the Unity runtime and executables is now prominently displayed in the Debugger.
• Backtrace library will try to guess unhandled exception classifier based on exception message/stack trace.

General Improvements

• BacktraceClient, BacktraceReport, BacktraceData, BacktraceData and BacktraceDatabase now allow users to pass attributes in dictionary form with string key and string values. Attributes must now be provided with the Dictionary<string, string> data structure to allow the serializer to be as fast as possible.
• Removed dependancy on 3rd party JSON.NET library to reduce the size of the package. Backtrace-unity now provides it's own serializer for BacktraceReport usage.
• Further reduction in size of Backtrace.Unity assembly with BacktraceJObject.
• BacktraceDatabase won't try to deserialize BacktraceReport anymore - because of that, callback api won't return BacktraceReport object in BacktraceResult.
• Support has been improved for parsing unhandled exception output from the Unity runtime and Unity executables,

NOTE: When migrating from previous releases, there is an API change that developers will want to uptake for attribute submission. Specifically, attribute definitions previously used a signature
attributes: new Dictionary<string, object>() { { "key", "value" } },
In this release, we made a change to require a string for the value instead of an object for faster performance.
attributes: new Dictionary<string, string>() { { "key", "value" } },

Bug Fixes

• Annotation name typo - updated children from childrens

Version 2.1.4

Version 2.1.4

• EnvironmentVariable class now will handle correctly nullable key/values,
• BacktraceAttributes handle correctly nullable values.

Version 2.1.3

Version 2.1.3

• BacktraceUnhandledException will generate environment stack trace if Unity stack trace is empty. BacktraceReport will still generate normalized fingerprint for unhandled exception without stack trace.
• BacktraceUnhandledException will provide information from Unity Error logger in source code property, which should improve error analysis in web debugger.
• BacktraceAttributes won't try to collect Annotations anymore.
• Annotations won't use ComplexAttributes property anymore.

Version 2.1.2

• BacktraceReport will generate report fingerprint for exceptions without stack trace.
• Changed game object depth default property value.
• Added Exception information to the Annotation object.

3.0.0-alpha1

Version 3.0.0

• Removed JSON.NET Dependency - now Backtrace library provide our own serializer just for BacktraceReport usage.
• BacktraceJObject allowed us to decrease size of Backtrace.Unity assembly.
• BacktraceClient and BacktraceReport allow our user to pass attributes in dictionary form with string key and string values. Because we want our serializer to be as fast as possible, we will require attributes in Dictionary<string, string> data structure.
• BacktraceDatabase won't try to deserialize BacktraceReport anymore - because of that, callback api won't return BacktraceReport object in BacktraceResult.

Version 3.0.0-alpha1 fixes:

• fixed invalid JSON properties that start ','.