Flutter CLI crash reporting
Ian Hickson edited this page Aug 7, 2023
·
8 revisions
If you have not opted-out of Flutter's analytics and crash reporting, when a flutter
command crashes it attempts to send a crash report to Google in order to help Google contribute improvements to Flutter over time. A crash report may contain the following information:
- The name and version of your local operating system
- The version of Flutter
- The runtime type of the error, e.g.
StateError
orNoSuchMethodError
- The stack trace generated by the crash, which contains references to Flutter CLI's own code and contains no references to your application code
- A stable client ID - a constant and unique number generated for the computer where Flutter is installed. It helps us deduplicate multiple identical crash reports coming from the same computer. It also helps us verify if a fix works as indended after you upgrade to the next version of Flutter.
- Home of the Wiki
- Roadmap
- API Reference (stable)
- API Reference (main)
- Glossary
- Contributor Guide
- Chat on Discord
- Design documents
- Code of Conduct
- Issue triage reports (latest)
- Our Values
- Tree hygiene
- Issue hygiene and Triage
- Style guide for Flutter repo
- Project teams
- Contributor access
- What should I work on?
- Popular issues
- Running and writing tests
- Release process
- Flutter Framework Gardener Rotation
- Rolling Dart
- Manual Engine Roll with Breaking Commits
- Updating Material Design Fonts & Icons
- Postmortems and Retrospectives
- Hotfix Documentation Best Practices
- In case of emergency
- Landing Changes With Autosubmit
- Setting up the Framework development environment
- The Framework architecture
- API Docs code block generation
- Running examples
- Using the Dart analyzer
- The flutter run variants
- Test coverage for package:flutter
- Writing a golden-file test for package:flutter
- Managing template image assets
- Setting up the Engine development environment
- Compiling the engine
- Debugging the engine
- Using Sanitizers with the Flutter Engine
- Testing the engine
- The Engine architecture
- Flutter's modes
- Crashes
- more...
- Setting up the Packages development environment
- Plugins and Packages repository structure
- Contributing to Plugins and Packages
- Understanding Packages tests
- Plugin Tests
- Releasing a Plugin or Package
- more...