DTiPhoneSimulatorErrorDomain Code 2

Also.... I found a very informative website that has a ton of examples specifically on how to work with dates within Swift.Here's a code snippet that he uses as an example, but does not compile for me, and I have no idea why I get the error: could not find member 'CalendarUnitDay'. Was this syntax changed with Swift 2.0?Every example I could find uses this syntax, but for me... no luck.// Playground - noun: a place where people can play import UIKit let userCalendar = NSCalendar.currentCalendar() // Let's create some dates to work with // ==================================== // It's 3:45:30 a.m., New Year's Day. Time to go home. let goHomeYoureDrunkTimeComponents = NSDateComponents() goHomeYoureDrunkTimeComponents.year = 2015 goHomeYoureDrunkTimeComponents.month = 1 goHomeYoureDrunkTimeComponents.day = 1 goHomeYoureDrunkTimeComponents.hour = 3 goHomeYoureDrunkTimeComponents.minute = 45 goHomeYoureDrunkTimeComponents.second = 30 let goHomeYoureDrunkTime = userCalendar.dateFromComponents(goHomeYoureDru

They renamed some enums / options to be more consistent.In Swift, it would now be NSCalendarUnit.Year (type NSCalendarUnit, case .Year). If you double command-click on NSCalendarUnit (or NSYearCalendarUnit) in Xcode in your playground, it will pull up the Swift version of the header.And as far as the example code goes, OptionSets are handled differently now in Swift 2.0 and use set syntax instead of bitwise operators to join and test them.See the Xcode 7 beta release notes or https://forums.developer.apple.com/thread/3623 for more info on that.

My Apple Watch also got battery drains from 100% to 55% in 6 hours last night ..........I can do nothing to downgrade only can wait till the beta 2 comes out

I expected an increase of iPhone battery usage, but not at this level. 100% at 6:00 PM, 61% at 8:00 PM. There has been no physical interaction, on my part, with the two devices (iPhone 6 and Apple Watch) during this period. This is terrible, even for a Beta release. iOS 9 is Alpha at best!I hope there is a point release in the very near future. I cannot build and compile that fast!

Same on my side,it is awsome that a beta version is as worse as this IOS9 Beta 1. With only less improvements the battery is empty in extremely shorten time. But battery is one of the important things at MOBILE phones. So I really do not know why Apple was doing this Beta 1 because it is much more a pre-Alpha. Same at OSX 10.11 with Mail. It crashes totally against Exchange accounts. Really worse. I think they are not ready and / or WWDC was too early. Hopefully we get an update during the next 2 weeks, otherwise I think battery is damadged.

If you did install iOS9 as an upgrade your data should be there on the phone. If your did wipe your phone during the install process just restore it with the backup data from the last backup before upgrading.But downgrading after installing iOS9 or watchOS 2 is not recommended. It can work on the phone but as some iOS upgrades also update the firmware for cellular connections you can have many problems after a downgrade. For watchOS 2 a downgrade is not possible.

I also have this same issue. From what i can remember (only 2 weeks ago) i had this also on the day i got my watch, it looks like there are some background processes running wich could cause this.I found some Threats on the web wich said u need to reset the Network settings on your iphone (did this) and setup your watch as a new one instead of putting back the backup. Most users report bettter battery at day 2. I will let u know how mine is reacting today!

from the Keynote…it works on:iPad AiriPad Air 2iPad mini 2iPad mini 3& 'SplitView' is just on iPad Air 2…

That is what I'll try at first. We'll see what the bridging brings with the new Xcode 7 and Swift 2. I never tried it with earlier versions but it didn't look to be very seamless.Thanks/Peter

Tried the Start Up Disk options right from the start, hence the thread topic name. Neigher of two backup ones work. Each ends up in the same 10.11 system.Running the disk command in terminal yielded: No CoreStorage logical volume groups found.Yosemite started out as a terrible release and so far 10.11 is similar.