Guideline 2.5.4 rejection: Background modes used for other purposes
What it means, why it happens, and how developers get through it.
Subject line you may see: Guideline 2.5.4 - Performance - Software Requirements
What Apple's guideline says
Multitasking apps may only use background services for their intended purposes: VoIP, audio playback, location, task completion, local notifications, etc.
From App Review Guidelines, 2.5.4, as revised October 16, 2026.
Common causes
- The audio background mode is declared to keep the app alive, not to play audio
- Background location declared without a feature that needs it
- A background mode left over from a template or old feature
- The feature that needs background mode is hard for the reviewer to find
How to fix it
- Remove every background mode the app does not truly use (UIBackgroundModes in Info.plist)
- For the modes you keep, make sure the feature uses them for their intended purpose
- Explain in Notes for Review which feature uses each mode and how to see it
- Ship a new build and reply with the path to the feature
What to put in your reply
A sample reply note. Replace the brackets with your facts and remove anything that does not apply.
Hello, Thank you for the review. Regarding Guideline 2.5.4, build [number] [removes the audio background mode / uses background location only for (feature)]. To see it: 1. [step] 2. [step]. Thank you.
Real cases: others who got 2.5.4
No public cases logged yet.
Questions developers ask about 2.5.4
What does a Guideline 2.5.4 rejection mean?
Your app declares a background mode, such as audio or location, but does not use it for that purpose, or the reviewer could not find the feature that needs it.
Why do apps get rejected under Guideline 2.5.4?
Common causes, based on Apple's guideline text: the audio background mode is declared to keep the app alive, not to play audio; background location declared without a feature that needs it; A background mode left over from a template or old feature; the feature that needs background mode is hard for the reviewer to find.
How do I fix a Guideline 2.5.4 rejection?
1. Remove every background mode the app does not truly use (UIBackgroundModes in Info.plist). 2. For the modes you keep, make sure the feature uses them for their intended purpose. 3. Explain in Notes for Review which feature uses each mode and how to see it. 4. Ship a new build and reply with the path to the feature.
Do I need a new build for Guideline 2.5.4?
Fix, new build, then reply. Something in the binary has to change. Fix it, bump the build, resubmit, and reply with what changed and how to verify. This is how the guideline is usually resolved, not a prediction for your app.
How should I reply to App Review about Guideline 2.5.4?
Reply in App Store Connect. Thank the reviewer and name Guideline 2.5.4, say exactly what changed and in which version and build, give a numbered path the reviewer can follow, and attach proof such as screenshots or a screen recording.
Stuck on 2.5.4?
Do it yourself, faster
App Store Rejection Rescue Kit: the full decoder, 12 reply templates, Notes for Review templates, and a 60-point preflight checklist.
Get the kit, $12Have it written for you
Send your rejection, get a reply drafted for your exact case. Kit buyers get $10 off.
AI-assisted, built on Apple's App Review Guidelines. Not a guarantee of approval. If we do not deliver within 24 hours, you get a full refund.
Reply service, $29Related rejections
See also: 2.5.1 public APIs · 5.1.1 privacy
Source: Apple's App Review Guidelines, section 2.5.4, as revised October 16, 2026. Last checked . Always read the current official text. How we write these guides.