Guideline 5.1.1
Guideline 5.1.1 - Privacy: Background Location Without Proper Configuration
Low RiskEasy0 Reports
Our Take
Your app declares background location capability but is missing required configuration. Apple scrutinizes background location heavily — apps must demonstrate clear user-facing value and have all required purpose strings.
Resolution Guide
01
**Verify you need background location** — Background location is only appropriate for navigation, fitness tracking, ride-sharing, or similar apps where continuous location is the core feature. If your app only needs location while in the foreground, remove `location` from `UIBackgroundModes` and use `requestWhenInUseAuthorization` only.
02`NSLocationWhenInUseUsageDescription` — explain why you need location while the app is visible
**Add all required purpose strings** — You need BOTH of these in Info.plist:
- `NSLocationAlwaysAndWhenInUseUsageDescription` — explain why you need location in the background. Be specific: "Chain tracks your ride route in the background so you can see your complete path and distance even when your phone is locked."
03
**Implement proper location authorization flow** — Request `requestWhenInUseAuthorization` first. Only escalate to `requestAlwaysAuthorization` when the user triggers a feature that needs it. Never request Always on first launch.
04
**Enable background location updates in code** — Set `locationManager.allowsBackgroundLocationUpdates = true` and `locationManager.showsBackgroundLocationIndicator = true` (shows the blue bar).
05Start with WhenInUse authorization and only add Always when the feature demands it Always include review notes explaining background location usage Test that the blue location indicator appears during background tracking
**Prepare your review notes** — In App Store Connect → App Review Information, explain exactly why your app needs background location. Example: "Our app tracks cycling rides. Background location is required so the route is recorded accurately when the screen is locked during a ride."
Prevention:
Community Solutions · 0
Sign in to share your solution.
More Guideline 5 (Legal) rejections
- Guideline 5 - Legal: Remove Watermark Feature
- Guideline 5.1.1 - Data Collection and Storage: Incomplete Privacy Manifest
- Guideline 5.1.1 - Data Collection and Storage: Missing Purpose Strings
- Guideline 5.1.1 - Data Collection and Storage: Privacy Manifest Missing
- Guideline 5.1.1 - Data Collection and Storage: Privacy Nutrition Label Mismatch
- Guideline 5.1.1 - Data Collection and Storage: Privacy Policy