DTiPhoneSimulatorErrorDomain Code 2

It turns out that although the WatchKit app was upgraded by Xcode to WatchOS 2-type, it didn't really work. I had to make a new target and drag files over and change which bundle they were part of. After that, it didn't work due to an inclusion of a framework that didn't allow for Core Location methods but that's another issue.Hope that helps.

So, assuming that it is not possible (without resorting to creating a custom Set type etc), one wonders if there is any particular reason for why Hashable should/must imply Equatable, or rather why the == of Equatable should/must have Self parameters.Btw, here's another (boilerplaty) workaround, using an enum:protocol SomeProtocol : CustomStringConvertible { } struct Foo : SomeProtocol { var description: String { return Foo(id) } let id: Int init(_ id: Int) { self.id = id } } struct Bar : SomeProtocol { var description: String { return Bar(id) } let id: Int init(_ id: Int) { self.id = id } } struct Baz : SomeProtocol { var description: String { return Baz(id) } let id: Int init(_ id: Int) { self.id = id } } enum ConformingToSomeProtocol : Hashable, CustomStringConvertible { var description: String { switch self { case .FooValue(let v): return v.description case .BarValue(let v): return v.description case .BazValue(let v): return v.description } // Any shorter way to do this? } case FooValue(Foo) case BarValue

Managed Distribution Does Managed Distribution Device Assignment support in-app purchases? iAP not supported with MDM device assignment in iOS 9. Apple is aware of the desire for this feature and are discussion the best approach.Apple Configurator 2 An admin can export a company profile and import to as many machines as needed. Single sToken - cannot use institutiontal sToken with a seperatel location sToken for application deployment. The ideal method for Managed Distribution Device Assignemnt will be utilizing AC 2 as a mechanism to auto-enroll into an MDM. App thinning is not supported with Apple Configurator.iOS 9 How will iOS handle storage constraints for iOS updates? Currently, the iOS update command will fail the device will not be able to silently update. Similarly to non-silent updates, 50% battery is required for installation. A future update to iOS (not iOS 9) may do the following: Delete tagged App thinning Application data Delete Managed Applications -> Update iOS -> Push

OMG, it is user error! I expected that using the mouse to drag thru the document would work to scroll the image. Instead, you just move your finger on the top of the Magic Mouse or use two fingers on the trackpad.Seems to work ok now.Never mind...

Yes! This has been happening to me as well. This workaround has worked reliably for me... 1. Stop any updates that are currently trying. 2. Turn off Wifi. 3. Find the smallest app that needs updating (to conserve OTA data) and tap Update. 4. Once it starts downloading, kick on Wifi. 5. Hit Update All. The apps should start downloading and installing. Tried to stick a proxy between the phone and my computer to sniff the packets, but that failed... Not sure why this is happening. Same issue on my home and work wifi. A reboot also fixes it... But that takes forever. 🙂-T

Did you erase and install? Also, try not to install Java. Keep things simple and lean as much as you can to narrow it down.I have been using Safari 8.1 without incident so far on 2 MBPs. One tab (Twitter) crshed one time.

Benj4, might you be able to use an NSTimer event to call requestLocation? That doesn't help with distance filtering, but you could set it to every second or two and at least you'd get an update that way.

Based on the videos and some of the new Swift API's are explicitly available on iOS 7 (like #available and guard statements), I'd say Swift 2 will run on iOS 7 and later. The next question is going to be when can we start submitting Swift 2 Apps to the App store. I'm not going to make the change to 2.0 until I know I'll still be able to submit our Apps (or at least have a reasonable accurate timeframe of when I will). And I'll say I really want to make the change to 2.0 ASAP.AndrewEdit: The Swift session currently streaming live is making many references to running on iOS 7 and later.

Thanks for the reply. The superclass is a CoreDataFetchedResultsController. It's used to handle all of the heavy lifting with Core Data. The reason for connecting the table to the superclass is so that I can access all of the methods and update the table. I tried the IBOutlet option and could not find it when I tried to connect the tableview. It did not show up as an option when I control click dragged to the viewController that subclassed the superclass. Am I missing something here?I'd be happy to look into the protocol option with Swift 2. Do you have any resource that would explain that process? It doens't look like the documentaion is up to date yet.Take care,Jon