Bump bugsnag-android-ndk from 4.9.1 to 5.22.3

[dependabot]

Bumps bugsnag-android-ndk from 4.9.1 to 5.22.3.

Release notes

Sourced from bugsnag-android-ndk's releases.

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

... (truncated)

Changelog

Sourced from bugsnag-android-ndk's changelog.

5.22.3 (2022-05-12)

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

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

... (truncated)

Commits

• 55c2fe1 Merge pull request #1685 from bugsnag/releases/v5.22.3
• c2bb12b v5.22.3
• 650579e Merge pull request #1684 from bugsnag/tms/fixture-logging
• dc7af52 Improve test fixture logging
• 9e1da59 Merge pull request #1679 from bugsnag/PLAT-8390-concurrency
• a29c9d4 Merge branch 'next' into PLAT-8390-concurrency
• 28359da Merge pull request #1683 from bugsnag/PLAT-8430/fix-location-status
• 04eb1fc fix(locationStatus): use LocationManager.isLocationEnabled on Android 12 on...
• 59edeb5 Fixed concurrency bug that could be triggered via the React Native plugin
• 93a224b Merge pull request #1680 from bugsnag/PLAT-8334/optimise-resolve-dependencies
• Additional commits viewable in compare view

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)

[dependabot]

Superseded by #138.