7.
Expanding the Application
Written by Scott Grosch
Heads up... You’re accessing parts of this content for free, with some sections shown as text.
Heads up... You’re accessing parts of this content for free, with some sections shown as text.
Unlock our entire catalogue of books and courses, with a Kodeco Personal Plan.
Unlock now
Now that you’ve got a database up and running, you need to tell your app how to connect to it. As you saw in the previous chapter, “Server Side Pushes,” Vapor will run a local server for you at an address like http://192.168.1.1:8080 (change with your own IP address).
This is the URL that your app will need to talk to if you successfully registered for push notifications. Of course, remember to substitute your IP address in the URL.
Token Details
You’ll want to be able to pass appropriate details to your web service which describes the user’s push notification registration.
Open the starter project from this chapter’s materials, then create a new Swift file called TokenDetails.swift and add the following code:
struct TokenDetails {
let token: String
let debug: Bool
}
Your web service expects JSON data, so add an encoder to the top of the struct:
private let encoder = JSONEncoder()
To use the JSONEncoder, your struct must conform to Encodable. Add the following extension:
extension TokenDetails: Encodable {
private enum CodingKeys: CodingKey {
case token, debug
}
}
You need to explicitly specify the CodingKeys because Swift, by default, will attempt to encode each property. You don’t want to encode the encoder, though. By specifying the keys of token and debug Swift knows to only encode those two properties.
Now you can implement the method which will return the encoded data. Add the following inside TokenDetails:
func encoded() -> Data {
return try! encoder.encode(self)
}
While fully functional, there’s one more piece to implement. When you’re debugging your app, you’ll want to have an easy way to see what is being sent to the web service.
Add another extension:
extension TokenDetails: CustomStringConvertible {
var description: String {
return String(data: encoded(), encoding: .utf8) ?? "Invalid token"
}
}
CustomStringConvertible lets Swift know that when you pass this struct to print that it should call your custom implementation of the description property.
The last piece left is to add an initializer to TokenDetails:
init(token: Data) {
self.token = token.reduce("") { $0 + String(format: "%02x", $1) }
#if DEBUG
encoder.outputFormatting = .prettyPrinted
debug = true
print(String(describing: self))
#else
debug = false
#endif
}
The DEBUG macro will be true when you’re running your app from Xcode. Using the .prettyPrinted setting makes the JSON output more human friendly. As you add more items to the data that you send during registration, these “pretty” lines become a life saver when debugging.
You might, for example, want to store the users’ preferred language. By storing the language on your server, you’ll be able to periodically examine the list of languages to determine whether you should consider localizing your app to another language. Add a new property to TokenDetails:
let language: String
Then set the value in the initializer, just after assigning the token:
language = Locale.preferredLanguages[0]
Finally, add language to the enum:
case token, debug, language
Sending the Tokens
Now that you have a way to generate the details which will be sent, replace the application(_:didRegisterForRemoteNotificationsWithDeviceToken:) method body in AppDelegate.swift with the following code:
Testing
Note: For this to work, you need to make sure an instance of your Vapor server is running and configured to run on your IP address, as well as make sure your database is running. You also need to set up the sendPushes.php script to use your APNs token. This is all described in Chapter 6, “Server-Side Pushes”.
Refactor for Reuse
You can probably already see how the push notification code will be almost exactly the same in every project you create. Do a little cleanup by moving this common code to a new file called PushNotifications. Add the following code to the file:
Key Points
- Once you have your database established, you need to tell your app how to connect to it. Vapor will allow you to run a server written with Swift.
- Take the time to add some additional lines at the end of notification registration to display the body of the JSON request in a “pretty,” easy-to-read format, which can help in the future with debugging.
Where to Go From Here?
And there you have it! You’ve successfully built an API that saves device tokens and an app that consumes that API. This is the basic skeleton you will build upon when using push notifications. In Chapter 8, “Handling Common Scenarios,” you will start handling common push notification scenarios, such as displaying a notification while the app is in the foreground… so keep reading!