forked from flutter/flutter
-
Notifications
You must be signed in to change notification settings - Fork 1
Flutter CLI crash reporting
Ian Hickson edited this page Nov 1, 2018
·
7 revisions
(The flutter
tool points to this page in its introduction message.)
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 (master)
- Glossary
- Contributor Guide
- Chat on Discord
- Code of Conduct
- Issue triage reports
- Our Values
- Tree hygiene
- Issue hygiene and Triage
- Style guide for Flutter repo
- Project teams
- Contributor access
- What should I work on?
- Running and writing tests
- Release process
- Rolling Dart
- Manual Engine Roll with Breaking Commits
- Updating Material Design Fonts & Icons
- Postmortems
- Setting up the Framework development environment
- The Framework architecture
- The flutter tool
- 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
- 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
- Engine disk footprint
- Comparing AOT Snapshot Sizes
- Custom Flutter engine embedders
- Custom Flutter Engine Embedding in AOT Mode
- Flutter engine operation in AOT Mode
- Engine-specific Service Protocol extensions
- Crashes
- Supporting legacy platforms
- Metal on iOS FAQ
- Engine Clang Tidy Linter
- Why we have a separate engine repo
- Reduce Flutter engine size with MLGO
- Setting up the Plugins development environment
- Setting up the Packages development environment
- Plugins and Packages repository structure
- Plugin Tests
- Contributing to Plugins and Packages
- Releasing a Plugin or Package
- Unexpected Plugins and Packages failures