Releases: backtrace-labs/backtrace-unity
Releases · backtrace-labs/backtrace-unity
Version 3.6.2
Version 3.6.2
Bugfixes
- Fixed invalid behavior of multi select dropdown in Unity 2017/2018. Now users can select multiple values (instead of one) on multi select dropdowns.
- Fixed invalid escaping of control characters, affecting reports in Chinese to be rendered incorrectly in the Backtrace UI.
- Fixed a bug caused by the Unity API when Backtrace tries to parse Unity message from a background thread.
- General API improvements.
Version 3.6.1
Version 3.6.1
Bugfixes
- Fixed unhandled exception caused by truncated stack trace
Improvements
- improved client side unwinding support on Android
Version 3.6.0
Version 3.6.0
New functionality
- Added option for client side unwinding of native crashes on Android for NDK 19+ (Unity 2019+)
- Added support for passing all attributes defined in the managed c# layer to Windows native crashes
- Added Unity engine log buffer to reports objects and updated Debugger view to display the last Log lines again.
- Improved OOM support - memory warnings won't generate and store crash reports.
Bugfixes
- Backward compatibility support for .NET 3.5
Version 3.6.0-preview.3
Version 3.6.0-Preview
New functionality
- Added support for client side unwinding of native crashes on Android
- Added support for windows native crashes
Bugfixes
- Backward compatibility support for .NET 3.5
This preview release also fixes compilation issues on platforms without native client class implementation.
Version 3.6.0-preview.2
Version 3.6.0-Preview
New functionality
- Added support for client side unwinding of native crashes on Android
- Added support for windows native crashes (including attributes, attachments, ANRs),
- Unity engine logs are now available once again in the Backtrace web debugger.
Bugfixes
- Backward compatibility support for .NET 3.5
Version 3.6.0-preview
Version 3.6.0-Preview
New functionality
- Added support for client side unwinding of native crashes on Android
Bugfixes
- Fixed error in .NET 3.5 support
Adjustments
- The library now ignores ANR reports generated in the debug mode,
- The library will omit report generation when OOM occured.
Version 3.5.0
New functionality
- Support for capturing metrics to determine crash free users and sessions for your game. Once enabled, unique application launches and unique player identifiers (default:
guid
) will be submitted to Backtrace so you will be able to get an overview in our web console of how many errors, hangs, crashes and memory problems occur compared to all active users for a given platform, version, etcetera. See the README for more info on functionality and configuration options. This functionality is supported on all Unity supported platforms except WebGL. - Support for breadcrumbs. Once enabled, various "breadcrumb" events (such as application going to background, log message, network connectivity lost and many more) will be submitted with all types of Backtrace reports and viewable in the web console. It is possible to configure client-side which events to include and from which log level severity. It is also possible to add custom events, like "player completed a level", via the API. By default the breadcrumbs are limited to 64kB, and when the limit is reached, the oldest events will automatically be removed to make space for newer breadcrumbs. See the README for more information on functionality and configuration options. This functionality is supported on all Unity supported platforms.
- Support for controlling the size and quality of the JPEG screenshots captured, to reduce bandwith and storage.
- Support for filtering out DebugLog error messages.
Removed
- Support for .NET 2.0 was removed. .NET 2.0 has been end of life for some time. If support is required for .NET 2.0, please use backtrace-unity 3.4.x
Bugfixes
- Fixed Unity 2020 & 2021 warnings
- Adjusted structure size on the iOS build
- Guess backtrace-android native crash reporter path if appcontext is not available
Version 3.5.0-preview
Version 3.5.0-preview.1
New functionality
- Support for capturing metrics to determine crash free users and sessions for your game. Once enabled, unique application launches and unique player identifiers (default:
guid
) will be submitted to Backtrace so you will be able to get an overview in our web console of how many errors, hangs, crashes and memory problems occur compared to all active users for a given platform, version, etcetera. See the README for more info on functionality and configuration options. This functionality is supported on all Unity supported platforms except WebGL. - Support for breadcrumbs. Once enabled, various "breadcrumb" events (such as application going to background, log message, network connectivity lost and many more) will be submitted with all types of Backtrace reports and viewable in the web console. It is possible to configure client-side which events to include and from which log level severity. It is also possible to add custom events, like "player completed a level", via the API. By default the breadcrumbs are limited to 64kB, and when the limit is reached, the oldest events will automatically be removed to make space for newer breadcrumbs. See the README for more information on functionality and configuration options. This functionality is supported on all Unity supported platforms.
Removed
- Support for .NET 2.0 was removed. .NET 2.0 has been end of life for some time. If support is required for .NET 2.0, please use backtrace-unity 3.4.x
Bugfixes
- Fixed Unity 2020 & 2021 warnings
- Adjusted structure size on the iOS build
- Guess backtrace-android native crash reporter path if appcontext is not available
Version 3.4.0
Version 3.4.0
- native/managed attachment support - user can add path to attachments via BacktraceClient Initialize method or via Unity Editor in the BacktraceClient's inspector. Once user add them on the initialization method/game object - it will be available in every report that BacktraceClient will send to Backtrace.
- background thread support - now BacktraceClient will report exceptions/unhandled exceptions generated by any background thread.
- ANR detection improvements - BacktraceClient won't report anymore ANRs detected when the application goes to the background.
thread.main
attribute support - attribute stores an identifier of a main thread. In this situation user can use value available in this attribute to detect main thread.- Backtrace native integration will set
_mod_faulting_tid
attribute for ANR reports to set default faulting thread. - Fixed arabic language bug, that generated an unhandled exception on new Unity message.
- Fixed attachment prefix
attachment__
->attachment_
Version 3.4.0-rc3
Version 3.4.0-rc3
- native/managed attachment support - user can add path to attachments via BacktraceClient Initialize method or via Unity Editor in the BacktraceClient's inspector. Once user add them on the initialization method/game object - it will be available in every report that BacktraceClient will send to Backtrace.
- background thread support - now BacktraceClient will report exceptions/unhandled exceptions generated by any background thread.
- ANR detection improvements - BacktraceClient won't report anymore ANRs detected when the application goes to the background.
thread.main
attribute support - attribute stores an identifier of a main thread. In this situation user can use value available in this attribute to detect main thread.- Backtrace native integration will set
_mod_faulting_tid
attribute for ANR reports to set default faulting thread. - Fixed arabic language bug, that generated an unhandled exception on new Unity message.
- Fixed attachment prefix
attachment__
->attachment_