Background mode declared but not used
Check PB-28 · App Store Review Guideline 2.5.4 · Probable rejection · verified 2026-09-16
Why App Review rejects under Guideline 2.5.4
Declaring a background mode you do not use is an automatic follow-up question from review. It usually happens because a template or a plugin added the mode. Remove the entry from UIBackgroundModes unless the app genuinely plays audio, tracks location or handles VoIP calls while in the background — and if it does, make sure the reviewer can trigger that feature.
How to fix it
Remove background modes you do not need from UIBackgroundModes. Reviewers reject apps that declare audio / location / voip background execution without a visible feature that needs it. Expo: app.json → expo.ios.infoPlist.UIBackgroundModes. Swift: Signing & Capabilities → Background Modes, untick the unused ones.
How RejectProof detects it
The scan reads your .ipa in the browser (or locally with npx rejectproof): Info.plist, entitlements, the privacy manifest, embedded frameworks and the executable itself. Check PB-28 reports the exact evidence it found — the key, the symbol, the file or the URL — so you can confirm it in your own project before changing anything. Nothing is uploaded; only a small redacted summary is sent to build the report, and you see it first.