Add additional app launch scenarios for OOM tracking #3
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.
Summary:
OOM tracking is based off of the blog post from Facebook https://code.fb.com/ios/reducing-fooms-in-the-facebook-ios-app/
This requires a process-of-elimination to determine if a launch is due to an OOM crash by marking every legitimate reason that an application could start. The article did not cover ways that the app may be launched from the OS which are background fetches and silent push notifications currently.
New additions in this PR