DTiPhoneSimulatorErrorDomain Code 2

Converting my app to use Swift 2, and I'm getting a crash on this if-let where clause (that worked in 1.2):Used to look like this:if showFilterButton { if let dataController = dataController() as? FilteredCoreDataController, filter = dataController.filter where filter.customized { filterButton = UIBarButtonItem(image: UIImage(named: FilterFilled), style: .Plain, target: self, action: showFilters:) } else { filterButton = UIBarButtonItem(image: UIImage(named: Filter), style: .Plain, target: self, action: showFilters:) } } else { filterButton = nil }But it crashes on line 2. Finally discovered that removing the where clause doesn't crash the app (but obviously doesn't give me the behavior I want). Thought it was something weird like Apple changing how where clauses with in an if-let clause, but even separating it out into a nested if doesn't work:if showFilterButton { if let dataController = dataController() as? FilteredCoreDataController, filter = dataController.filter {//where filter.customi

From the iOS 9 Beta Software Installation Guide:System RequirementsiOS 9 beta supports iPhone 4s or later, iPod touch (5th gen), and iPad 2 or later. iOS 9 beta should be installed using the latest released version of iTunes ...Only iPad 2 or later? Really?Then how did I just install it on a first gen iPad mini?

I'm trying to upload a new version of an app to iTunes Connect but everything I've tried so far has resulted in a Invalid Binary report by iTunes Connect. I have the Archive action set to Release and all schemes set to use the distribution certification and profile. Everything archives fine and the binary validates, but after uploading to iTunes Connect the binary moves into the Invalid Binary state and I get the following email:Invalid Signature - Code object is not signed at all. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose Clean All in Xcode, delete the build directory in the Finder, a

I have the Watch 2 Beta 1 profile installed on both my iPhone and Apple Watch. I downloaded the update through the Apple Watch app, but when it goes to install it says it failed to install. Both the watch and iPhone are fully charged and plugged in, and both have been restarted. Any ideas?

I got following error when reqeust data from non-ssl protocol with NSURLSeesion API. I think it because of ATS in iOS9. Anyone knows what I should put in plist to opt out ATS?-- ATS description from release note--App Transport SecurityApp Transport Security (ATS) lets an app add a declaration to its Info.plist file that specifies the domains with which it needs secure communication. ATS prevents accidental disclosure, provides secure default behavior, and is easy to adopt. You should adopt ATS as soon as possible, regardless of whether you’re creating a new app or updating an existing one.If you’re developing a new app, you should use HTTPS exclusively. If you have an existing app, you should use HTTPS as much as you can right now, and create a plan for migrating the rest of your app as soon as possible.---error---Error Domain=NSURLErrorDomain Code=-1200 An SSL error has occurred and a secure connection to the server cannot be made. UserInfo=0x7fcfebe17cc0 {NSURLErrorFailingURLPeerTrustErrorKey=<S

I am trying to pass data from one view controller to another view controller. Here is my code so far that I have tried, but I keep getting an error when using this code. The error says, Outlets cannot be connected to repeating content.-(void)prepareForSegue:(UIStoryboardSegue *)segue sender:(id)sender { SchoolLocationViewController *schoolLocation = [segue destinationViewController]; if ([sender isEqual:btnAbington]) { schoolLocation.campusLocation = schoolLocation.campusLabel.text = @Abington; } }

Have the following code running in 7.0 beta (7A120f) - didn't see that as a topic in the beta forum...adjusting to the forum change.let dateComponentsFormatter = NSDateComponentsFormatter() dateComponentsFormatter.allowedUnits = NSCalendarUnit.Day | NSCalendarUnit.Hour | NSCalendarUnit.Minute | NSCalendarUnit.SecondReceiving the following build error: Binary operator '|' cannot be applied to two NSCalendarUnit operands.Did not see this error in Xcode 6, not sure if this should be filed as a bug report at this juncture. Other solutions offered by the interwebs proving unviable.Thoughts?Cheers,Josh

Open Directory was added to OS X Server early on in its release form. This is after OS X transitioned away from the NetInfo directory used by its predecessor, NeXTSTEP. However, Open Directory is similar, in a few ways, to the old-style Windows NT 4.0 directory system. At the same time that Apple adopted this older system, Microsoft, with Windows 2000, moved away from it and began using their much more robust Active Directory system. For some time, I have been urging Apple to move away from the antiquated Open Directory, and use Active Directory, since it is much more flexible and powerful, makes use of multimaster replication, and is used by many, many Windows network administrators. Moving to Active Directory would make is so much easier to manage OS X Servers in enterprise settings, not requiring two separate skillsets, one for Open Directory and one for Active Directory. This would also allow Apple to have an end-to-end solution, and build out their Profile Manager and configuration profile servi