A Summary of the WWDC25 Group Lab

I was wondering what the best way of setting up an App Group with a subset of my data for display on the watch.My App was originally written with Core Data. Kelly

Anyone else getting this error on install?

We read through all of the documentation, Xcode 7 header files, and tried to summarize everything we could figure out about watchOS 2. We hope this is a quick jumping off point for developers who just want a quick description and links directly into the Apple documentation. http://www.sneakycrab.com/blog/2015/6/8/watchos-20-tldrPlease give feedback, corrections and new discoveries, and we'll update the post with new information as we find it.

I need a guide for adding trial period option for iOS app auto-renewing subscription without using separate server.The thing is that different time period options inside one auto-renewing group of items have separate IDs, however there is no ID for trial period. How can I request it from out my app after user presses Trial period button.There are no descriptions on Developer Forums and on other websites, no examples as well, so I don't know how to implement this.P.S.: I use RMStore to cover transaction APIs.Here is how the code approximately looks:- (void)performRequestForProduct:(NSString *)productID completionBlock:(void(^)(BOOL success))func { NSSet *productIdentifiers = [NSSet setWithObjects:kInAppIDUltimate, kInAppIDPremium1Year, kInAppIDPremium1Month, kInAppDonationBundleID, nil]; [[UIApplication sharedApplication] setNetworkActivityIndicatorVisible:YES]; [[RMStore defaultStore] requestProducts:productIdentifiers success:^(NSArray *products, NSArray *invalidProducts) { if (invalidProducts.count

I have rebuilt my app using XCode 7 and am testing that it works on my watch running watchOS 1.0.1 before I upgrade the device to version 2.0. Everything seems fine so far except that my groups do not have their custom insets (all zero) but instead have insets of 2. If I change the insets to larger values then it seems to work as expected, but not for zeroes.This works fine in the simulator (which runs 2.0) but not on the watch when running 1.0.1. I notice that the new API offers the ability to set the insets at runtime (which is very useful - thanks for that) so I'm wondering if this is related to that?Sounds like I need to file a bug report but I thought I'd mention it here in case anyone else notices that things are positioned strangely when running an app built with XCode 7 on a watch running 1.0.1.

According to the docs and some tests I just ran, interface objects in watchOS 2.0 are still write-only. I'm wondering what the reasoning behind this is now the code excutes on the watch, and therefore there's no longer a round trip to the phone. WatchKit developers have traditionally had to keep track of UI state manually due to this restriction imposed by the old architecture, but now the architecture has changed it seems a little strange to keep those restrictions in place. Could someone from Apple please comment on this?Also, it also seems a little strange that new watch app projects in Xcode still have seperate groups and targets for the interface and the code. Is this likely to change in a future beta?

The WatchKit Programming Guide is out-of-date, as it still refers to the old architecture, talks about communitcating the iOS app via openParentApplication(_:reply:), and using App Groups to share data etc.Will this be updated soon to reflect all the changes in watchOS 2.0?

i keep getting this core storage operation is not allowed on a sparse logical volume group error when installing. I'm lost as there seems to be no support documents & very few people with the problem

Question: On Yosemite, there is an issue where FileVault 2 will report Encrypted Paused during the encryption process, then never resume. It won't decrypt, and the only fix seemed to be deleting the CoreStorage volume.Is there a fix for this besides deleting the CoreStorage volume? For example, how to unpause and either resume encryption or decrypt?Answer:The Encryption Paused issue was addressed in 10.10.3. The root cause was a problem with resizing the CoreStorage volume. When the CoreStorage volume was unable to grow, the encryption was paused and could not resume until the resize issue was addressed.To fix this issue:1. Update your Mac to 10.10.3, or boot from an alternate drive which is running 10.10.3.2. Un-lock the encrypted drive if necessary3. Open Terminal4. Run the following command to get your Mac's disk identifier:diskutil list5. Once you have the disk identifier information, run the following command:sudo fsck_cs -y disk_identifier_goes_here6. fsck_cs should repair the CoreStorage volume and add

i cant figure out how to add a member to my group. please help