getsentry / getsentry/sentry-java
Report app exit reasons
- Linguagem predominante
- Kotlin
- Estrelas
- 1.4k
- Forks
- 478
- Merge médio
- 2d 22h
- PRs com merge (30d)
- 69
Descrição
### Problem Statement
`ApplicationExitInfo.getReasion()` provides a detailed breakdown why an app shut down. We should collect this information and report it:
* [`REASON_UNKNOWN`]()
* [`REASON_EXIT_SELF`]()
* [`REASON_SIGNALED`]()
* [`REASON_LOW_MEMORY`]()
* [`REASON_CRASH`]()
* [`REASON_CRASH_NATIVE`]()
* [`REASON_ANR`]()
* [`REASON_INITIALIZATION_FAILURE`]()
* [`REASON_PERMISSION_CHANGE`]()
* [`REASON_EXCESSIVE_RESOURCE_USAGE`]()
* [`REASON_USER_REQUESTED`]()
* [`REASON_USER_STOPPED`]()
* [`REASON_DEPENDENCY_DIED`]()
* [`REASON_OTHER`]()
* [`REASON_FREEZER`]()
* [`REASON_PACKAGE_STATE_CHANGE`]()
* [`REASON_PACKAGE_UPDATED`]()
* [`REASON_MEMORY_LIMITER`]()
### Solution Brainstorm
* Report as Metrics
* Report as Logs
* Enrich matching events (ANR events contain `REASON_ANR`)
┆Issue is synchronized with this [Jira Improvement]() by [Unito]()
Guia de contribuição
Avaliação
Esta issue ainda não foi avaliada.