docs(crashlytics): illustrate different methods for recording crashes #11275
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
russellwheatley
changed the title
Closed
10 tasks
Lyokone
approved these changes
Jul 13, 2023
pr-Mais
approved these changes
Jul 13, 2023
lesnitsky
approved these changes
Jul 13, 2023
|
Hi @kevinthecheung - would be nice to have a new deployment of Firebase docs site so this is refreshed. Thanks. |
swav-labrys
reviewed
Aug 8, 2023
| } | ||
| // If you want to record a "non-fatal" exception, use `FirebaseCrashlytics.instance.recordFlutterError` instead | ||
| const fatalError = true; | ||
| FlutterError.onError = (errorDetails) { |
There was a problem hiding this comment.
does this condition have any sense since it is const value?
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
see title.
Related Issues
Replaces this PR: #10772
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]).This will ensure a smooth and quick review process. Updating the
pubspec.yamland changelogs is not required.///).melos run analyze) does not report any problems on my PR.Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?