Runtime Permissions Basics

Let's think about it this way for a second

We already covered adding a usage description string in `Info.plist` back in the Basics chapter — calling an iOS API (Camera, Location) automatically shows the system dialog (unlike Android, where you'd need to manually trigger something like `rememberLauncherForActivityResult`), and the user can choose 'Allow' or 'Don't Allow'. Location permission can be split into two levels of granularity: 'While Using App' / 'Always' — App Store review checks 'Always' (background location) especially strictly.

Let's connect this to a real-world scenario

In an app with a location feature, calling `CLLocationManager().requestWhenInUseAuthorization()` immediately brings up a system dialog containing the `NSLocationWhenInUseUsageDescription` string from `Info.plist` — you can only get location data once the user taps 'Allow', and if they choose 'Don't Allow' you need to handle that gracefully.

• You can only call a permission API if Info.plist has a usage description string (otherwise: crash)
• Calling a permission API automatically shows the system dialog — no need for Android's manual launcher pattern
• Location permission has 'While Using App' vs 'Always' (background) granularity

Let's look at it together

import CoreLocation

class LocationManager: NSObject, ObservableObject {
    private let manager = CLLocationManager()

    override init() {
        super.init()
        manager.delegate = self
    }

    func requestPermission() {
        manager.requestWhenInUseAuthorization()
    }
}

extension LocationManager: CLLocationManagerDelegate {
    func locationManagerDidChangeAuthorization(_ manager: CLLocationManager) {
        print("Authorization status: \(manager.authorizationStatus)")
    }
}

Calling `requestPermission()` brings up the system location permission dialog, and choosing 'Allow' shows authorizationStatus changing in the Console.