v5.24.0

Enhancements

• Complex metadata (nested structures such as maps & lists) added in Java/Kotlin is now fully preserved in NDK errors
  #1715
• Configuration.discardClasses now applies to NDK errors
  #1710

v5.23.1

Bug fixes

• Report the correct filename for native-libs that are loaded from within apk files
  #1705

v5.23.0

Enhancements

• Added configuration option to control whether internal errors are sent to Bugsnag
  #1701

Bug fixes

• Fixed Bugsnag interactions with the Google ANR handler on newer versions of Android
  #1699
• Overwriting & clearing event metadata in the NDK plugin will no longer leave phantom values
  #1700

v5.22.4

Bug fixes

• Reverted #1680 to avoid deadlocks during startup
  #1696
• Improved app.inForeground reporting for NDK errors
  #1690

v5.22.3

Bug fixes

• Fixed concurrency bug that could be triggered via the React Native plugin
  #1679
• Correctly report device.locationStatus on Android 12 onwards using LocationManager.isLocationEnabled
  1683
• Small performance improvements to Bugnag.start
  #1680

v5.22.2

Bug fixes

• Fixed NDK stack-traces for libraries linked after Bugsnag.start was called
  #1671

v5.22.1

Enhancements

• Max reported threads can now be configured using manifest meta-data "com.bugsnag.android. MAX_REPORTED_THREADS"
  #1655
• Small improvement to startup performance (Bugsnag.start)
  #1648

v5.22.0

Enhancements

• Added Bugsnag.isStarted() to test whether the Bugsnag client is in the middle of initializing. This can be used to guard uses of the Bugsnag API that are either on separate threads early in the app's start-up and so not guaranteed to be executed after Bugsnag.start has completed, or where Bugsnag may not have been started at all due to some internal app logic.
  slack-jallen:#1621
  #1640

• Events and Sessions will be discarded if they cannot be uploaded and are older than 60 days or larger than 1MB
  #1633

Bug fixes

• Fixed potentially thread-unsafe access when invoking Bugsnag static methods across different threads whilst Bugsnag.start is still in-flight. It is now safe to call any Bugsnag static method once Bugsnag.start has begun executing, as access to the client singleton is controlled by a lock, so the new isStarted method (see above) should only be required where it cannot be determined whether the call to Bugsnag.start has begun or you do not want to wait. #1638
• Calling bugsnag_event_set_context with NULL context correctly clears the event context again
  #1637

v5.21.0

Enhancements

• Fix inconsistencies in stack trace quality for C/C++ events. Resolves a few
  cases where file and line number information was not resolving to the correct
  locations. This change may result in grouping changes to more correctly
  highlight the root cause of an event.
  #1605
  #1606

Bug fixes

• Fixed an issue where an uncaught exception on the main thread could in rare cases trigger an ANR.
  #1624

v5.20.0

Enhancements

• The number of threads reported can now be limited using Configuration.setMaxReportedThreads (defaulting to 200)
  #1607

• Improved the performance and stability of the NDK and ANR plugins by caching JNI references on start
  #1596
  #1601