Skip to content

Bump bugsnag-android-ndk from 4.9.1 to 5.22.2#130

Closed
dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot/gradle/com.bugsnag-bugsnag-android-ndk-5.22.2
Closed

Bump bugsnag-android-ndk from 4.9.1 to 5.22.2#130
dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot/gradle/com.bugsnag-bugsnag-android-ndk-5.22.2

Conversation

@dependabot
Copy link

@dependabot dependabot bot commented on behalf of github May 9, 2022

Bumps bugsnag-android-ndk from 4.9.1 to 5.22.2.

Release notes

Sourced from bugsnag-android-ndk's releases.

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

... (truncated)

Changelog

Sourced from bugsnag-android-ndk's changelog.

5.22.2 (2022-05-04)

Bug fixes

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

5.22.1 (2022-04-28)

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

5.22.0 (2022-03-31)

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

5.21.0 (2022-03-17)

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

5.20.0 (2022-03-10)

... (truncated)

Commits
  • 1c98bea Merge pull request #1673 from bugsnag/releases/v5.22.2
  • a3bb9a6 v5.22.2
  • b2df0ac Merge pull request #1671 from bugsnag/PLAT-8392/dlopen-breaks-symbolication
  • 9158d1d Merge branch 'next' into PLAT-8392/dlopen-breaks-symbolication
  • 1b20817 Merge pull request #1669 from bugsnag/tms/log-discard-old
  • 33374e2 Merge branch 'next' into tms/log-discard-old
  • ba82575 fix(unwind): fallback to dladdr in the crash unwinder when a stack frames `...
  • 1f14725 Merge pull request #1670 from bugsnag/karl-fix-build
  • 23697ae Fix build issues with 32-bit
  • 882cce9 Merge pull request #1668 from bugsnag/master
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [bugsnag-android-ndk](https://github.com/bugsnag/bugsnag-android) from 4.9.1 to 5.22.2.
- [Release notes](https://github.com/bugsnag/bugsnag-android/releases)
- [Changelog](https://github.com/bugsnag/bugsnag-android/blob/next/CHANGELOG.md)
- [Commits](bugsnag/bugsnag-android@v4.9.1...v5.22.2)

---
updated-dependencies:
- dependency-name: com.bugsnag:bugsnag-android-ndk
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label May 9, 2022
@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github May 23, 2022

Superseded by #133.

@dependabot dependabot bot closed this May 23, 2022
@dependabot dependabot bot deleted the dependabot/gradle/com.bugsnag-bugsnag-android-ndk-5.22.2 branch May 23, 2022 04:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants