iPhone App
- import WatchConnectivity and conform to WCSessionDelegate.
- use the static session delegate via
WCSession.default()
.- Send data to Watch app using:
WCSession.default().sendMessage(message, replyHandler:_ errorHandler:_)
- The message object should be a dictionary of type [String:Any]
- If you are looking for data to be returned from the Watch app, provide the logic in a closure defined in the replyHandler; otherwise, pass in nil.
- To respond to messages sent from the Watch app, you will use the WCSessionDelegate callback method
func session(_ session: WCSession, didReceiveMessage message: [String : Any], replyHandler: @escaping ([String : Any]) -> Swift.Void){...}
You need to import the WatchConnectivity framework into your view controller file in the iOS application. This gives you access to the class objects that are designed to communicate with the Watch companion application. You will need to import this on the Watch app side as well. The only real difference with the Watch app is that you will not have a view controller file, but an interface controller file.
import WatchConnectivity
Next, you will need to make sure that your application can support a session for WatchConnectivity. If it can, then you must set the view controller as its delegate and activate the default session. You will get an error here. You need to conform to WCSessionDelegate and implement a few methods before the IDE begins to calm down.
// MARK: - View Life Cycle Callbacks override func viewDidLoad() { super.viewDidLoad() automaticallyAdjustsScrollViewInsets = false if WCSession.isSupported() { WCSession.default().delegate = self WCSession.default().activate() } else { print("\nViewController: connectionManager is nil\n") } }
To conform to WCSessionDelegate, let's add an extension to the bottom of the view controller. Some people hate this approach. I have my way, but for tutorial purposes, I will follow the RayWenderlich approach. I am a huge fan of just getting code directly from COMMAND + CLICKING on the delegates and grabbing ALL OF THE METHODS out of the specification and begin to manipulate it and understand how things work. In this extension, I am providing you will all of the methods. They are already marked so that you will see when each of them fire in the console. If you feel frisky, delete some of the ones that are marked OPTIONAL to make your code file look spiffy.
extension ViewController : WCSessionDelegate { func session(_ session: WCSession, activationDidCompleteWith activationState: WCSessionActivationState, error: Error?) { print("0. ViewController: ", "activationDidCompleteWith activationState") } /** ------------------------- iOS App State For Watch ------------------------ */ func sessionDidBecomeInactive(_ session: WCSession) { print("1. ViewController: ", "sessionDidBecomeInactive") } func sessionDidDeactivate(_ session: WCSession) { print("2. ViewController: ", "sessionDidDeactivate") } func sessionWatchStateDidChange(_ session: WCSession) { print("3. ViewController: ", "sessionDidDeactivate") } /** ------------------------- Interactive Messaging ------------------------- */ func sessionReachabilityDidChange(_ session: WCSession) { print("4. ViewController: ", "sessionReachabilityDidChange") } func session(_ session: WCSession, didReceiveMessage message: [String : Any]) { print("5. ViewController: ", "didReceiveMessage") } func session(_ session: WCSession, didReceiveMessage message: [String : Any], replyHandler: @escaping ([String : Any]) -> Swift.Void) { print("6. ViewController: ", "didReceiveMessage") // This is where you handle any requests coming from your Watch App } func session(_ session: WCSession, didReceiveMessageData messageData: Data) { print("7. ViewController: ", "didReceiveMessageData") } func session(_ session: WCSession, didReceiveMessageData messageData: Data, replyHandler: @escaping (Data) -> Swift.Void) { print("8. ViewController: ", "didReceiveMessageData") } /** -------------------------- Background Transfers ------------------------- */ func session(_ session: WCSession, didReceiveApplicationContext applicationContext: [String : Any]) { print("9. ViewController: ", "didReceiveApplicationContext") } func session(_ session: WCSession, didFinish userInfoTransfer: WCSessionUserInfoTransfer, error: Error?) { print("10. ViewController: ", "didFinish userInfoTransfer") } func session(_ session: WCSession, didReceiveUserInfo userInfo: [String : Any] = [:]) { print("11. ViewController: ", "didReceiveUserInfo") } func session(_ session: WCSession, didFinish fileTransfer: WCSessionFileTransfer, error: Error?) { print("12. ViewController: ", "didFinish fileTransfer") } func session(_ session: WCSession, didReceive file: WCSessionFile) { print("13. ViewController: ", "didReceive file") } }
To send data to your Watch App, once the Watch App has requested it, you will handle this in the method...
func session(_ session: WCSession, didReceiveMessage message: [String : Any], replyHandler: @escaping ([String : Any]) -> Swift.Void) { print("6. ViewController: ", "didReceiveMessage") // build out your response message using a Dictionary let returnMessage: [String : Any] = [ "key1" : value1, "key2" : value2, "key3" : value3 ] // return your data in this manner replyHandler(returnMessage) // WARNING // You must call the replyHandler before the method ends, otherwise, your app will crash. }
This is only one half of the transaction! You must configure your Watch app to connect to the iPhone app and handle any returned messages!