Releases: bugsnag/bugsnag-unity
v4.8.5-alpha03
Adds additional JNI error handling and pushing of local frames to prevent rare crashes.
v4.8.5-alpha02
dep: update Android dependency to include JNI fixes
v4.8.4
Enhancements
-
Add device id to error reports on Cocoa platforms
#203 -
Update bugsnag-cocoa to v5.23.5:
-
Fix JSON serialisation of strings with control characters
#739 -
Removed non-thread safe date formatter
#758 -
Avoid dereference null pointer in JSON serialisation
#637
Naugladur -
Fixed an issue where an app could deadlock during a crash if unfavourable
timing caused DYLD lock contention.
#580
#675
#725
#721 -
Fix possible report corruption when using
notify()
from multiple threads
when configured to skip capturing/reporting background thread contents
(generally only Unity games).
#442 -
Added several additional event fields (
codeBundleId
,osName
,
modelNumber
,locale
) that were missing from the OOM reports.
#444 -
Bugsnag now correctly records a new session if it is returning to
the foreground after more than 60 seconds in the background.
#529
-
v4.8.3
v4.8.2
v4.8.1
v4.8.0
Enhancements
This release adds ANR detection for Unity apps running in Android. To enable this option you should
set Bugsnag.Configuration.AutoDetectAnrs
to true
after initialising bugsnag in the normal way.
- Detect ANRs on Android and provide configuration option to enable detection
#184
Bug fixes
- (Android) Prevent SIGABRT when altering Configuration on background thread
#187
v4.7.0
-
Update bugsnag-android to v4.22.2:
-
This release adds a compile-time dependency on the Kotlin standard library. This should not affect
the use of any API supplied by bugsnag-unity. -
Modularise bugsnag-android into Core, NDK, and ANR artifacts
#522 -
Migrate dependencies to androidx
#554 -
Report internal SDK errors to bugsnag
#570
#581
#594
#605
#588
#612 -
Add
detectNdkCrashes
configuration option to bugsnag-android to toggle whether C/C++ crashes
are detected
#491 -
Use NetworkCallback to monitor connectivity changes on newer API levels
#501 -
Fix deserialization of custom stackframe fields in cached error reports
#576 -
Buffer IO when reading from cached error files, improving SDK performance
#573 -
flushOnLaunch() does not cancel previous requests if they timeout, leading to potential duplicate reports
#593 -
Report correct value for free disk space
#589 -
Allow overriding the versionCode via Configuration
#610 -
Catch throwables when invoking methods on system services
#623
-
-
Update bugsnag-cocoa to v5.23.0:
-
Fix unrecognized selector crash when adding metadata
#430 -
This release removes support for reporting 'partial' or 'minimal' crash reports
where the crash report could not be entirely written (due to disk space or other
issues like the device battery dying). While sometimes the reports could point
in the right direction for debugging, they could also be confusing or not enough
information to pursue and close the issue successfully.This release also renames a few configuration properties to align better with the
intended use and other Bugsnag libraries, so people who use more than one
platform can easily find related functionality in a different library. The old
names are deprecated but still supported until the next major release.
#435Bugsnag.setBreadcrumbCapacity()
is nowsetMaxBreadcrumbs()
on the
BugsnagConfiguration
class. In addition, the default number of breadcrumbs
saved has been raised to 25 and limited to no more than 100.BugsnagConfiguration.autoNotify
is now named
BugsnagConfiguration.autoDetectErrors
BugsnagConfiguration.autoCaptureSessions
is now named
BugsnagConfiguration.autoDetectSessions
-
v4.6.7
v4.6.6
Bug fixes
- Fixed the naming and description of the GUI property "Unique logs per second"
to be "Unique seconds per log" to reflect the actual behavior, which is the
number of seconds required between unique Unity log messages which
bugsnag-unity will convert into breadcrumbs or reports. Increase the value to
reduce the number of logs or reports generated from frequent error messages. - Update bugsnag-cocoa to v5.22.9:
- Deprecate
config.reportBackgroundOOMs
property - designating any app
termination as a possible error condition can cause a lot of false positives,
especially since the app can die for many genuine reasons, especially when
running only in the background.
bugsnag-cocoa#425 - Fix use-after-free in
notify()
logic which could lead to a deadlock
bugsnag-cocoa#420 - Reduce severity of log message about thread status from 'error' to 'debug' as
it does not necessarily indicate a problem and is only used for debugging.
bugsnag-cocoa#421 - Show correct value for
app.inForeground
when an app launches and crashes in
the background without ever coming to the foreground.
bugsnag-cocoa#415 - Fix improperly retained properties which could result in a crash due to
premature deallocation
bugsnag-cocoa#416
- Deprecate