iOS lets apps declare specific background modes such as audio, location, or VoIP — using one of those modes for a purpose it wasn't designed for, just to keep the app alive in the background, is a violation.
Common when an app declares the "audio" background mode to keep running for an unrelated reason like syncing data or tracking analytics.
"Your app uses background modes for purposes other than their intended use, per guideline 2.5.4. The 'audio' background mode should only be used for continuous audio playback."
Guideline 2.5.4 permits apps to use iOS background modes only for the tasks they were designed for. Declaring a mode such as audio, location or VoIP in order to keep an app running for another reason is a violation. Reviewers look at whether the declared mode matches real functionality.
Background execution is a shared, limited resource. Each declared mode exists because a specific kind of app genuinely needs to keep working when the screen is off, such as a navigation app or a music player. When apps borrow a mode for something else, they drain batteries and crowd out the apps that rely on it legitimately. The rule is meant to keep background privileges tied to user-visible purposes, so the device stays responsive and battery life stays predictable.
Examples include audio, location, VoIP, background fetch and more, each with defined purposes.
Through the mechanisms the system provides for that purpose.
Yes, it is part of the same concern.
Platform rules change often. This page is a plain-language explanation written by AppReviewFix, not official guidance. Check the current App Store Review Guidelines for the exact wording.