Improve crashing handling/reporting
Open
Nobody has claimed this yet.
Discussion
p3-medium
- Dominant language
- Kotlin
- Stars
- 4.2k
- Forks
- 3.1k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 7
Description
As suggested here https://github.com/owncloud/android/pull/2726, having a crash reporter to help detecting and fixing problems is a good idea.
Apart of the tools mentioned there, we can discuss about other options to handle, to finally get the most appropiated one for our targets.
Let's open the discussion...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the discussion in pull request #2726 and the crash-reporting tools mentioned there. Compare the available options against the app's targets, then document or implement the agreed approach once the discussion reaches a decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100