14 DAY TRIAL // More often than not, our weekly list of updates from Apple generally includes beta releases for the developer community. This week was no different, but at least one of these releases has proved more exciting than expected.
The week kicked off with a new iOS 8.2 seed, followed by a new version of Xcode, and a new Yosemite beta with some goodies inside. A new Server beta was also released. Get the full scoop below.
iOS 8.2 and Xcode beta 5
Labeled as build 12D4580a, the fifth beta in the iOS 8.2 development cycle continues to focus on WatchKit – a new framework for developing and testing apps for the upcoming Apple Watch.
The software now supports settings bundles for extensions running in iOS Simulator, and the app now displays the controls you specify in your settings bundle. The beta further includes Wi-Fi calling options. Registrants to the iOS Developer Program can grab this beta immediately from the iOS Dev Center.
Xcode 6.2 beta 5 merely accompanies iOS 8.2 and assists development of WatchKit software.
OS X Yosemite 10.10.3 with Photos app
One of the most exciting OS X betas released by Apple in a very long time, build 14D72i arrived this week packing an all-new Photos app that many have been eager to get their hands on.
Set to replace iPhoto, the new software makes photo management a breeze, and even includes editing features. Cloud syncing is also a key feature of Photos for Mac. We offer an extensive look at the software right here: Behold the OS X Photos App - The Best Thing Since Sliced Bread.
OS X Server 4.1 Developer Preview
Server users have a new beta to download and test out, provided that they have a registered developer account with Apple.
In this new seed, Profile Manager supports new MDM commands and payloads with iOS 8.2, a Caching Server configuration option for DNS TXT records spit out in Windows formats, and the ability to export accounts to a single file for users and groups.
According to the list of known issues, enrolling a device with a placeholder through the user portal doesn’t work as expected. A workaround is to “delete the device placeholder using Profile Manager admin and reenrolling the device,” according to the seed notes. Some issues have been addressed as well, but Server 4.1 still requires heavy testing before being promoted to Stable status.