Better crash tracking

[jesmrec]

When a crash related to the system happens, app stops logging and no trace about the crash appears in logcat or log files after reopening the app. For that reason, we should look for a solution that help us to get information about the crash to fix it.

Posibilities:

• Check if there is any internal way to do it (new library, new API interaction that allows to get that info)
• Use an external dependency to fetch the info. Google Play Console helps, but this is statistic-oriented, and specific cases are not taken in account. Something like Crashlitycs comes to my mind (free and non-free tiers).

In this issue, we should explore options and determine if some of then fits better our case and helps to improve the crash tracking tasks.

TASKS

• [ ] Research (if needed)
• [ ] Create branch feature/feature_name
• [ ] Development tasks
  • [ ] Implement whatever
  • [ ] ...
• [ ] Code review and apply changes requested
• [ ] Design test plan
• [ ] QA
• [ ] Merge branch feature/feature_name into master

[michaelstingl]

I remember NewPipe has some magic crash handling. Anything we could learn?

• https://github.com/TeamNewPipe/NewPipe/blob/dev/.github/CONTRIBUTING.md

[jesmrec]

Report crashes through the automated crash report system of NewPipe

@theScrabi any hint about this? something that could help us?