watchkit

When using SpriteKit in watchOS 3, how do you handle the touch events? I am porting the SpriteKit games from iOS and the codes below won't work. Or you have to control the WKInterfaceController somehow? override func touchesBegan(_ touches: Set<UITouch>, with event: UIEvent?) {} override func touchesMoved(_ touches: Set<UITouch>, with event: UIEvent?) {} override func touchesCancelled(_ touches: Set<UITouch>, with event: UIEvent?) {} override func touchesEnded(_ touches: Set<UITouch>, with event: UIEvent?) {} After a lot of frustration with the same issue, I wound up using gesture recognizers,

I want to hide the back button from my Apple Watch app from the status bar. I used the programmable segue to navigate. But I want to to hide/disable the back button. Is it possible? infinite-loop This is how you do it: WKInterfaceController.reloadRootControllersWithNames( ["myInterfaceController"], contexts: [] ) Where myInterfaceController is the identifier of the destination Interface Controller. Thanks to Harvant for the pointer. If you check the docs for WKInterfaceController , you'll see there's no API to accomplish what you're looking for: https://developer.apple.com/library/prerelease

i am new to Watchkit development and unable to find solution to share data between iPhone and iWatch, please help me i am looking to share data using groups. Aadil Keshwani We can pass the data between iPhone & iWatch using groups. Basically iWatch can not do any processing and we need to share the data. We can share data using the NSUserDefaults . But for that you need to enable Appp Groups from capabilities section in both your project target and your iwatch app target, as showed below Below is the sample code to achieve that. In your viewController or appDelegate file add following code

When I try to build and run a WatchKit extension on my real Apple Watch, I sometimes get the following error message: I've tried to build the parent application for the iPhone and then again for my WatchKit app but I still get the error message. Does anyone know what causes this error message and how to deal with it? This seems to happen when it takes a long time to install the WatchKit App on the actual watch and Xcode times out waiting for the process to start due to the long install time. It can take a long time for two reasons: It sometimes takes a while for the Watch to "notice" the App

I've set my notification sash color in storyboard and it works fine in the simulator, but it shows up as gray on my watch. Does anyone know if this is a known issue or do you need to do something at runtime on a real device to show the color properly? The sash color is set for the WKNotificationCategory in the storyboard, which has a name. (In your screenshot "myCategory"). Then, for the correct sash color to appear on the real device, the push notification needs to have the matching category name when you send it. UILocalNotification *notification = [[UILocalNotification alloc] init]; if

Basically, my app is laid out in the page format and I would like it to launch into the middle of the three pages. There is no way of setting a previous page segue, so I have been trying to do it in code. I have the main view set to the first view, and I have tried a variety of methods to segue to the middle view as soon as the app is launched. Here is the two ways I tried: if segueCheck == true { self.pushControllerWithName("budget", context: self) self.presentControllerWithName("budget", context: self) segueCheck = false } The first presents the view, but as a completely separate view, and

I want to create a watch app for an existing iOS app. But I am in a situation that i don't own a apple watch and my existing iOS app will run only on real devices not on simulator. Is it possible to run the app on the iphone device and test my watch app in the watch simulator? Dmytro Hutsuliak Pairing a real iPhone and a Watch simulator is not possible at least at the moment. I make this conclusion because of 3 reasons: A Watch simulator automatically pairs to an iPhone simulator during the installation process. It is not possible to unpair a Watch simulator from the interface at all.