“A Summary of the WWDC25 Group Lab”

Has anyone else had a problem with iPad always resetting itself everytime one tries to go into a group with the latest iOS 9 Beta?

Below are two examples of what one might assume to be gaps / missing protocols in the current standard library (Swift 2, Xcode 7 beta 2). I'd like to get advice on how to handle the particular situation described here as well as similar situations in general (ie how to handle the prevalence and successive diminishing of supposed gaps during the rapid evolution of Swift and its standard library).Ok. Consider the primitive number types in the standard library (Double, Float, Float80, UInt, Int, UInt8, Int8, UInt16 ... Int64). They share some common characteristics, some of which are explicitly available for us to use through protocols such as IntegerArithmeticType, FloatingPointType, IntegerType etc, and others which are only there implicitly.Two examples of such only-implicitly common features / missing protocols:The fact that any primitive number type can be (explicitly) converted to (initialized with) any other primitive number type.All the integer types have bounds specified by their .max and .min propertie

I saw a post in another group about a developer making custom watch faces for OS2. Did I miss something? I thought we could only create complications, not watch faces.

AllI've seen this for a while now (old Yosemite betas and potentially before) where if you join a Jabber group chat room in iMessage that any message I post has 2 issues:1) The message appears at the bottom of the chat and out of sequence when others reply. i.e. I say Hello, someone else says Hello but their reply appears above mine instead of below even when they sent theirs later. Therefore iMessage is displaying them out of time sequence2) My messages are double or triple posted in the chat room. This only ever happens in group chats through Jabber and not when I am direct IM'ing someone even if still using Jabber as the medium.I raised a bug on this a while back and it was closed as a duplicate to another bug, one that is still open.Wondering if anyone else see's this behavior and has any suggestions as have not seen this behavior change in El Cap beta 1 or 2Thanks

I am adding a new feature to my existing app and I have to add app group to project in order to share data between extension and app. However, after I added app group to project file, my code can't no longer retrieve data from previous keychain on simulator. It looks like it create a brand new keychain for the app. If I turn off app group and my app can retrieve data again. Does iOS create a different keychain after add app group to project? It's even weird is that thishappens only on simulator. When I test it on real device, app can retrieve keychain data without issue. I have go through some documents and found no information about this. Is it a bug on simulator? Can anyone gives feedback?Following is my environment:1. Xcode 6.3.22. Simulator iPhone 6 (iOS 8.3 12F69)

I've added images to the Complication group in Assets.xcassets within my WatchKit Extension but I can't figure out how to load one of these images as a UIImage in code. Can anyone help me out with this?I just watched the Creating Complications with ClockKit WWDC video but the code sample just used UIImage(named: Background) and UIImage(named: Foreground)Thanks

Hi, I have an app group that worked fine between my watch and iPhone using Swift 1. Now, however, nothing is saving to my app group when I use the same code to save and synch the data (and thus nothing appears on my watch).I believe the relevant code is here://in the AppDelegate var sharedData = NSUserDefaults(suiteName: group.RxRemindMe)//in my VC NSKeyedArchiver.setClassName(RxRemindMe.Medication, forClass: Medication.self) NSKeyedUnarchiver.setClass(Medication.self, forClassName: RxRemindMe.Medication) appDelegate.sharedData!.setObject(savedAsData, forKey: TheMedicationsShared) appDelegate.sharedData!.synchronize()if I run the same .setObject command on a non-shared userDefault object, I see bytes saved (size changes to some positive bytes) and my phone app can access the data. However, when I execute line 4 above via the shared group object, the object remains nil in size and nothing has changed. I thus can't recall the data either on the phone or on the watch. Is this a bug in