watchkit

WCSession and Today Widget

大兔子大兔子 提交于 2019-12-03 10:13:28
I've an app with a today extension and a watch app. From the main app WCSession works fine and data is transferred to the watch and received correctly but when I try to send or receive data through the WCSession in the today widget the property paired and watchAppInstalled of the session are set to false so calling transferUserInfo: does nothing and session:didReceiveUserInfo: is never called. I know I can open the app using openURL and then send the new data but I want to do that without leaving Notification Center. Does anyone know a nice workaround for this problem? If the watch app is

HKWorkoutSession isn't keeping app at front of Apple Watch

人走茶凉 提交于 2019-12-03 10:05:02
问题 It has been stated that an app running a HKWorkoutSession will have special privileges over other watchOS 2 apps, so when a user looks at their Apple Watch, it will go to the view showing running a workout rather than the watch face. Currently, on both my device and simulator, this is not the case. If I start a HKWorkoutSession and then leave for 5 minutes and then interact with either the Apple Watch, or the Watch Simulator, it presents the watch face. If I then open my app, it appears to

Embedded Binary Validation Utility Error

一世执手 提交于 2019-12-03 08:58:45
问题 Since yesterday Xcode is doing stupid things while trying to run my WatchKit app on my iPhone. It gives me the error: Embedded Binary Validation utility Error Error: warning: Is a directory It's not very helpful and it seems like it's complaining about provisioning profiles for my Watchkit Extension target. I think I set it up correctly by following this answer. This is how I have set up my profiles. Three App IDs and six profiles (three for development and three for distribution). Main app:

Xcode Watchkit: None of the valid provisioning profiles allowed the specified entitlements: beta-reports-active, com.apple.security.application-groups [duplicate]

不想你离开。 提交于 2019-12-03 08:55:58
问题 This question already has answers here : Watchkit Extension - No matching provisioning profiles found (7 answers) Closed 4 years ago . Yes, I know that there are a lot of these questions floating around and I know that the answer to all of them was: Log into Developer Member Center Go to Identifiers, profiles, etc Click Edit and then Generate on your provisioning profile That didn't work for me! I developed my application in Xcode 6.4 Beta 1 and with WatchKit. I tried submitting it but after

How can you download WatchKit? [closed]

风流意气都作罢 提交于 2019-12-03 08:46:01
问题 Closed. This question is off-topic. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 5 years ago . Does anyone know when WatchKit will be available for download for iOS developers? Will Xcode 6 include an emulator to allow for a Apple Watch app to be created/tested on a Mac? 回答1: Update: 11/18/14 - WatchKit is officially available on apple's website. You must download the latest version of Xcode from the

Invalid Apple Watch icon file names must match pattern “*<dimension>@<scale>x.png”

寵の児 提交于 2019-12-03 08:34:01
问题 I'm trying to submit an update to my App to include Apple Watch capabilities, however whenever I validate the build I get the errors detailed in the screenshot below. Looking at the bottom error my file name seems to be matching the pattern so I don't see what the issue is. If I can get the pattern right for 1 icon then I can apply the same logic across the board, however I'm not having much luck with it. Has anyone else had this issue? 回答1: I got the same issue when I tried to submit. My

Cocoa pods and Watchkit Extesion

大兔子大兔子 提交于 2019-12-03 08:02:44
I try to build a WatchKit Extension for my app... I Updated the pods file to look like this: platform:ios, '8.0' use_frameworks! source 'https://github.com/CocoaPods/Specs.git' link_with 'my-team-ios', 'My Team WatchKit Extension' def shared_pods pod 'DOSingleton' pod 'JSONModel' pod 'MagicalRecord' end target :'My App' do shared_pods pod 'Facebook-iOS-SDK', '~> 3.23.1' pod 'Reveal-iOS-SDK', :configurations => ['Debug'] ... some more pods here... end target :'My Team WatchKit Extension' do shared_pods end How I install the pods and don't get an error... But, when I build the App, I get this

Inconsistent behavior of openParentApplication in my WatchKit App

╄→гoц情女王★ 提交于 2019-12-03 06:45:43
I'm developing an Apple Watch application that uses the openParentApplication:reply: method to communicate with its parent app. The parent app communicates with a web service and sends back the data it gets to the watch extension by means of calling the reply method with a NSDictionary containing the data. The app works perfectly when the parent app is open in the foreground or background. But if I open the parent app and then terminate it using the task switcher, the first time the watch extension makes a call to openParentApplication:replyInfo: , it gets the following error and the parameter

How to share data using Watch Connectivity when working with Core Data

馋奶兔 提交于 2019-12-03 06:02:34
In my iOS application I use Core Data to store data and a fetch request to create an array of NSManagedObject s to display in a UITableView . On the Watch OS I check if WCSession is supported and active a session, then send the iOS application a message from the watchOS extension. When the iOS application receives the message from the watchOS it should send the array of Objects to the watchOS extension to display the data in the WKInterfaceTable , but I am unsure how to do this. Ultimately what I am trying to achieve is; How to share the array of Objects with the watchOS extension? If the user

iOS7 and Apple Watch

大憨熊 提交于 2019-12-03 05:54:44
问题 I have a app with the minimum iOS target iOS7. I am considering in add some extra features with the apple watch. Theres is any option to maintain the iOS7 as the minimum target and still add support for apple watch if the app is running on a iOS 8? Something like the extensions/widgets of the iOS8. Thanks in advance 回答1: You can set your deployment target to iOS7.x and make sure you build against iOS8.2 SDK. You will need to set the frameworks as optional (weak linking) in your build settings