O'Reilly logo

Programming iOS 10 by Matt Neuburg

Stay ahead with the world's most comprehensive technology and business learning platform.

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, tutorials, and more.

Start Free Trial

No credit card required

Chapter 19. Calendar

The user’s calendar information, which the user sees through the Calendar app, is effectively a database of calendar events. The calendar database also includes reminders, which the user sees through the Reminders app. This database can be accessed directly through the Event Kit framework. You’ll need to import EventKit.

A user interface for interacting with the calendar is also provided, through the Event Kit UI framework. You’ll need to import EventKitUI.

The calendar database is accessed as an instance of the EKEventStore class. This instance is expensive to obtain but lightweight to maintain, so your usual strategy will be to instantiate and retain one EKEventStore instance. There is no harm in initializing a property or global as an EKEventStore instance and keeping that reference for the rest of the app’s lifetime:

let database = EKEventStore()

In the examples in this chapter, my EKEventStore instance is called self.database throughout.

Access to the calendar database requires user authorization. You’ll use the EKEventStore class for this. Although there is one database, access to calendar events and access to reminders are considered two separate forms of access and require separate authorizations. To learn what the current authorization status is, call the class method authorizationStatus(for:) with an EKEntityType, either .event (for access to calendar events) or .reminder (for access to reminders). To ask the system to put up the authorization request ...

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, interactive tutorials, and more.

Start Free Trial

No credit card required