flutter / flutter/flutter-intellij
improve crash reporting
- Dominant language
- Java
- Stars
- 2k
- Forks
- 356
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 27
Description
We should look at upgrading the crash reporting we're doing from this plugin. Currently we can only get the first 500 chars of a stack trace, and can't get the exception text.
Android Studio uses this code to do crash reporting:
- android/src/com/android/tools/idea/diagnostics/crash/StudioCrashReporter.java
- android/src/com/android/tools/idea/diagnostics/error/ErrorReporter.java
Contributor guide
Research direction
Locate the plugin's current crash-reporting implementation, then compare its behavior with android/src/com/android/tools/idea/diagnostics/crash/StudioCrashReporter.java and android/src/com/android/tools/idea/diagnostics/error/ErrorReporter.java. Done means crash reports include the complete stack trace rather than only 500 characters and include the exception text.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- devtools, observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100