watch-os-2 | 易学教程

Where and When to get data for Watch Complication

阅读更多关于 Where and When to get data for Watch Complication

After working with complications for a few days, I feel confident saying the following about the update process for updates that happen at a prescribed interval: The system calls requestedUpdateDidBegin() This is where you can determine if your data has changed. If it hasn't, your app doesn't have to do anything. If your data has changed, you need to call either: reloadTimelineForComplication if all your data needs to be reset. extendTimelineForComplication if you only need to add new items to the end of the complication timeline. Note: the system may actually call

Xcode 7 supporting watch OS1 and OS2

阅读更多关于 Xcode 7 supporting watch OS1 and OS2

I have been fiddling with Xcode 7 for sometime now, I get to know that it supports only Swift 2 and there is no way to support Swift 1.0 or 1.2 in Xcode 7. This is fine. Now coming to WatchOS, can I have two targets one for WatchOS1 and one for WatchOS2 separately in Xcode 7 so that I can support for both?? I was looking into the deployment target setting in the build settings of both the watch target and the iOS app target but I could see only WatchOS2 in the list so Can I support two targets one for WatchOS1 & WatchOS2 respectively in Xcode 7? If so should I install WatchOS1 SDK at some

Using WCSession with more than one ViewController

阅读更多关于 Using WCSession with more than one ViewController

问题 I found many questions and many answers but no final example for the request: Can anyone give a final example in Objective C what is best practice to use WCSession with an IOS app and a Watch app (WatchOS2) with more than one ViewController . What I noticed so far are the following facts: 1.) Activate the WCSession in the parent (IOS) app at the AppDelegate: - (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions { //Any other code you

How big can the payload be when sending data via WatchConnectivity?

阅读更多关于 How big can the payload be when sending data via WatchConnectivity?

问题 When sending data using the WatchConnectivity framework, either from the phone to the watch or vice-versa, how big can the payload be before the framework gives me the WCErrorCodePayloadTooLarge error? I couldn't find the answer on Apple's documentation, and there doesn't seem to be much information on this on the internet at this time (in fact, googling WCErrorCodePayloadTooLarge gives me just 4 results). Has anyone tested to try to find the answer to this? If this question doesn't get an

Send messages between iOS and WatchOS with WatchConnectivity in watchOS2

阅读更多关于 Send messages between iOS and WatchOS with WatchConnectivity in watchOS2

I watched the WWDC2015 and saw that you can develop native apps on the watch now. This opened up a lot of capabilities and I am wondering how I could send data between my iOS app and my AppleWatch app. I saw that there is a new framework called WatchConnectivity. How can I use this and what are my options when sending data back and forth? Philip WatchConnectivity First the two classes that are supposed to communicate with each other (iOS and watchOS) need to conform the <WCSessionDelegate> and #import the WatchConnectivity framework Before you can send data you need to check if your device is

App installation failed due to application-identifier entitlement

阅读更多关于 App installation failed due to application-identifier entitlement

问题 I am unable to install a watchOS 2 WatchKit app due to an application-identifier entitlement. This happened after turning on App Groups in the Capabilities tab. Full error: App installation failed This application's application-identifier entitlement does not match that of the installed application. These values must match for an upgrade to be allowed. This is running the app in debug mode on a physical device. Running just the iOS app works fine. I have turned App Groups off again and

NSUserDefaults not working on Xcode beta with Watch OS2

阅读更多关于 NSUserDefaults not working on Xcode beta with Watch OS2

I just installed the latest beta of Xcode to try Swift 2 and the improvements made to the Apple Watch development section. I'm actually having an hard time figuring out WHY this basic NSUserDefaults method to share informations between iOS and Watch OS2 isn't working. I followed this step-by-step tutorial to check if I missed something in the process, like turning on the same group for both the phone application and the extension, but here's what I got: NOTHING . Here's what I wrote for the ViewController in the iPhone app: import UIKit class ViewController: UIViewController { @IBOutlet weak

Send messages between iOS and WatchOS with WatchConnectivity in watchOS2

阅读更多关于 Send messages between iOS and WatchOS with WatchConnectivity in watchOS2

问题 I watched the WWDC2015 and saw that you can develop native apps on the watch now. This opened up a lot of capabilities and I am wondering how I could send data between my iOS app and my AppleWatch app. I saw that there is a new framework called WatchConnectivity. How can I use this and what are my options when sending data back and forth? 回答1: WatchConnectivity First the two classes that are supposed to communicate with each other (iOS and watchOS) need to conform the <WCSessionDelegate> and

NSUserDefaults not working on Xcode beta with Watch OS2

阅读更多关于 NSUserDefaults not working on Xcode beta with Watch OS2

问题 I just installed the latest beta of Xcode to try Swift 2 and the improvements made to the Apple Watch development section. I\'m actually having an hard time figuring out WHY this basic NSUserDefaults method to share informations between iOS and Watch OS2 isn\'t working. I followed this step-by-step tutorial to check if I missed something in the process, like turning on the same group for both the phone application and the extension, but here\'s what I got: NOTHING . Here\'s what I wrote for