- 10 Dec, 2018 1 commit
-
-
Todd Volkert authored
This modifies our flutter_tools crash reports to include the error message. This error message may contain personally identifying information (PII), such as a file system path on the developer's local machine that may contain user names, project code names, etc. To disable crash reporting, the developer can run the following command: flutter config --no-analytics For more information on what gets reported during crashes of the flutter tool, see: https://github.com/flutter/flutter/wiki/Flutter-CLI-crash-reporting
-
- 17 Oct, 2018 1 commit
-
-
Alexandre Ardhuin authored
-
- 05 Oct, 2018 1 commit
-
-
Alexandre Ardhuin authored
-
- 04 Oct, 2018 1 commit
-
-
Alexandre Ardhuin authored
-
- 12 Sep, 2018 1 commit
-
-
Alexandre Ardhuin authored
* enable lint unnecessary_new * fix tests * fix tests * fix tests
-
- 20 Jul, 2018 1 commit
-
-
Greg Spencer authored
-
- 20 Jun, 2018 1 commit
-
-
Yegor authored
-
- 02 Feb, 2018 1 commit
-
-
Alexandre Ardhuin authored
-
- 28 Mar, 2017 1 commit
-
-
Yegor authored
* enable crash reporting in flutter_tools * fix analytics text; use relative paths * fix test
-
- 21 Mar, 2017 1 commit
-
-
Alexandre Ardhuin authored
-
- 15 Mar, 2017 1 commit
-
-
John McCutchan authored
- [x] Don't use package:stack_trace. - [x] Don't use Chain.capture. - [x] Fix an instance of aggressive catching of exceptions Related #8742
-
- 10 Mar, 2017 1 commit
-
-
Yegor authored
-
- 09 Mar, 2017 1 commit
-
-
Todd Volkert authored
-
- 07 Mar, 2017 1 commit
-
-
Yegor authored
-
- 04 Mar, 2017 2 commits
-
-
Chris Bracken authored
-
Yegor authored
* add crash reporting without enabling it * do not drop futures on the floor * return exitCode from executable run * debug travis * remove unnecessary todo * rename local fs getter
-