Home iOS & Swift Books UIKit Apprentice

27
Saving Locations Written by Fahim Farook

Heads up... You're reading this book for free, with parts of this chapter shown beyond this point as scrambled text.

You can unlock the rest of this book, and our entire catalogue of books and videos, with a raywenderlich.com Professional subscription.

Unlock Now

At this point, you have an app that can obtain GPS coordinates for the user’s current location. It also has a screen where the user can “tag” that location, which consists of entering a description and choosing a category. Later on, you’ll also allow the user to pick a photo.

The next feature is to make the app remember the locations that the user has tagged.

This chapter covers the following:

  • Core Data overview: A brief overview of what Core Data is and how it works.
  • Add Core Data: Add the Core Data framework to the app and use it.
  • The data store: Initializing the data store used by Core Data.
  • Pass the context: How to pass the context object used to access Core Data between view controllers.
  • Browse the data: Looking through the saved data.
  • Save the locations: Saving entered location information using Core Data.
  • Handle Core Data errors: Handling Core Data errors when there’s an issue with saving.

Core Data overview

You have to persist the data for these captured locations somehow — they need to be remembered even when the app terminates.

The last time you did this, you made data model objects that conformed to the Codable protocol and saved them to a .plist file. That works fine, but in this chapter I want to introduce you to a framework that can take a lot of work off your hands: Core Data.

Core Data is an object persistence framework for iOS apps. If you’ve looked at Core Data before, you may have found the official documentation a little daunting, but the principle is quite simple.

You’ve learned that objects get destroyed when there are no more references to them. In addition, all objects get destroyed when the app terminates.

With Core Data, you can designate some objects as being persistent so they will always be saved to a data store. Even when all references to such a managed object are gone and the instance gets destroyed, its data is still safely stored in Core Data and you can retrieve the data at any time.

If you’ve worked with databases before, you might be tempted to think of Core Data as a database, but that’s a little misleading. In some respects, the two are indeed similar, but Core Data is about storing objects, not relational tables. It is just another way to make sure the data from certain objects don’t get deleted when these objects are deallocated or the app terminates.

Using Core Data

Core Data requires the use of a data model. This is a special file that you add to your project to describe the objects that you want to persist. These managed objects, unlike regular objects, will keep their data in the data store till you explicitly delete them.

The data model

Back in Chapter 22, when you first created the MyLocations project, the project settings had an option named Use Core Data. At that point, I mentioned that you should enable the option and that you’ll learn what this option does later on, in this chapter.

The empty data model
Cge uggnp veda tonic

The new Location entity
Tku leh Wizucioh ubnuvl

Choosing the attribute type
Mfuusisq yla ekmpehixu zhke

All the attributes of the Location entity
Oqq tra irzriqiyot oh fri Yorodoov ikbijh

Making the category attribute non-optional
Suceps hqu huyudaxc ohqqipake bex-agniaxiq

Generate the code

➤ Click on the Location entity to select it and go to the Data Model inspector.

The Data Model inspector
Xlo Gami Bumul aqstuzvot

import Foundation
import CoreData

@objc(Location)
public class Location: NSManagedObject {
  
}

import Foundation
import CoreData

extension Location {
    @nonobjc public class func fetchRequest() -> NSFetchRequest<Location> {
        return NSFetchRequest<Location>(entityName: "Location")
    }

    @NSManaged public var latitude: Double
    @NSManaged public var longitude: Double
    @NSManaged public var date: Date?
    @NSManaged public var locationDescription: String?
    @NSManaged public var category: String?
    @NSManaged public var placemark: NSObject?
}

extension Location : Identifiable {

}

Fix the code

Unfortunately, Xcode made a few small boo-boos in the types of the properties, so you’ll have to make some changes to Location+CoreDataProperties.swift.

import CoreLocation

@NSManaged public var placemark: CLPlacemark?

The data store

On iOS, Core Data stores all of its data into an SQLite — pronounced “SQL light” — database. It’s OK if you have no idea what SQLite is. You’ll take a peek into that database later, but you don’t really need to know what goes on inside the data store in order to use Core Data.

import CoreData

lazy var persistentContainer: NSPersistentContainer = {
  let container = NSPersistentContainer(name: "MyLocations")
  container.loadPersistentStores {_, error in
    if let error = error {
      fatalError("Could not load data store: \(error)")
    }
  }
  return container
}()

lazy var managedObjectContext = persistentContainer.viewContext

(UIApplication.shared.delegate as? AppDelegate)?.saveContext()

saveContext()

Pass the context

When the user presses the Done button in the Tag Location screen, the app currently just closes the screen. Let’s fix that and actually save a new Location object into the Core Data store when the Done button is tapped.

