Skip to Content
Platform.Ontology

Why the process ended (exit reasons)

Apps can read why they were killed: Android ApplicationExitInfo, iOS MetricKit exit metrics.

Gets silentlyNotifications and backgroundPlatform quirksAndroid and iPhoneWhile you use itIn the background

In one line

Can learn why the system last ended the app, such as low memory

Apps can read why they were killed: Android ApplicationExitInfo, iOS MetricKit exit metrics.

Lets apps and SDKs learn whether the system, the user or a crash ended a session. Android 17 adds a memory limiter reason; it also exposes behavior to the person's device.

What it can and can't do

What the user does: Nothing. It happens the next time the app starts or a report arrives

It can

  • List recent reasons the app was ended on Android, such as low memory or you swiping it away
  • Get exit counts by reason on iPhone through MetricKit
  • Fix crashes and memory problems with the reports

It cannot

  • See why other apps ended
  • See your data or activity
  • Get iPhone reports faster than about once per 24 hours

How it differs between platforms: Android lists recent exits one by one. iPhone gives counts about once a day.

On Android and iPhone

AndroidiPhone
StatusSupportedSupported
First versionAndroid 11 (API 30)iOS 14.0
Permission or entitlementNot listedNot listed
Protection levelnonenone
How access is grantednonenone
What the user seesNoneNone
How long it lastsRecords kept for a short history (about the last 16 exits)Delivered in daily MetricKit payloads
How to take it backn/an/a
Store policyNone listedNone listed
APIActivityManager.getHistoricalProcessExitReasons()MXAppExitMetric (MetricKit)
NotesReasons: REASON_LOW_MEMORY, REASON_USER_REQUESTED, REASON_EXCESSIVE_RESOURCE_USAGE, REASON_OTHER ('MemoryLimiter:AnonSwap' on 17)Counts foreground and background exits by reason, delivered about once per 24 h

Data you get

What comes back: Exit records
Shape: list
How often: On demand

FieldTypeUnitRangePrecision
reasonenumNoneLOW_MEMORY, CRASH, USER_REQUESTED, OTHERNot listed
recordsintegercountabout 16approx

Technical limits

  • Android keeps a short history
  • iOS gives daily aggregates only

The story

What it is

An app can read why it was closed: by you, by a crash or by the system.

For you

You do not see it. When an app crashes or gets killed, it can learn why and later fix the bug. You may see fewer crashes over time.

For makers

Makers use it to find crashes, out of memory kills and battery problems. It also shows how you use the phone. Patterns of exits can serve as a quiet device profile.

Where you see it

TypeExampleApps
developerA developer sees that many users hit a memory kill on one phone model and fixes it.Firebase Crashlytics, Sentry
gamesA game studio finds that a level crashes older phones and lowers its graphics.None named
mediaA video app notes that the system closed it during long playback and reduces memory use.None named
fitnessA run tracker learns that the phone killed it mid run and starts a foreground service.Strava
analyticsAn analytics kit stores exit patterns to tell phones apart.None named
securityA security tool notices repeated kills that match a tampering attempt.None named

Risks

  • Fingerprinting by exit pattern
  • Shows how you use the phone

Android and iPhone in short

  • Android: Android 17 adds a memory limiter reason to ApplicationExitInfo.
  • iPhone: iPhone reports exit data in aggregate through MetricKit.

What the platform says

Good uses and abuse

Legitimate uses

  • Crash analytics

Known abuse

  • Fingerprinting by exit patterns

Scores

ScoreValueMeaning
Sensitivity1 of 5How revealing the data is
Utility3 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bitsNot ratedRough identifying entropy, when known

History

  • 2020-09, Android 11 (API 30): ApplicationExitInfo introduced
  • 2020-09, iPhone iOS 14: MXAppExitMetric added to MetricKit
  • 2026-06, Android 17 (API 37): App memory limits report REASON_OTHER with MemoryLimiter:AnonSwap

Same idea on the web

  • Idle Detection. Can tell when you step away or lock your screen, if you allow it

Sources

How well checked: Based on official documentation.

On this page