Skip to Content
Platform.Ontology

Force stop and force quit

A person can kill an app: Android force stop cancels alarms; iOS force quit stops background fetch and silent push.

Gets silentlyNotifications and backgroundPlatform quirksAndroid and iPhoneIn the background

In one line

Can't keep running or wake itself after you force stop (Android) or swipe it away (iPhone)

A person can kill an app: Android force stop cancels alarms; iOS force quit stops background fetch and silent push.

Marks the clearest signal that someone does not want an app active. Both systems then block background starts until the person opens the app again.

What it can and can't do

What the user does: You tap Force stop in Android Settings, or swipe the app up in the iPhone app switcher

It can

  • Start working again as soon as you open the app yourself
  • Wake up for VoIP calls, location events or Bluetooth on iPhone, for some modes only
  • Keep its saved data, since force stopping does not erase anything

It cannot

  • Receive push messages on Android until you open the app again
  • Fire alarms or scheduled jobs on Android after a force stop; they are cancelled
  • Get silent background pushes on iPhone after a force quit; Apple discards them
  • Run background refresh on iPhone until you open the app once more

How it differs between platforms: Android force stop blocks pushes and cancels alarms. iPhone force quit blocks silent pushes and refresh, but some call, location and Bluetooth wakes still work.

On Android and iPhone

AndroidiPhone
StatusSupportedSupported
First versionAndroid 3.1 (API 12)iOS 7.0
Permission or entitlementNot listedNot listed
Protection levelnonenone
How access is grantedsettingsnone
What the user seesSettings > Apps > Force stopSwipe up in app switcher
How long it lastsApp stays in the stopped state until the user launches it; alarms, jobs and broadcasts cancelled; FCM not deliveredBackground fetch, BG tasks and silent push stop until the user relaunches; location region events still relaunch
How to take it backOpen the app againOpen the app again
Store policyNone listedNone listed
APIApplicationInfo.FLAG_STOPPED, FirebaseMessaging not deliveredUIApplication state; no API to detect
NotesStopped state blocks FCM broadcasts and cancels alarms and jobs; Android 15 can also cancel on swipe for some devicesApple: force quit means silent push is discarded; VoIP, location and BLE wakes continue for some modes

Data you get

What comes back: Stopped
Shape: boolean
How often: On user action

FieldTypeUnitRangePrecision
stoppedbooleanNonetrue or falseNot listed

Technical limits

  • Cannot be detected directly
  • Region monitoring and some modes survive force quit on iOS

The story

What it is

A person can kill an app for good, and the phone then blocks it from running in the background.

For you

You swipe the app away or tap Force stop. From then on the app cannot send alerts or sync until you open it again, which can surprise you when a reminder never shows up.

For makers

Makers treat a force stop as a clear sign someone wants out. They know push and timed jobs will fail, so they design gentle re-engagement for the next time the user returns.

Where you see it

TypeExampleApps
messagingAfter you force quit a chat app, messages stop arriving as alerts until you open it.WhatsApp, Telegram
fitnessA step counter or sleep tracker stops logging in the background and leaves a gap in your day.None named
gamesA game with timed energy refills cannot send you the full energy alert after you force close it.Clash of Clans
adsAn ad measurement tool sees a gap in sessions and cannot record background events until the next open.None named
analyticsA product team sees a spike of users who force stop right after an update and treats it as a quality warning.None named
securityA banking app cannot run its background fraud checks after a force stop, so it checks again at next launch.None named

Risks

  • Missed alerts and reminders
  • Gaps in tracking data

Android and iPhone in short

  • Android: Force stop sets a stopped state that blocks broadcasts and cancels alarms and jobs.
  • iPhone: Force quit makes iOS discard silent pushes. Some wake ups like VoIP and location can still reach the app.

What the platform says

  • Apple: Close an app. Apple documents how to close an app on iPhone by swiping up in the app switcher.

Good uses and abuse

Legitimate uses

  • User control

Known abuse

  • None

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

  • 2012-04, Android 3.1 (API 12): Stopped state introduced
  • 2013-09, iPhone iOS 7: Force quit prevents background fetch and silent push

Same idea on the web

Sources

How well checked: Based on official documentation.

On this page