-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Add instructions for writing useful bug reports #172
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,32 @@ | ||
| --- | ||
| layout: page | ||
| title: Creating Useful Bug Reports | ||
| permalink: /bug_reports/ | ||
| --- | ||
|
|
||
| The instructions in this document detail the current steps required to provide the most actionable bug reports for crashes and other bad behavior. Each step is optional but will greatly improve how quickly issues are diagnosed and addressed. We appreciate your effort in sending us as much feedback as possible. | ||
|
|
||
| ## Create an Issue on Github | ||
| * A new Github issue may be created at https://github.com/flutter/flutter/issues/new | ||
|
|
||
| ## Provide the Flutter Version | ||
| * Run `flutter --version` in your project and paste the results into the Github Issue | ||
|  | ||
|
|
||
| ## Run the Command in Verbose Mode | ||
| Follow these steps only if your issue is related to the `flutter` tool. | ||
| * All Flutter commands accept the `--verbose` flag. If attached to the issue, the output from this command may aid in diagnosing the issue. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Add "If your problem is with the 'flutter' tool, then:" or some such (since people attaching verbose "flutter run" output to every framework bug is going to get old fast) |
||
| * Attach the results of the command to the Github issue. | ||
|  | ||
|
|
||
| ## Provide the Most Recent Logs | ||
| * Logs for the currently connected device may be accessed via `flutter logs` | ||
| * If the crash is reproducible, clear the logs (⌘ + k on Mac), reproduce the crash and copy the newly generated logs into a file attached to the bug report. | ||
| * If you are getting exceptions thrown by the framework, include all the output between and including the dashed lines of the first such exception. | ||
|  | ||
|
|
||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Add:
|
||
| ## Provide the Crash Report | ||
| * In case the iOS simulator crashes, a crash report is generated in `~/Library/Logs/DiagnosticReports/`. | ||
| * In case the iOS device crashes, a crash report is generated in `~/Library/Logs/CrashReporter/MobileDevice`. | ||
| * Find the report corresponding to the crash (usually the latest) and attach it to the Github issue. | ||
|  | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add a second paragraph here praising anyone who's willing to send us feedback.