A Summary of the WWDC25 Group Lab

I've got the beta installed on my iPad Mini 2. I just happened to look at the message responses to a group message that I sent which originated from my iPhone 6 Plus (on iOS 8.3) which was sent to a mix of iMessage and regular SMS accounts, and while my original group message was contained in a group message thread, all the responses to it came back in individual threads. I verified that on my iPhone they are all coming back as part of the group message thread. Only seems to be an issue on the iPad and on the iPad with iOS 9 (previous group messaging on iOS 8.3 and below worked as expected).I also checked in Settings -> Messages to see if the Group Messaging option was enabled, and it isn't there anymore. (For that matter, neither is MMS Messaging.) Can anyone else verify that Group Messaging is or isn't working for them as expected?

Greetings,I have an iOS 8 Swift-based app using a UISplitViewController as its root view controller. My project's deployment setting is iOS 8.0 and I had to use launch images (and not a launch storyboard) because launch storyboards did not support containers such as UINavigationController, UISplitViewController and UITabBarController (this is quoted from a DTS response I got).In comes iOS 9 with its iPad multitasking feature, which requires using launch storyboards. Things seem to work (on iOS 9) if I specify my main storyboard as a launch storyboard but iOS 8 displays a black screen during launch. Strangely, if I check the Use as launch screen checkbox for the main storyboard, the compiler spits out an error (Launch screens may not have connections). Using a XIB file (with a UISplitViewController within) as a launch file seems to kind of work on both iOS 8 and iOS 9 but I can't seem to be able to modify the UISplitViewController in IB.This is quite puzzling as there is no way to have the system use launch im

Hi,I am just starting to make an apple watch app/extension for an app that I already have on the iPhone. On the iPhone the app has a core data store that it uses to store data. Looking at Apple's documentation it seems that the right way to access this core data store on the watch would be to setup the data store in a shared app group container.To do this I would also need to perform the following steps :1. Migrate the existing data store from the current location into the shared container on app startup (at least the first time)2. Take care of cases where the core data store is encrypted (we encrypt the sqlite DB underneath) and also figure out if that will conflict with the migration in step 1.The steps above are possible to do although they are not trivial.I was wondering what issues would there be if I was to avoid this step altogether (using the shared container) and simply called openParentApplication:reply: everytime my watch app needed data ? My gut instinct tells me that this method would be

Hello all,I'm working on an app that uses animated images in WKInterfaceGroup backgrounds. I have this section of code to set the images:[group setBackgroundImageNamed:@Test-]; [group startAnimatingWithImagesInRange:NSMakeRange(0, 14) duration:15*(1.0/30.0) repeatCount:1]; [shapeGroup setBackgroundImageNamed:@Test2-]; [shapeGroup startAnimatingWithImagesInRange:NSMakeRange(0, 14) duration:15*(1.0/30.0) repeatCount:1];There are 50 of these groups on screen, and I have coded it such that all of them MUST run through the code I posted in order to change their image. Nothing changes the alpha values of the groups. I have ensured that nothing is asking the groups to update to different images at the same time.The behavior I get is extremely inconsistent. Sometimes, group will run its animation. Sometimes, shapeGroup will run its animation. Sometimes both run, and sometimes neither run. There is no consistency either. A group that might have just succes

I have a watchOS 1 app with a large user deployment that makes extensive use of App Groups in the WatchKit extension. Will the app continue to run as before in some kind of legacy mode even when a device is updated to watchOS 2? Or is it imperative to migrate the app to the new model to keep it operational?

I am using a LIst picker with multiple PickerItems with a title. Currently the picker is nested in a group with a background image. However, the picker seems to have a solid black background under the text?Am I doing wrong/missing something to make it transparent? Or is this by design?

I'm trying to send a text data from watchOS 2 to iPhone but found out the hard way that I can no longer use openParentApplication on iOS9. So my next recommended option is to save text into a file and send it via shared groups, which from the watchOS 2 transitioning guide is no longer possible:You cannot rely on a shared group container to exchange files with your iOS app. Fetching files involves transferring them wirelessly to Apple Watch.WatchOS2 transition doc says there are mechanisms to do transfer of a file over network but no specifics or guidance.While Apple Watch provides mechanisms to facilitate those transfers, you must update your data-handling code to support those mechanisms.What are the mechanisms?I read through the WKInterfaceController doc and header file and didn't see an API to do network file transfer.

This is a follow up to the thread, Troubleshooting the launch of local user XPC Launch Agent, in the original (and now archived) Dev Forums.Based on further tests, I assume there must be some configuration that I'm not setting up correctly, as opposed to the code.I started from scratch again with a fresh Xcode Project. This time, I based the code mostly on the example code posted by Apple Engineer eskimo1 in this thread (which uses an privileged Launch Daemon) with a modification or two based on the code posted by Apple Engineer dsorresso in this thread. As I assume that their code can be expected to work (i.e.- to help rule out a coding error on my part). Except that I modified the code so that it works with/as an XPC Service Launch Agent without the privileged aspect and which resides inside of the user's home directory.The following was all done on OS X 10.10.3 (14D136) Yosemite and built with Xcode 6.3.2 (6D2105).* I first started off both the command line interface program and the XPC Service Launch Agen

Hey all,Setup:Xcode 6.3.2iOS/WatchKit SDK 8.3What Works:App groups are configured and tested to be working.Local development builds with development provisioning profiles work. I can build & debug to my Apple Watch hardware.Simulator also works (not that this matters).Now, enter ad hoc distributions via Crashlytic using our CI (Jenkins) environment. The application is distributed fine, and installs on device fine.But....Issue: Launching the application once installed on the Watch (via Crashlytics) results in a spinner that hangs forvever.Eventually (after about a minute) the app crashes.I've stripped the application down to a single controller with a button (no networking or heavy async stuff going on).To re-iterate - my local development builds to device work perfectly fine.Any ideas!? Is there a way to get the logs for what is going on with the watch?

suddenly after adding a group to the App Groups section for my Watch extension and iPhone app, I can no longer put any app on my device, All I get is the folowing error:The application does not contain a valid application-identifier entitlementhas anyone encountered this and solved it?(System is as folows: 10.11 + Xcode7 + iOS 9 + watch2) == full beta os nightmare.

I originally posted this problem in the old devforums, and now have a reduced test case.I still don't understand what's fundamentally the issue here, but basically the new compiler is somehow allowing a block to get added to a GCD queue twice in some situations. In the following code, the 10 worker blocks each do their thing and the parent block waits until they're all done. This used to work really well (through Xcode 5.1.1), but now, occationally, one of the worker threads will get added to the queue *twice*.Jeffreyint main(int argc, const char * argv[]) { @autoreleasepool { dispatch_group_t group = dispatch_group_create(); dispatch_queue_t queue = dispatch_get_global_queue(DISPATCH_QUEUE_PRIORITY_HIGH, 0); NSUInteger totalWorkers = 10; NSMutableArray *workers = [[NSMutableArray alloc] init]; for (NSUInteger iWorker=0; iWorker<totalWorkers; iWorker++) { __block int numThreads = 0; workerType worker = ^{ numThreads++; if (numThreads>1) { NSLog(@Whoops! Called by two threads); } int y = 0; for

I can not get the CMD-R run function to update my watch display. I have made changes to my storyboard yet when I run the app again (and again), there is no change in the view. My changes to the view include resizing and changing the alignment of a group within a group. I've delete the app from my phone and had mixed results with running the app again. Sometimes the app won't appear on the watch face with the xcode display showing Waiting to attach. What techniques do I need to use to avoid any associated bugs or other issues with the two devices communications to get through the development process with less hassle?