Swift 6

same here iPhone 6 plus battery is horrendous. But my iPad air 2 is actually the same it wad on iOS 8 which is great easily last a day just the iPhone with the issues

You might be right that it is part of the reason. But they didn't have to make it open source for that reason alone. Nothing prevented them from keeping their Linux port to themselves.You make it open source if there is a benefit in either driving adoption or in faster and more efficient testing and bug fixes. Swift probably reached a plateau in adoption and was surely straining their resources in testing and bug fixing given its evolution history. Now they can deploy more of those testing and maintanence resources into Xcode (which is falling behind in capabilities relative to the latest IDEs in my opinion) as well as Apple SDK support.

Same here. Every time I try to view a storyboard or .xib in Xcode 7, I get this exception:UNCAUGHT EXCEPTION (NSInvalidArgumentException): *** -containsValueForKey: only defined for abstract class. Define -[NSUnarchiver containsValueForKey:]!I can run the app fine, I just can't actually view or edit my storyboard/.xibs in Xcode anymore!Stack trace:Process: Xcode [4209] Path: /Applications/Xcode-beta.app/Contents/MacOS/Xcode Identifier: com.apple.dt.Xcode Version: 7.0 (8123.26) Build Info: IDEFrameworks-8123026000000000~7 Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: Xcode [4209] User ID: 501 Date/Time: 2015-06-10 15:05:14.928 -0400 OS Version: Mac OS X 10.10.3 (14D136) Report Version: 11 Anonymous UUID: 9B7324FE-113A-BF78-0590-ECC7DDE67CD9 Sleep/Wake UUID: A68D9DCC-EE2D-439B-B979-F232409B3139 Time Awake Since Boot: 10000 seconds Time Since Wake: 3700 seconds Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000

Hey mate, works here (iPhone 6 Plus on iOS 9.0b1)Can you expand on does not work, it's a little vague so the more informaiton the better...especially concidering this is a third-party app Apple really wouldn't have much opportunity to 'look at this and fix the issue', it might be an idea to drop an email to the Shazam support team if it's really that bad.

No problem on my iphone 6 with an backup from 8.3. So i think it isn't a problem in general.

search the archived forum for this error the package does not contain an info.plist - much was written about it back around 6 months ago.

I like paper too - we probably both have gray hair (if any hair at all 🙂). However, the frameworks change so often not sure it would be productive to print out 5000 pages of paper every few months.What I often do is print out the Guides - those change at a slower pace. Also, I bought a Kindle for the sole purpose of reading Swift docs while sitting in a sand chair at the beach, in bright light. Or read them on long flights.I haven't heard back yet from SiteSucker. Since I can access the index.html file using 'curl', I can only suppose the Apple server knows about SiteSucker and disables it from accessing the files. Really - if we could just get the book directly none of this would come into play.

You could try updating the other code yourself, since you have the source?Switching to Swift 2.0 will probably throw up a lot of errors and warnings, but most issues that need fixing tend to be simple repetitive changes that the migrator probably could have handled (changing var to let, updating the old generic functions to be called as methods, etc).It might not be very difficult at all, and when those other people update their code, you can always just swap it in.

FWIW, I also see that all the @IBOutlets in my (all-Swift) source are displaying in Xcode as unlinked from my storyboard/.xibs (even though, as I said, I can run the app just fine).