A Summary of the WWDC25 Group Lab

Hi everyone,I have an existing watch OS1 app on the store and I'm trying to figure out the best path forward. My OS1 app uses deprecated architecture, such as MMWormhole (shared group container) and the openParentApplication:reply: method of the WKInterfaceController class. When adding the new watch OS 2 app, is it better to keep deprecated OS1 app (no more updates) or remove OS1 app?I know you can maintain OS1 & OS2 side by side, per the Transition Guide:Do you need to support earlier versions of Apple Watch?You can deliver Watch apps for both watchOS 1 and watchOS 2 in the same iOS app bundle, but doing so means maintaining separate targets and executables for each. Because it runs on Apple Watch, a Watch app for watchOS 2 must be completely recompiled into a separate executable. And because of the architectural differences between the platforms, sharing code may be more effort and add more complexity than having two separate apps.Pros of keeping OS1 appMore customer base reach (but Apple custo

This might be a far fetch, but I hope someone out there has any clues.BackgroundI have an OS X app that uses AVAudioEngine to play a group of files concurrently. This works perfectly fine (most of the time 😉) on my shiny new Macbook Pro with a flash drive.In order to test how my app behaves on older/smaller/slower machines I thought I'd use Parallels to create a virtual machine with a little RAM and see how my app behaves there.So, I created a virtual machine, made sure that sound is working on the virtual machine (I can hear sound played on the virtual machine) and installed Xcode on the virtual machine to be able to see what was actually going on.And then the problems beganProblemWhen I start my app I do some initialization of the AVAudioEngine (attach nodes). When I call this line on my virtual machine:mainMixer = audioEngine.mainMixerNodea lot of errors are logged to my console:2015-08-05 10:55:31.562 app_name[357:2898] 10:55:31.562 ERROR: DefaultDeviceAggregate.cpp:361: CreateDictionaryForDevic

I have been building my Mac app against OS X 10.10. With OS X 10.11 around the corner I decided to try compiling and running my app with it to see how it performed. Immediately I noticed that many of my view animations are broken. Those animations are performed by the following steps:1. Set the starting frame for several layer backed NSView objects.2. Begin an animation context with [NSAnimationContext beginGrouping];3. Set the ending frame position for the same NSView objects in #1 above.4. Set an animation timing curve on the NSAnimationContext.5. Set an animation duration on the NSAnimationContext.6. Set a completion handler on the NSAnimationContext that performs post-animation cleanup and removes offscreen views from the view hierarchy.7. Ending the NSAnimationContext grouping and thus beginning the animation.The animations worked perfectly (albeit slower) under OS X 10.10 but under OS X 10.11 there are two problems right off the bat:1. Views seem to animate from the wrong starting position. A v

I'm using NSUserDefaults to save some information so we can share between Apple Watch And iPhone. I've found that sometimes I am saving different properties at the same time which leads to issues. For example:1. Extension is saving one object2. While this is happening, a notification is passed to the iOS app that causes it to save a separate property.This is pretty much happening at the same time and I'm seeing that the property modified by the extension is not getting correctly persisted in the NSUserDefaults database. Is there anything I can do to protect against this scenario?

HiI was working on an app with iOS 8 and WatchOS 1 that shared a Core Data file via App Groups with its corresponding iOS app and it was working nicely and almost ready to submit, the concept I had was working great.After looking at the initial videos on WatchOS 2 it is looking like using Core Data could now become an absolute nightmare!there doesn't seem to be much anywhere giving best practices on how you would have a core data store on the iPhone and the Watch and keep them in sync.I know there is the new Watch Connectiveity framework for transferring files but I don't really see how that helps regarding Core Data setups?I would have expected Apple to at least give some pointers on how this sort of thing could be achieved? am I missing a link somewhere?My app requires data to be shared between the iOS app and the Watch app with new Core Data records to be added from either the iOS app or the watch app but both devices having access to all the dataI was looking to get started on moving it up to iOS