Handle location and geocoding with SwiftUI
I’m continuing on my Weather app research in SwiftUI. My next problem is this:
How do I get the current location (as a longitude / latitude) and a place (like a city) in my app such that the UI is updated when location updates happen?
It turns out that this is a fairly easy problem, but it does come with some knowledge that you just have to know. Here is the list:
- How can I update the UI based on programmatic changes to the value?
- How can I listen for location updates?
- How can I convert a location into a place (also known as geocoding)?
Let’s tackle this one by one.
Update the UI with an ObservableObject
The first is handling updates to the UI based on programmatic changes to the value. I have three values I need to deal with:
- The location
- The state of the location service
- The geocoding of the location
There are multiple ways to do this, including the ubiquitous environment object. However, I’m going to use an
ObservableObject for this function. This isn’t my app state. I want to inject the observation wherever I need it, and I don’t mind if the data is duplicated since the location is the location.
Here is an observable object:
This only has one variable. However, when I change
someVar, all the views that are hooked into it will be updated too. That’s the point of the
objectWillChange and the
willSet call. The import of
Combine is what makes all this possible.
For example, here is a
ContentView that hooks into it:
When you click on the button, the
someVar within the location manager will increment, which will in turn update the UI. This gives us the basis for updating the UI programatically.
Get the location with CLLocationManager
Next, let’s update our
LocationManager so that it actually handles the location. This is done in two parts:
- Set up a
CLLocationManagerDelegatethat will update the location.
- Start listening for updates.
First, you have to add an entry into the
Info.plist. I’m going to ask for “when-in-use” permission to use the location. You should always only ask for permissions you absolutely need, otherwise you risk losing your customers to privacy concerns. The permission you want is labelled “Privacy - Location When In Use Usage”. Underneath, it’s called
NSLocationWhenInUseUsageDescription. Add it to the
Info.plist and fill in the value (as a string) with the reason for needing permission.
Now the preliminaries are over, let’s look at that delegate:
CLLocationManager (that we set up next) receives an authorization update, it will set the status. When it receives a location update, it will set the location and kick off a geocode of the current location.
Turning our attention to the
LocationManager itself now, we need to remove
someVar (since we don’t need it any more), and replace it with the following:
Together with the preceding listing (which I place in the same swift file), the location and status are updated. The interesting stuff is in the
init() code. It should be self-explanatory. The only difficult part is “where is the delegate?” - that’s the extension methods we wrote earlier.
Use the geocoder to turn location into a placemark
The final piece is to turn the location into the placemark. I’ve already produced a dummy call to
geocode() which is called whenever the location changes. All I need to do now is to fill it in:
completionHandler is an async return value. The geocoder method will return immediately, but it will continue to work in the background. When it is complete, it will call the completion handler with the results. We then set the new placemark and the view observing this value will get the update.
Use it in a view
Here is the view I use to test:
I’m still getting the values in the same way, but now I have access to the location and the placemark. I like “promoting” the latitude and longitude to the be properties on the
CLLocation. By default, they are buried inside the
coordinate property. To do the promotion, I have the following code:
This code is placed in the same place as the
The location manager doesn’t work inside the preview window. For this reason, I’m going to be switching to a “fake” location manager that is attached when running in debug mode. This will allow me to inject a fake location by constructing the three variables I need. You will always need to check the status (ensure the value is
.authorizedAlways) and don’t add the “current location” when you are not authorized.
When you run it in the simulator, you will be prompted for the permission to use location, then see the following:
This is my first peek into the application state (and outside the UI), and it turned out to be really easy.
Leave a comment