fix: Android - make sure logcat.log is attached to unhandled event (SIGSEGV Segfault)#3694
fix: Android - make sure logcat.log is attached to unhandled event (SIGSEGV Segfault)#3694jamescrosswell merged 46 commits intomainfrom
Conversation
Co-authored-by: Bruno Garcia <bruno@brunogarcia.com>
Co-authored-by: Bruno Garcia <bruno@brunogarcia.com>
Co-authored-by: Bruno Garcia <bruno@brunogarcia.com>
…oid.Init(AppContext, configuration);`
…coped namespace declaration
The release is out now! We just need an update from |
@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. |
|
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! |
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: