App Store rejectionApp Store Guideline 2.5.4: background modes used for the wrong purpose

Rather not fix it yourself? App Fix Ticket starts with a fixed-price diagnosis, then a fixed price for the fix before any fix work.

Why Apple flags the mode, and the fix

1. 01

   A mode is on that no feature uses

   “Multitasking apps may only use background services for their intended purposes: VoIP, audio playback, location, task completion, local notifications, etc.” Apple, Guideline 2.5.4

   A template, a tutorial or an old feature can leave Audio, Location updates, Background fetch, Background processing or Bluetooth switched on. Reviewers check each declared mode, so turn off the ones the app doesn’t use. Xcode stores them in UIBackgroundModes in Info.plist.

   <!-- Info.plist, example only: keep a mode only if a shipping feature uses it,
        including remote-notification (silent push) -->
   <key>UIBackgroundModes</key>
   <array>
     <string>remote-notification</string>
   </array>

2. 02

   Audio is on to keep the app alive

   “The app plays audible content in the background.” Apple Developer, Background execution modes (audio)

   Playing silent audio to keep the app running in the background is not what the audio mode is for. The audio mode is for apps that play sound the user hears, such as music, podcasts or navigation prompts.

3. 03

   Location updates where significant-change would do

   “For example, apps can use the significant-change location service to receive location events as an alternative to using the Location updates background mode.” Apple Developer, Configuring background execution modes

   Continuous background location drains the battery, so the reviewer looks for a feature that needs it, such as turn-by-turn directions or workout tracking. For check-ins or nearby alerts, use significant-change location or region monitoring, which don’t need the mode. They still need the Always permission and a clear purpose string.

4. 04

   A plugin or Expo config turned the mode on

   Flutter and React Native plugins for audio, location or geofencing may ask you to add a background mode in their setup steps. In Expo, a config plugin or ios.infoPlist.UIBackgroundModes in app.json can add modes at build time. Remove the entry, run npx expo prebuild --clean, and check the generated Info.plist. If the feature isn’t in this release, remove the mode, or the plugin.

5. 05

   The feature exists but the reviewer didn’t find it

   “Use background execution modes sparingly because overuse can negatively impact device performance and battery life.” Apple Developer, Configuring background execution modes

   If the mode is needed, say where in the reply: which screen, which action starts it, and what keeps working in the background. Use App Review Information notes for the next submission, and add a demo account if the feature needs sign-in.

Checked against the vendor’s docs on November 9, 2026: App Store Review Guidelines: 2.5.4; Apple Developer: Configuring background execution modes.

Rather hand it over?

Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.

• from $450App Fix TicketOne reproducible bug in an existing mobile or web app, diagnosed and fixed.See scope and start

Related: App Store Guideline 2.5.1 · App Store Guideline 2.1 · App Store Guideline 5.1.1 · App Store Guideline 5.1.2