Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This PR adds support of reporting fatal ANRs (ANR which resulted in the
Application Not Responding
dialog where user decided to close the application).This functionality relies on the ApplicationExitInfo API (available since Android API 30), which can be read on the next application run. So in that sense it is similar to the approach we have to report NDK crashes: on the next application run we need to run this information and match it with the last RUM view event we know.
Since we cannot mark a particular
ApplicationExitInfo
as read in the system, we have to store the timestamp of the lastApplicationExitInfo
we processed to avoid the possible delivery on the next application run.When processing
ApplicationExitInfo
, we will read trace information attached to it and try to parse it (it is non-structured log).This PR doesn't add the possibility to disable reporting of non-fatal (or unknown) ANRs, and it doesn't add
error.category
info, this will be done in next PRs.Review checklist (to be filled by reviewers)