Get the context

➤ Switch to LocationDetailsViewController.swift. First, import Core Data at the top, and then add a new instance variable:

var managedObjectContext: NSManagedObjectContext!

var managedObjectContext: NSManagedObjectContext!

override func prepare(
  for segue: UIStoryboardSegue, 
  sender: Any?
) {
  if segue.identifier == "TagLocation" {
    . . .
    // New code
    controller.managedObjectContext = managedObjectContext 
  }
}

var managedObjectContext: NSManagedObjectContext

var managedObjectContext: NSManagedObjectContext?

Pass the context from SceneDelegate

SceneDelegate.swift now needs some way to pass the NSManagedObjectContext object to CurrentLocationViewController.

func scene(
  _ scene: UIScene, 
  willConnectTo session: UISceneSession, 
  options connectionOptions: UIScene.ConnectionOptions
) {
  let tabController = window!.rootViewController as! UITabBarController
  if let tabViewControllers = tabController.viewControllers {
    let navController = tabViewControllers[0] as! UINavigationController
    let controller = navController.viewControllers.first as! CurrentLocationViewController
    controller.managedObjectContext = managedObjectContext
  }
}

let container = NSPersistentContainer(name: "MyLocations")
container.loadPersistentStores {_, error in
  if let error = error {
    fatalError("Could not load data store: \(error)")
  }
}
return container

var persistentContainer: NSPersistentContainer

init() {
  persistentContainer = createPersistentContainer()
}

func createPersistentContainer() -> NSPersistentContainer {
  // all the initialization code here
  return container
}

lazy var persistentContainer: NSPersistentContainer = { ... }()

lazy var managedObjectContext = persistentContainer.viewContext

Browse the data

Core Data stores the data in an SQLite database. That file is named MyLocations.sqlite and it lives in the app’s Library folder. That’s similar to the Documents folder that you saw previously.

Core Data data store location

➤ The easiest way to find the location of the Core Data folder is to add the following to Functions.swift:

let applicationDocumentsDirectory: URL = {
  let paths = FileManager.default.urls(
    for: .documentDirectory, 
    in: .userDomainMask)
  return paths[0]
}()

print(applicationDocumentsDirectory)

file:///Users/fahim/Library/Developer/CoreSimulator/Devices/31DCE39D-CEC6-4228-B6DF-98FA08E5544F/data/Containers/Data/Application/D21A7746-093C-4431-82CF-917A86AB7186/Documents/
The new database in the app’s Documents directory
Kxi ced jakadudu ap qva ahp’l Desikemcd zopishicz

Browse the Core Data store using a GUI app

You will use Liya to examine the data store file. Download it from the Mac App Store or cutedgesystems.com/software/liya/.

Liya opens with this dialog box
Wuno upaxf poqk hyuh puaxoh bum

Connecting to the SQLite database
Rowsiqpezn mi hko NSRihi tudirazi

The empty MyLocations.sqlite database in Liya
Sza irprk QdWudoraacq.dxjuya yolanayi el Tuqe

Troubleshoot Core Data issues

There is another handy tool for troubleshooting Core Data. By setting a special flag on the app, you can see the SQL statements that Core Data uses under the hood to talk to the data store.

The Edit Scheme... option
Zti Atuy Npreju... epsoab

The scheme editor
Fye rltehi obezuq

-com.apple.CoreData.SQLDebug 1
-com.apple.CoreData.Logging.stderr 1
Adding the SQLDebug launch argument
Etziwg rxo RNJToxac jiuygr akzacuxf

CoreData: annotation: Connecting to sqlite database file at "/Users/fahim/Library/Developer/CoreSimulator/Devices/31DCE39D-CEC6-4228-B6DF-98FA08E5544F/data/Containers/Data/Application/2BB1CA6C-E43C-4D48-B744-90206ECD3667/Library/Application Support/MyLocations.sqlite"
CoreData: sql: SELECT TBL_NAME FROM SQLITE_MASTER WHERE TBL_NAME = 'Z_METADATA'
CoreData: sql: pragma recursive_triggers=1
CoreData: sql: pragma journal_mode=wal
CoreData: sql: SELECT Z_VERSION, Z_UUID, Z_PLIST FROM Z_METADATA
CoreData: sql: SELECT TBL_NAME FROM SQLITE_MASTER WHERE TBL_NAME = 'Z_METADATA'
CoreData: sql: SELECT TBL_NAME FROM SQLITE_MASTER WHERE TBL_NAME = 'Z_MODELCACHE'
CoreData: sql: SELECT TBL_NAME FROM SQLITE_MASTER WHERE TBL_NAME = 'ACHANGE'
CoreData: sql: SELECT TBL_NAME FROM SQLITE_MASTER WHERE TBL_NAME = 'ATRANSACTIONSTRING'

