DTiPhoneSimulatorErrorDomain Code 2

That's not the way you would usually activate whole module optimization (neither in Xcode6 or Xcode 7).In Xcode 7 it's in the Build Settings section: Swift Compiler - Code Generation -> Optimization Level.In Xcode 6 there was a check box in the Swift Compiler section, if i remember correctly.From the command line it's eg swiftc -O -whole-module-optimization main.swift

Same for me... but I blew it out anyway... had some issues with Disk Utility but im good now. Runnign Parallels with a regualr VM of Windows 10 with no issues.Office 2016 was working fine but now with the update yesterday Outlook has some visual issues/bugs. Reflector 2 - Not workingLync for Mac - Not workingEvernote - WorkingDropbox/OneDrive/GoogleDrive - Working

I'm still trying to catch up here. jgobble, how does your current app work in the 2.0 simulator? As in, you've got lat/long being run on the watch (ie background in the phone) and displayed on the watch. What happens when watch 2.0 asks for a lat/long position? does it just fail now because the watch has no GPS, or is it smart enough to get it from the phone? In other words, will current code asking for lat/long still work, or does it have to be redone with watchConnectivity to work now? As you say, a lot of stuff to have to redo so soon after the 1.0 release! thanks for the help here.

Does anyone have a solution to this?I wanted to test out iOS 9 and watchOS 2. Neither of them worked well enough for me to really develop on. I mostly did this because I wanted to test out the new custom complications feature available to developers in watchOS 2, and as far as I know, this is not possible in the watchOS simulator still.I downgraded my iPhone 5S and iPad Air to iOS 8.3 no problem. I cannot downgrade my Apple Watch 42mm Black Sport to WatchKit 1.0.1 (I think that was the version of it, it was the first official update to the Apple Watch).Right now, it seems that until I put iOS 9 back on my iPhone 5S, I cannot use my Apple Watch, because I cannot pair with it using iOS 8.3. I have looked everywhere and no one seems to have a solution to this.Can I go to the Apple Store and get my Apple Watch reset with that hidden debug port underneath the removeable strap?I need to get my Apple Watch functioning again ASAP.P.S. watchOS 2 beta was especially horrible for anything netw

Come on, there's a difference between alpha software and beta software. This watchOS 2 beta is really an alpha. Allow people to downgrade!

It looks like you meant to post a code fragment, but it's not there.

If you hover over the space without moving the cursor for about 2 seconds, does the close 'x' button appear like in OS X Yosemite?

The question is how/why/when the superclass expects its storyTableView property to be set. What you're doing might be the right approach, but there's certainly a code smell about it, which can't be resolved without knowing more about the superclass.It's possible that the correct answer is to mark the superclass property as @IBOutlet, which should allow you to connect the property in the storyboard.Note that with Swift 2, the right approach might be to turn the superclass into a protocol with an extension that provides default behavior.

Yep, the battery life is terrible and the OS is laggy and buggy. Typical 1st beta. Hopefully #2 comes out quickly.