Swift 6

Also, I'm on 28 hours on this build. Don't know if the system need settling or not. (iPhone 6/64)

Yes. Same to my iPhone 6 + last night. Battery life drains from 100% to 70% around 6 hours....Moreover, I cannot login citibank website either with safari or citibank app

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!

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

Hi jeroWe had exactly the same problem with an app that has been published for sale on June 6. Several updates of the app before that date kept the identifier. Now all our users got a new identifier, which breaks our device verification.I would be very interested if this is a one time problem or if this change is permament.I made no major change on the provisioning profile recently.

Last night i set the iPhone 6 to Airplane Mode instead of DND.7 hours Airplane Mode -> after wake up still 100% battery.deaktivated airplane mode and only read the answers here (13 eMails). Battery 95% in less than 10 minutes.poor battery life depends definitely with network activities together.only deactivate mobile data has no effect on my phone.

Thanks @marchyman for your answer. I've mistakenly pasted too small fragment of my code. Already edited original post and added missing initializers.Despite having all this initializers, I still cannot make this code work - in swift 1.2 it worked seamlessly.

The first step is probably to go to the Product menu in your project in Xcode and hold down the option key and choose Clean Build Folder..., to make sure there isn't any previously compiled code causing problems because of incompatibility.I don't think upgrading OS X to the El Capitan would improve anything for you, since a lot of us are just running Xcode 7 beta on Yosemite.If you haven't already backed up your project, you might want to do that before updating the code further, just in case you end up deciding to go back and wait.Assuming there isn't isn't anything really weird going on with your project, you would just need to work your way through it fixing the errors and warnings generated by the compiler. There can be a lot of new errors and warnings because of the changes between Swift 1.2 and 2 and the updates to Cocoa, but most of the errors and warnings should be relatively trivial to fix (changing var to let, updating the old generic sort/map/filter/find functions to be called as methods,

It's closer, but it should be called dataHasChanged or something similar, not reloadTableView. The fact that it's currently displayed in a table view should be an implementation detail known only to the detail VC. The message you send should have a higher level meaning. Picture the case where you decide to display it in a collection view, a page view controller or some other UI widget. Your source VC shouldn't have to care.Anyway I apologize that I seem to have missed the real problem with your prepareForSegue. You shouldn't instantiate the VC from the storyboard. That is already done for you by UIKit when the segue is performed. You just access the destination view controller of the segue via the segue.destinationViewController property. So it would be something along the lines of let feedVC = segue.destinationViewController as FeedViewController. Maybe some ? in there... I don't do Swift yet. 🙂

I don't understand what you mean by That is, am I missing something that prevents using only 'class'?.Anyway, are you really sure that the best thing you can do is to do it without using protocols?Even after watching the WWDC 2015 video Protocol-Oriented Programming in Swift? : )