Add API for deliberately crashing an app #1842
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a new public API,
SentrySdk.CauseCrash(CrashType), and several crash types - some of which are platform specific. This makes demonstrating how Sentry handles such crashes much easier.The main Sentry library for the
net6.0-androidtarget will now include some Java and C code that was previously used in the Android sample. The code and build scripts have been cleaned up a bit. We will still keep the binaries checked in so contributors don't necessarily need to re-build these dependencies. However we will rebuild them in CI to make sure the ones we are always clean and secure.For the
net6.0-iostarget, we already have code in the Sentry Cocoa SDK that will cause a native crash, so we just call that.