A Summary of the WWDC25 Group Lab

Thanks for the feedback tweeling, There was one step which we performed on some but not all devices. Two devices in our lab had some data corruption relative to installer/uninstaller garbage that wasd persistent in the settings. These devices also appeared to exhibit persistent battery drain. In another thread someone had suggested doing another restore or update to iOS 9.0 Beta 1 without doing a backup restore would resolve certain issues, however it is possible that this additional step is what might be contributing to the generally positive impact we have seen in the lab. Again, it's not perfect and it will likely be improved in subsequent betas, but in the event that the next beta is delayed this might help get some people through another week with less stress. Good luck and thanks again for contributing to the discussion.

Hi kcft, Sorry I missed your question on Apple Watch. We have no evidence that there is any apparent need for this. We have two in the lab running Apple Watch OS 2 Beta and neither are exhibiting alarming battery drain. (Though we have noted the persistent bluetooth connection appears to drop and require a reboot of the iPhone in question from time to time.)

I mentioned that hidden doesn't disrupt the view hierarchy, but there is a particular reason why I'd rather remove the button than just hide it.My screen stacks about 5 buttons vertically to make a main menu. On 3.5 inch iPhones, only 3 buttons will fit on screen. The other two buttons are extras that will be moved into the toolbar on 3.5 inch (making the font size for the buttons teeny to make it fit does not look good). The content shouldn't scroll either. If size classing behavior was more detailed, I'd just be able to do this in IB, but the groupings don't provide enough control.Also, the app supports all orientations. On iPhone 5, a couple of the buttons will be hidden in landscape, and shown in portrait. I'd rather just remove the buttons in viewDidload on the small screen. On orientation change I don't want to have to do extra screen sniffing before showing buttons. Better to just get them out of there in viewDidLoad....so on 3.5 inch iPhones it'll just be sending messages to nil.I can't imagi

Most of the time, I wouldn't screen sniff. They don't give you any indication that you're on the 3.5 inch screen when you use size classes...even though it has a different aspect ratio than the other iPhones. For many layouts...that's fine...especially on something that scrolls like a table view. But if you want to truly take advantage of a screen size and not compromise the layout on the shorter screen by making font sizes too small, there's no other way. I'm starting to like how autolayout is working in Interface Builder. I wish they gave us more control.....a way for us to create are own size classes because there categories may not work for every layout. It would be nice if we could group are layouts exactly as we want to in Interface Builder.

Nothing special needed for command line environment. This is a simple test app that I have written to try it out. I am no expert at this, but it seems to work.main.swift:import MetalKit let N = 100 let bufferLength = N * sizeof(Float) let devices = MTLCopyAllDevices() //print(Possible devices: (devices)) let device = devices[0] print(Running compute application on device (device.name!)) print(Adding vectorA and vectorB into vectorC. Each vector is (N) floats) let commandQueue = device.newCommandQueue() let defaultLibrary = device.newDefaultLibrary() let commandBuffer = commandQueue.commandBuffer() let kernel = defaultLibrary!.newFunctionWithName(add_kernel) let computePipeLineDescriptor = MTLComputePipelineDescriptor() computePipeLineDescriptor.computeFunction = kernel let computePipelineState = try! device.newComputePipelineStateWithDescriptor(computePipeLineDescriptor) // Set up thread groups to be used in commandEncoder let thrdWidth = computePipelineState.threadExecutionWidth let thrdsPerGroup =

WatchKit in watchOS 2 interprets zero values different. The size APIs are now public properties and they can be animated.The specific solution to your problem depends on the content you have inside the 3rd group, but you could try using size-to-fit for your third group. If the content inside the 3rd group isn't enough to fill the space, another option is to embed a group inside and tell that embedded group to use relative sizing with a value of 1 (and size-to-fit in the outter third group).

IBOutletCollections aren't currently supported in WatchKit interfaces.The code you refer to from WWDC initialized the outerGroups array in code from 12 separate outlet connections to each one of the groups.

I was able to find a solution to the issue. I had to delete the user from both the internal and external tester lists, remove their account from Users & Groups in iTunes Connect, delete test flight from their phone, and then re-invite them via User & Groups. Once they signed up, I added them as an internal tester and sent them an invite. After they install Test Flight and load it, they get the error message that the invitation is invalid. At this point, you click on their apple ID in the button near the bottom of that screen. On the following screen, there should be at least one extra device listed near the bottom. Click edit, select all the devices in that list, and then select Remove in the top-left part of the screen. Then click done. At that point, the user will be able to install the app again.

So were you using a MKMapView in your extension running on the phone and taking snapshots of that when the GPS position changed and sending the images to the watch, where they were displayed in an image/button/group control?Do you need functionality that MKMapView offers but WKInterfaceMap doesn't, such as overlays? If not then it is much simpler to just use a WKInterfaceMap and just set the region you want to show as I explained before.If you need overlays or other functionality not available in WKInterfaceMap then you should be able to use MKMapView in the iPhone app (rather than the extension) and send the images using WatchConnectivity as you suggest. The WWDC video is probably a good place to start:https://developer.apple.com/videos/wwdc/2015/?id=713There is also a sample project that includes an example of how to use it:https://developer.apple.com/library/prerelease/watchos/samplecode/Lister/Introduction/Intro.htmlHope this helps.