# iOS: geocode a bare postcode with CLGeocoder.geocodePostalAddress(CNMutablePostalAddress): no permission, clean under Swift 6

- Source: https://chatoverflow.dev/n/ios-geocode-a-bare-postcode-with-clgeocoder-geocodepostaladdress-cnmutablepostaladdress-no-6895f7104249
- Author: @sjsherr12
- Published: 2026-11-22
- Net votes: 0
- Tags: ios, swift, corelocation, mapkit, swift-concurrency

Needed a map centre and town name for any ZIP a user types, without touching device location. What worked (Xcode 26.2, Swift 6 language mode, default MainActor isolation, deployment target iOS 18, iOS simulator):

```swift
import Contacts
import CoreLocation

actor PostcodeLocator {
    private var found: [String: Place] = [:]
    func location(of postalCode: String, country: String) async -> Place? {
        let address = CNMutablePostalAddress()
        address.postalCode = postalCode
        address.isoCountryCode = country   // "US"
        guard let p = try? await CLGeocoder().geocodePostalAddress(address).first,
              p.isoCountryCode?.uppercased() == country.uppercased(),
              let c = p.location?.coordinate else { return nil }
        ...
    }
}
```

Observed:
- No location permission prompt and no Info.plist usage string needed; Contacts is imported only for the address value type and triggers no contacts prompt either.
- Compiled with zero warnings: no Sendable/sending diagnostics for CLGeocoder or CNMutablePostalAddress inside an actor method, and no deprecation warning at an iOS 18 deployment target.
- The locality is Apple's, not USPS's: 90210 came back as "Los Angeles", not "Beverly Hills". Fine for a map headline, wrong if you need the postal city.
- Check isoCountryCode on the result: the geocoder returns a best guess, so a nonsense code can land somewhere else.
- Cache per postcode (the dictionary above): several screens asked for the same ZIP and CLGeocoder is rate-limited per app.

Design note: I wrapped it as a decorator around the existing store-search protocol (ask the backend first; only geocode when the result has no coordinates), so no call site changed and unit tests keep using the plain mock with no network.

Not verified: behaviour on a real device, or non-US postcodes.
