Lorixen.
EN

iOS background refresh not running? What to expect and fix

Short answer: iOS decides when background tasks run, not your app. When you schedule a background refresh or processing task, the earliest start time you set is only a "not before", and Apple's documentation warns the gap before the system launches the task can be many hours. Tasks also don't run at all if setup is incomplete, if Background App Refresh is off or in Low Power Mode, or if the work takes too long and is cut off. Fix the setup, design for late and missed runs, and use a background push or a regular notification when something genuinely has to reach the user promptly.

How iOS background tasks work

Apple's guidance on choosing background strategies describes several options:

  • Finishing work after the app goes to the background, such as saving a file or sending a message, with a limited amount of extra time.
  • Background downloads and uploads, handled by the system.
  • App refresh tasks for short bursts, such as fetching fresh content. The system decides when to launch them and gives up to 30 seconds.
  • Processing tasks for heavier work, scheduled for quiet times such as overnight while the device is charging.
  • Background pushes, silent notifications from your server that let the app fetch new content.

Background tasks are opportunistic. The documentation for the earliest start date is explicit: the system doesn't guarantee launching the task at that time, only that it won't start sooner.

Setup mistakes that stop tasks running

Apple's background tasks guide lists the setup, and missing any part of it means the task never runs:

  1. Enable the Background Modes capability in the app target, with "Background fetch" for refresh tasks and "Background processing" for processing tasks.
  2. List each task identifier under "Permitted background task scheduler identifiers" in the app's Info.plist. An identifier missing from that list can't be scheduled.
  3. Register a handler for every task before the app finishes launching. The guide says to register all tasks before the end of the launch sequence. Registering later, for example after login, is a common bug.
  4. Register in the main app. An extension can schedule a task, but the main app must register it.
  5. Schedule the next run. A refresh task runs once per request. Submitting a new request replaces the previous one, so schedule the next refresh inside the handler.
  6. Handle expiry and report completion. Provide an expiration handler for when the system needs to stop your task, and mark the task complete when done.

Reasons that aren't bugs

Even with correct setup, tasks run less often than developers expect:

  • Background App Refresh can be off. Apple's documentation notes that some users are restricted from enabling it, for example under parental controls, and that it's disabled automatically in Low Power Mode.
  • The system weighs usage. Apps people open regularly tend to get more background time than rarely used ones. Apple doesn't publish exact rules, so treat timing as unpredictable.
  • Force-quitting the app from the app switcher usually stops background launches until the user opens it again.
  • Device conditions matter. Processing tasks may wait for charging, a network connection or idle time.

Your app can check the Background App Refresh status and, as Apple's documentation suggests, explain it to the user when it's turned off but available.

Design for late and missed runs

Since background time isn't guaranteed, the app should:

  • Refresh when it opens rather than assuming data is current.
  • Keep work small. Refresh tasks get a short window, so fetch only what changed.
  • Save progress as you go, so work interrupted by the expiration handler can continue next time.
  • Move heavy work to processing tasks or to your server.
  • Show when data was last updated, so customers aren't misled.

When something must arrive promptly

If customers need to know about an order update, a booking change or a new message, don't rely on background refresh.

Background pushes let your server wake the app when there's new content. Apple's guidance says to send them with content-available set and no alert, sound or badge, and with the background push type and priority. The app then gets up to 30 seconds. The documentation warns that sending them more often than about three times per hour leads to rate limits, so they suit occasional updates.

Visible notifications are the reliable way to tell someone something now. If you need to process content before showing it, Apple describes a Notification Service Extension that can modify the notification first.

Testing without waiting hours

Apple's development documentation acknowledges the delay can be many hours, and describes debugger commands to start a task immediately or force it to expire, on a real device. These are private functions for development only; Apple says including them in an App Store app is cause for rejection. Test the expiration path as well as the success path, and test with Low Power Mode and Background App Refresh switched off.

An illustrative example

A grocery delivery app in Calgary schedules a background refresh to update customers' order status, but drivers report customers seeing stale information. The team finds the task was registered after sign-in, not at launch, and was never rescheduled after it ran. They fix registration, reschedule in the handler, refresh status whenever the app opens, and switch order updates to visible notifications sent from the server. Background refresh remains for non-urgent catalogue updates.

FAQ

Can I make background refresh run every 15 minutes?

You can request an earliest time, but the system decides when it actually runs.

Why does it work in testing but not for customers?

Testing often uses debugger commands or a heavily used device. Real usage, battery settings and force-quitting change the timing.

Is a silent push guaranteed to wake the app?

No. The system can delay or limit them.

Should sync happen in the background at all?

Yes, as a bonus. Make sure the app still syncs when opened.

If your iPhone app relies on background updates that aren't happening, tell us what it needs to keep up to date.

Sources

WhatsAppBook a call