missing package product

Some websites like nytimes.com, twitter.com, cnn.com already have an icon when pinned to the top. According to “What's new in Safari 9” this code should be added in order to provide a custom icon:<link rel=icon sizes=any mask href=website_icon.svg> <meta name=theme-color content=red>That's what I did on our website (obdev.at) but Safari seems to ignore it. Anything I'm missing here? Or is there no support for third-party websites yet?

With the newest releases of iOS and iTunesConnect, Apple is more and more restrictive about what´s happening in your CFBundleVersion of your Extensions.I tried to fiddle around with Run Script Build Phases, such as this:#!/bin/sh INFOPLIST_EXT=${TARGET_BUILD_DIR}/${INFOPLIST_PATH} echo Extension writing to $INFOPLIST_EXT PLISTCMD=Set :CFBundleVersion $(git rev-list --all|wc -l) echo -n $INFOPLIST_EXT | xargs -0 /usr/libexec/PlistBuddy -c $PLISTCMDHowever, this seems to work for some types of Extensions (WatchKit), but for some others it doesn´t (Today Widget). In my cases, I seem to access the $TARGET_BUILD_DIR before there´s content in it. Using $BUILT_PRODUCTS_DIR delivers the same error.Extension writing to /Users/marc/Library/Developer/Xcode/DerivedData/MyApp-focpnqzzpnqsfyaqwwocwpujmhmh/Build/Intermediates/ArchiveIntermediates/MyApp/IntermediateBuildFilesPath/UninstalledProducts/TopNewsWidget.appex/Info.plist Set: Entry, :CFBundleVersion, Does Not Exist File Doesn't Exist, Will Create: /Users/marc/Libra

I'm finding that since i updated my (development) iPad Air 2 from 8.3 to iOS 9 Beta 1, its battery is draining like crazy. I unplugged with 100% charge last night, this morning it's alreadty dead again. It also constantly is really warm. Instruments shows blackboardd running at 20% CPU, the full time, and MobileMail running fairly high too.Mind you, this is not an ooh, i upgraded my only production-use device to a beta and now i'm complaining it's not perfect complaint, so hold back the usual snarky remarks about this. My concern is not only that this iPad is now unusable as a testing/development device, but that i'm actually worried about leaving it running like this at all, for what it might do to the CPU and the battery, long term. The only choice i'm seeing right now is powering it down completely and put it in a drawer until Beta 2 😟.

I didn't see a place to discuss Xcode 7 in the Xcode forum or the Pre-release forum. The same for new beta of OS X Server.

As I thought more about how to solve my activity data problem in a different post of mine I thought of this. My activity data for my apple watch is stored in a backup that is running iOS 8.3. My watch is now running OS 2.0 and I must have my iPhone running iOS 9 obviously to connect the two. If I continue to track my acitivity data running iOS 9 and WatchOS 2 and later when (if ever) there is a way to downgrade to Watch OS 1.0.1 again could I option-click update and go back to iOS 8.3 on my phone and restore from my backup of iOS 8.3 with that activity data to combine with the days I got running iOS 9? It's confusing and I don't know if it's possible but worth a shot.Even If I lose the activity data I have in the iOS 8.3 backup I wouldn't mind too much as long as I don't lose the activity data I have everytime I update to a new beta version.

Hello,I was wondering about failable initializers in Swift. I noticed that for structs it works as expected (at least by me), for example this is fine:struct Test { var someState: Int init?(value: Int) { if value < 0 { return nil } someState = value // we set the value after validation } }But for classes swift wouldn't allow you to fail until you set internal states like so:class Test { var someState: Int init?(value: Int) { if value < 0 { someState = 0 // this seems unneeded return nil } someState = value } }This seems wrong. Why do I need to populate class' data with unneeded default values before I can fail the initialization? I can see that this is valid for both Swift 1.2 and 2.0 so what am I missing here?