Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(crashlytics): Use PlatformDispatcher.instance.onError for async errors. Update Crashlytics example app to use "flutterfire-e2e-tests" project. #9669

Merged
merged 8 commits into from Oct 26, 2022

Conversation

russellwheatley
Copy link
Member

@russellwheatley russellwheatley commented Oct 4, 2022

Description

Flutter has changed the way it handles errors as of Flutter 3.3 (See this commit).

Updated example app and documentation using latest implementation to catch uncaught async errors: PlatformDispatcher.instance.onError.

I've also updated the docs to be more explicit about what choice of error report is sent to Crashlytics. See: #8815

Also updated the example app to use "flutterfire-e2e-tests" Firebase project. Updated this issue: #9643

Related Issues

Closes #8815

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.yaml and changelogs is not required.

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
  • All existing and new tests are passing.
  • I updated/added relevant documentation (doc comments with ///).
  • The analyzer (melos run analyze) does not report any problems on my PR.
  • I read and followed the Flutter Style Guide.
  • I signed the CLA.
  • I am willing to follow-up on review comments in a timely manner.

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

  • Yes, this is a breaking change.
  • No, this is not a breaking change.

@russellwheatley
Copy link
Member Author

Hey @kevinthecheung, I've updated the documentation to show users how to record "fatal" & "non-fatal" errors. Could you have a look at the changes and see what you think, please?

@russellwheatley russellwheatley changed the title docs(crashlytics): Use PlatformDispatcher.instance.onError for async errors. Update example apps. docs(crashlytics): Use PlatformDispatcher.instance.onError for async errors. Update Crashlytics example app to use "flutterfire-e2e-tests". Oct 6, 2022
@russellwheatley russellwheatley changed the title docs(crashlytics): Use PlatformDispatcher.instance.onError for async errors. Update Crashlytics example app to use "flutterfire-e2e-tests". docs(crashlytics): Use PlatformDispatcher.instance.onError for async errors. Update Crashlytics example app to use "flutterfire-e2e-tests" project. Oct 6, 2022
@russellwheatley
Copy link
Member Author

Hey @kevinthecheung - could you let me know if the doc changes are acceptable, please?

russellwheatley and others added 2 commits October 26, 2022 11:36
Co-authored-by: Kevin Cheung <kevinthecheung@users.noreply.github.com>
@russellwheatley russellwheatley merged commit 8a0caa0 into master Oct 26, 2022
@russellwheatley russellwheatley deleted the @russell/crash-9026 branch October 26, 2022 11:42
@firebase firebase locked and limited conversation to collaborators Nov 26, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[📚] Crashlytics recordFlutterFatalError
4 participants