A Summary of the WWDC25 Group Lab

Wait, so they can't share data anymore? I thought that was the point of app groups! And just to check I saved and then opened my shared app group on my phone app (not involving the watch at all)--still doesn't work. The issue is that when I use the .setObject command, nothing happens. It used to save my data into that object so I could retrieve it, but now nothing at all happens. Very frustrating since it took a working app and wrecked it (not the first or last time transferring to watchOS 2 and Swift too!).

Ah, nuts, got pulled away from my iOS 9 work and missed your response. Still trying to come up with the best way to track the new dev forums.I'm working on a social sharing app that lets you have relationships with other people (shocking, I know) and I wanted to make various relationships searchable - enter somebody's name into Spotlight and have that result take you directly to the detail view in the app that displays your relationship with that person. If you choose to sever the relationship with that person, I want to remove them from the search index. My original implementation was creating the NSUA when the user navigated to a distinct relationship view.My theory was you'd be more interested in seeing you old college friend Jane, who you interract with regularly, than Jane, your second cousin twice removed who you don't really like but can't de-friend because, well, family. I realize I could be attempting to recreate the smarts that you folks have already built into Spotlight.I thought I saw Address Book

I'm working on a social sharing app that lets you have relationships with other people (shocking, I know) and I wanted to make various relationships searchable - enter somebody's name into Spotlight and have that result take you directly to the detail view in the app that displays your relationship with that person. If you choose to sever the relationship with that person, I want to remove them from the search index. My original implementation was creating the NSUA when the user navigated to a distinct relationship view.I think what you should do is use CoreSpotlight to index the relationship/person information, and then use NSUA to layer on top of that the additional information about how the user navigates those relationships. A couple points to consider:Using CoreSpotlight will allow you to index all the relationships a user has established regardless of whether they have viewed them in your app. If you didn't do this, users wouldn't be able to search for somebody without first having viewed them in the ap

This is very useful summary, thanks! Would be interested in reading more about setting up peer-to-peer WiFi as my application requires higher bandwidth than what's recommended for Bluetooth LE. Are you aware of good resources on peer-to-peer WiFi development to get started with?Many thanks,Stefan

Right now I'm looking into the App Group entitlement to give us shared NSUserDefaults. It sounds like App Group (unlike iCloud and keychain-access-group entitlements) is shared on the device, but not over the iCloud account. I'm thinking if the shared deviceid NSUserDefault key doesn't exist, we'll save the IdentifierForVendor ID and then use that for all our apps once it saved.I'm curious if anyone else has tried that workaround.

NSUserDefault, using shared groups are no longer supported with iOS 9 and watchOS 2 since the watch extension is now running on the watch itself instead of on iOS. You'll need to take a look at the WatchConnectivity Framework if you want communication between watchOS 2 and iOS 9.Here is the framework reference: https://developer.apple.com/library/prerelease/ios/documentation/WatchConnectivity/Reference/WatchConnectivity_framework/index.htmlAlso take a look a the lister sample code here:https://developer.apple.com/library/prerelease/ios/samplecode/Lister/Introduction/Intro.html#//apple_ref/doc/uid/TP40014701

The UITextInputAssistantItem contains 2 arrays, leadingBarButtonGroups and trailingBarButtonGroups. You can add instances of another new class, UIBarButtonItemGroup, to these arrays to add or replace items on the short cuts bar. UIBarButtonItemGroup has 2 major properties, barButtonItems and representativeItem, that you can in turn fill out to specify what is on the bar. Finally to hide the bar (assuming that predictive text is also off) you can set the leading & trailing groups to an empty array.Example:NSArray barButtonItems = @[ /* Create UIBarButtonItems and place them here */ ]; UIBarButtonItem representativeItem = // This is optional, if present when there isn't enough room on the bar, the group will be replaced with this item UIBarButtonItemGroup *group = [[UIBarButtonItemGroup alloc] initWithBarButtonItems:barButtonItems representativeItem:representativeItem] textView.inputAssistantItem.leadingBarButtonGroups = @[ group ]; // replace the items on the bar. Altern

thanks, very interesting. Might be my case a little different? is seems there is onlune one volume in rMBP. Ran the command line to found the following:CoreStorage logical volume groups (1 found)Any other possibility?thanks

+1 This fault happens ~80% of the time.Process: SourceKitService [88642] Path: /Xcode//Xcode-beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/sourcekitd.framework/Versions/A/XPCServices/SourceKitService.xpc/Contents/MacOS/SourceKitService Identifier: SourceKitService Version: 1.0 (700.0.42.3) Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: Xcode [88591] User ID: 502 Date/Time: 2015-07-01 06:56:16.746 +0200 OS Version: Mac OS X 10.10.3 (14D136) Report Version: 11 Anonymous UUID: 85DF8F01-C036-BABB-C01A-14EB25054544 Sleep/Wake UUID: CB5F0B17-CF88-4E3D-B766-71B43FBA1AE9 Time Awake Since Boot: 130000 seconds Crashed Thread: 13 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000080 VM Regions Near 0x80: --> __TEXT 000000010022e000-000000010239e000 [ 33.4M] r-x/rwx SM=COW /Xcode//Xcode-beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/sourcekitd.framework/Versions/A/XPCServices/SourceKitService.xpc/Contents

Thank you junkpile for your reply. I'll look into this grouping of VCs.The large number of VCs is unavoidable for my application. I started my project using the page based application template that Xcode offers. It is a comic book, and on some of the pages there is animation and sound. The graphics and sound relies on NSTimer as a trigger. But because Apple's template recycles the view controller on the fly when the user turns the page, programmatically you stay on the same View Controller ( which is very clever on Apple's part ) I am not able to stop the sound if the user decides to turn the page before the animation finishes. This creates a very unprofessional looking (and sounding) app.I got around this using 2 methods - ignoreInteraction & respondToInteractions which prevented the user from turning the page until the animation was finished. But I could see how this would annoy a user if they wanted to turn the pages back or forward for some reason. They would have to stop and wait for the ani

Things have progressed. Here is Apple's technical note.I have found the SSL Labs server test site useful in identifying where the incompatibilities lie. It tells you more than everything about the server in question.

DownloadEarthquakesOperation is a group operation because of self.When creating the NSURLSessionTask, I needed to capture self inside the completion block in order to handle the results. However, if this were a URLSessionTaskOperation, I wouldn't be able to reference self before the call to super.init(task:), but I would have to do it before calling super because super requires the NSURLSessionTask. So there's this stalemate where I have to configure the task before calling super, but I can't configure the task before calling super because I need self.The quickest way to work around this was to not subclass URLSessionTaskOperation, but instead put it inside a group, where I have explicit control over the timing of the creation of the operation.