Releases: backtrace-labs/backtrace-unity
Releases · backtrace-labs/backtrace-unity
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_
Version 3.4.0-rc2
Version 3.4.0-rc2
- 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.
Version 3.4.0-rc1
Version 3.4.0-rc1
- native/managed attachment support - user can add path to attachments via BacktraceClient Initialize method or via Unity Editor Backtrace Window. 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.
Version 3.3.3
Version 3.3.3
- Fixed iOS compilation issue with Backtrace namespace.
- Prevent displaying Backtrace configuration when Application.isPlaying is true.
Version 3.3.2
Version 3.3.2
- ANR detection algorithm now uses
Time.unscaledTime
instead ofTime.time
to prevent ANR detection when game is paused. Pull request: #60
Version 3.3.1
Version 3.3.1
- Improved Out-of-memory detection on iOS - Backtrace will report Out-of-memory exceptions when a memory warning occured and the application unexpectly closed. The Out-of-memory watcher will analyse game version, system version, debugger information and even more to determine if application closed by Out-of-memory exception or not.
- Backtrace will no longer send low memory warnings reports from Android or iOS. Instead, Backtrace will utilize iOS OOM detection and extend the embedded native report attributes on Android.
- Users can now enable or disable out-of-memory detection any time via UI/Backtrace API.
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 ofLow 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 ofHang
.
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 toerror
. - Fixed nullable environment annotation value.