Save the locations

You’ve successfully initialized Core Data and passed the NSManagedObjectContext to the Tag Location screen. Now it’s time to put a new Location object into the data store when the Done button is pressed.

var date = Date()

dateLabel.text = format(date: date)

@IBAction func done() {
  guard let mainView = navigationController?.parent?.view 
  else { return }
  let hudView = HudView.hud(inView: mainView, animated: true)
  hudView.text = "Tagged"
  // 1
  let location = Location(context: managedObjectContext)
  // 2
  location.locationDescription = descriptionTextView.text
  location.category = categoryName
  location.latitude = coordinate.latitude
  location.longitude = coordinate.longitude
  location.date = date
  location.placemark = placemark
  // 3
  do {
    try managedObjectContext.save()
    afterDelay(0.6) {
      hudView.hide()
      self.navigationController?.popViewController(
        animated: true)
    }
  } catch {
    // 4
    fatalError("Error: \(error)")
  }
}

CoreData: sql: BEGIN EXCLUSIVE
. . .
CoreData: sql: INSERT INTO ZLOCATION(Z_PK, Z_ENT, Z_OPT, ZCATEGORY, ZDATE, ZLATITUDE, ZLOCATIONDESCRIPTION, ZLONGITUDE, ZPLACEMARK) VALUES(?, ?, ?, ?, ?, ?, ?, ?, ?)
. . .
CoreData: sql: COMMIT
A new row was added to the table
E ruk yuh req anked yu zqi lajbu

Examining the database from the Terminal
Oguxuqirb ylu zelikebe slam dza Dornotas

Handle Core Data errors

To save the contents of the context to the data store, you did:

do {
  try managedObjectContext.save()
  . . .
} catch {
  fatalError("Error: \(error)")
}

Fake errors for testing purposes

Here’s a way to fake such a fatal error, just to illustrate what happens.

Making the placemark attribute non-optional
Cayann cfa wlutajizb azvkubobe jiq-arfuinay

reason=Validation error missing attribute values on mandatory destination attribute, . . .
The app crashes after a Core Data error
Dda enl llillas ewnes i Maso Koju opwav

NSValidationErrorKey=placemark

Alert the user about crashes

➤ Add the following code to Functions.swift:

let dataSaveFailedNotification = Notification.Name(
  rawValue: "DataSaveFailedNotification")

func fatalCoreDataError(_ error: Error) {
  print("*** Fatal error: \(error)")
  NotificationCenter.default.post(
    name: dataSaveFailedNotification, 
    object: nil)
}

. . .
} catch {
  fatalCoreDataError(error)
}

NotificationCenter.default.post(name: dataSaveFailedNotification, object: nil)

// MARK: - Helper methods
func listenForFatalCoreDataNotifications() {
  // 1
  NotificationCenter.default.addObserver(
    forName: dataSaveFailedNotification,
    object: nil, 
    queue: OperationQueue.main
  ) { _ in
      // 2
      let message = """
      There was a fatal error in the app and it cannot continue.

      Press OK to terminate the app. Sorry for the inconvenience.
      """
      // 3
      let alert = UIAlertController(
        title: "Internal Error", 
        message: message,
        preferredStyle: .alert)

      // 4
      let action = UIAlertAction(title: "OK", style: .default) { _ in
        let exception = NSException(
          name: NSExceptionName.internalInconsistencyException,
          reason: "Fatal Core Data error", 
          userInfo: nil)
        exception.raise()
      }      
      alert.addAction(action)

      // 5
      let tabController = self.window!.rootViewController!
      tabController.present(
        alert, 
        animated: true, 
        completion: nil)
  }
}

listenForFatalCoreDataNotifications()
The app crashes with a message
Wma esp rbojsom cosg o poslara

28. The Locations Tab 26. Adding Polish

Have a technical question? Want to report a bug? You can ask questions and report bugs to the book authors in our official book forum here.

Have feedback to share about the online reading experience? If you have feedback about the UI, UX, highlighting, or other features of our online readers, you can send them to the design team with the form below:

© 2021 Razeware LLC

You're reading for free, with parts of this chapter shown as scrambled text. Unlock this book, and our entire catalogue of books and videos, with a raywenderlich.com Professional subscription.

Unlock Now

To highlight or take notes, you’ll need to own this book in a subscription or purchased by itself.

Read for Free with a Subscription

Buy this book for $59.99