[Android] Remove experimental enableNativeCrashReporting flag #769
Conversation
This file contains hidden or 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
Size Comparison Report (x86_64)
|
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.
What
enableNativeCrashReportingis been an experimental flag that allowed customers to opt in for getting native crash reports. This has been tested on the field and looks like we don't have any client issue that requires keeping this flag optional anymore, so removing this as part of the config and make it the default as part of the mainenableFatalIssueReportingflag.Verification
From the
gradle-test-app, trigger a fatal native crash. See report hereFollow-ups
Update public docs