Crashes organizer is used to view the crash reports generated for each app you distribute through the App Store or TestFlight.

Apple provides a service that collects crash logs from users and organizes them into downloadable crash reports. However, crash logs are collected only if you upload an app with the symbols. (In the Archives organizer, check the “Include app symbols for your application…” box when you upload your app to iTunes Connect.) For apps released in the App Store, the user must also agree to share crash logs with developers. TestFlight users automatically share crash logs with developers.

The service that creates the crash reports does the following:

Collects crash logs from both TestFlight and App Store builds.

Provides the total number of unique devices where the crash occurred.

Provides a sample set of crash logs for each crash report.

Removes all personal user data from the crash logs.

Creates crash reports daily.

Only a team agent or admin can view crash reports. Team members with an iTunes Connect account can also view crash reports.

Beginning May 1, 2015, new Mac apps and app updates submitted to the Mac App Store may no longer use garbage collection, which was deprecated in OS X Mountain Lion. Instead, migrate your apps to Automatic Reference Counting, using the migration assistant in Xcode to help with this transition. Apps may continue to use retain/release for manual memory management.

Automatic Reference Counting (ARC) is a compiler feature that provides automatic memory management of Objective-C objects. Rather than having to think about retain and release operations, ARC allows you to concentrate on the interesting code, the object graphs, and the relationships between objects in your application.

The size limit of an app package submitted through iTunes Connect has increased from 2 GB to 4 GB.

Please keep in mind that this change does not affect the cellular network delivery size limit of 100 MB.

In addition TestFlight you can organize your testers into groups to quickly send builds, provide separate instructions on where to focus, and apply an action to several testers at once in TestFlight. Get started in iTunes Connect.

CodeFormatter is a tool that uses Roslyn to automatically rewrite the source to follow our coding styles.

The tool itself is very simple to use; point it at a project or solution and it will systematically convert all of the code involved into the prescribed coding style. The process is very fast, taking only a few seconds for most projects and up to a couple of minutes for very large ones. It can even be run repeatedly on them to ensure that a consistent style is maintained over the course of time.

Swift has now reached 1.2 and includes a significantly enhanced compiler, as well as new features in the Swift language.

Compiler improvements

The Swift 1.2 compiler was engineered to be more stable and to improve performance in every way. These changes also provide a better experience when working with Swift in Xcode. Some of the most visible improvements include:

Incremental builds — Source files that haven’t changed will no longer be re-compiled by default, which will significantly improve build times for most common cases. Larger structural changes to your code may still require multiple files to be rebuilt.

Better compiler diagnostics — Clearer error and warning messages, along with new Fix-its, make it easier to write proper Swift 1.2 code.

Stability improvements — The most common compiler crashes have been fixed. You should also see fewer SourceKit warnings within the Xcode editor.

New language features

In Swift 1.2, the language has been further refined to ensure safe, predictable behavior. We also continue to improve the interaction between Swift and Objective-C. Some of the more notable changes include:

as! for failable casts — Casts that can fail at runtime are now expressed with the new as!operator to make their potential for runtime failure clear to readers and maintainers of your code.

Nullability may now be expressed in Objective-C headers — New Objective-C extensions in Clang allow you to express the nullability of pointers and blocks in your Objective-C API.

Swift enums can now be exported to Objective-C using the @objc attribute.

let constants are now more powerful and consistent — The new rule is that a let constant must be initialized before use (like a var), and that it may only be initialized, not reassigned or mutated after initialization.

More powerful optional unwrapping with if let — The if let construct can now unwrap multiple optionals at once, as well as include intervening boolean conditions. This lets you express conditional control flow without unnecessary nesting.

New native Set data structure — An unordered collection of unique elements that bridges with NSSet and provides value semantics like Array and Dictionary.

Swift 1.2 is a major step forward for both the language and the tools. It does include some source-incompatible changes that require updates to your code, so Xcode 6.3 includes a migrator to help automate the process. To begin the migration, click the Edit menu, then choose Convert > To Swift 1.2…