fix: Android - make sure logcat.log is attached to unhandled event (SIGSEGV Segfault)

[bricefriha]

From sentry-native#1027, we had to add the handler strategy to the .NET SDK, from the sentry-java (7.15.0-alpha1).

This is also meant to fix #3461. I tested this, and it seems to be fixed now.

More context at:

• SIGSEGV reported by Sentry when a NullReferenceException is thrown in Release mode dotnet/android#9055 (comment)

[bricefriha]

What's the next steps for this?

I let the Java team know that we are ready to merge so they are working on merging their PRs as well

once they have the update on the main release, we can merge

[bruno-garcia]

merged! getsentry/sentry-native#1027 (comment)

We'd like to wait for their release though, so we can checkout the release tag instead of a random commit sha

[bricefriha]

We'd like to wait for their release though

The release is out now!
https://github.com/getsentry/sentry-native/releases/tag/0.7.13

We just need an update from sentry-java

[jamescrosswell]

The release is out now! https://github.com/getsentry/sentry-native/releases/tag/0.7.13

We just need an update from sentry-java

@markushi any timeframe on getting the fix we tested in 7.15.0-alpha.1 into an official release? I'd love to roll this out in the .NET SDK but we've got a bit of a dependency chain.

Looks like we'll have to do something similar for iOS as well, and it would be nice to reference this solution when discussing with the cocoa team.

[markushi]

The release is out now! getsentry/sentry-native@0.7.13 (release)
We just need an update from sentry-java

@markushi any timeframe on getting the fix we tested in 7.15.0-alpha.1 into an official release? I'd love to roll this out in the .NET SDK but we've got a bit of a dependency chain.

Looks like we'll have to do something similar for iOS as well, and it would be nice to reference this solution when discussing with the cocoa team.

If it's tested and we know the change works, we can merge and get this released at any time. Let me get the PR up-to-date first.

[jamescrosswell]

Looks like the fix was included with the 7.19.0 release of the Java SDK. We just need to bump the version in this PR and we should be good to go!