[RUS] OS X 10.11 El Capitan (15A178w) + Xcode 7 beta [PRE-RELEASE] [Intel]

Ответить на тему
Статистика раздачи
Размер:  9,59 GB   |    Зарегистрирован:  8 лет 9 месяцев   |    Скачан:  0 раз
Сидов:  604  [  0 KB/s  ]   Личеров:  29  [  0 KB/s  ]   Подробная статистика пиров
 
   
 
 
Автор Сообщение

iPhone ®

Пол:

Стаж: 8 лет 9 месяцев

Сообщений: 2149

Создавать темы 10-Июн-2015 04:00

[Цитировать]

OS X 10.11 El Capitan (15A178w) + Xcode 7 beta [PRE-RELEASE]
Год выпуска: 2015
Версия: 15A178w
Разработчик: Apple Inc.
Сайт разработчика: http://www.apple.com/
Платформа: Intel only
Язык интерфейса: русский + английский
Таблетка: Программа пролечена (не требует введения данных/вводим любые данные)
Системные требования: Перед установкой OS X El Capitan, убедитесь в том, что вы используете 64-bit Intel-based Mac с установленной Mac OS X v10.6.7 Snow Leopard или поздней версией.
У вас должно быть как минимум 8GB свободного места на диску для установки OS X v10.11.
Xcode 7 требуется для разработки приложений на OS X v10.11.
Поддерживаемые устройства: Идентичны поддерживаемым устройствам последней публичной версии OS X Yosemite.
iMac (Mid-2007 или новее)
MacBook (13-inch Aluminum, Late 2008), (13-inch, Early 2009 или новее)
MacBook Pro (13-inch, Mid-2009 или новее), (15-inch, Mid / Late 2007 или новее), (17-inch, Late 2007 или новее)
MacBook Air (Late 2008 или новее)
Mac Mini (Early 2009 или новее)
Mac Pro (Early 2008 или новее)
Xserve (Early 2009)
Описание:

Что нового в OS X El Capitan
OS X El Capitan приносит поддержку технологии Metal на Mac, давая вашим приложениям беспрецедентные графические и вычислительние мощности. С Swift 2.0, вы можете писать намного лучший код благодаря новым передовым функциям. Новые API позволяют вашим приложениям работать совместно с Photos и Safari.
Что нового в Xcode 7
Xcode 7 включает в себя все что вам нужно для создания удивительных приложений для iPhone, iPad, Mac, и Apple Watch. Язык программирования Swift был обновлен и теперь он быстрее, чем когда-либо, с невероятными возможностями, делающими ваш код более простым для написания и понимания. И с новыми плэйграундами вы можете экспериментировать с новыми API или писать великолепную интерактивную документацию, используя встроенные ресурсы, дополнительный исходный код, и богатые текстовые комментарии. Возможность Xcode тестировать пользовательский интерфейс даже может записать действия в вашем приложении и сгенерировать тесты для вас.

Оригинал

What’s new in OS X El Capitan.
OS X El Capitan brings Metal to Mac, giving your apps unprecedented graphics and computing power.
With Swift 2.0, you can write even better code thanks to advanced new features.
New extensibility APIs let your apps work seamlessly with Photos and Safari.
What’s new in Xcode 7.
Xcode 7 includes everything you need to create amazing apps for iPhone, iPad, Mac, and Apple Watch.
The Swift programming language has been updated and is now faster than ever, with great features that make your code even easier to read and write.
And with the new playgrounds you can experiment with new APIs or author gorgeous interactive documentation using embedded resources, additional source code, and rich text comments.
Xcode’s user interface testing feature can even record your app in action and generate tests for you.
Доп. информация: Также снова изменили шрифт с Helvetica Neue на San Francisco, ранее использовавшийся только на Apple Watch.

OS X v10.11 Developer Beta 1 Release Notes

Introduction
OS X v10.11 Developer Beta 1 is pre-release software. Do not use this pre-release software in a commercial operating environment or with important data. You should back up all of your data before installing this software and regularly back up data while using the software.
OS X Recovery cannot be used to re-install OS X v10.11 Developer Beta 1. If an installation of OS X v10.11 Developer Beta 1 fails, you may recover from an earlier backup, or via an OS X Recovery Disk Assistant.  More information about creating an OS X Recovery Disk Assistant is available here: https://support.apple.com/en-us/HT202294
Bug Reporting
This build is being provided to you for testing and development purposes. Should you encounter any problems, submit a bug report using the online Bug Reporter at http://bugreporter.apple.com/. Please make sure to include “10.11 (15A178w)” in the bug title and description. This information will ensure that your bug is processed quickly.
When submitting a bug report, make sure to include a Summary, Steps to Reproduce, Expected Results, Actual Results, and the diagnostic output generated by running sudo sysdiagnose in Terminal, or use the special key chord Control-Option-Command-Shift-Period.
For complete instructions on submitting bug reports, visit the Bug Reporting page at http://developer.apple.com/bugreporter/.
Developer Beta System Requirements
The OS X v10.11 Developer Beta supports the following Macs:
• iMac (Mid 2007 or newer)
• MacBook Air (Late 2008 or newer)
• MacBook (Late 2008 Aluminum, or Early 2009 or newer)
• Mac mini (Early 2009 or newer)
• MacBook Pro (Mid/Late 2007 or newer)
• Mac Pro (Early 2008 or newer)
• Xserve (Early 2009)
Notes and Known Issues
Installation
Note
• After upgrading to OS X v10.11 Developer Beta, applications that write to protected/system locations may no longer function correctly.
Known Issues
• Directly upgrading from OS X Lion or earlier to OS X v10.11 Developer Beta 1 is not recommended.
• Migration from Windows is not supported in Developer Beta 1.
AirPlay
Known Issue
• AirPlay may not connect correctly with AppleTV. If both Apple TV and sender device are not on the same network, connect AirPlay once while on the same network, then try again. Alternatively, you may reboot both the Apple TV and the Mac, then try again.
Aperture
Known Issues
• Importing RAW files may cause the app to quit unexpectedly.
• The Aperture workspace may disappear occasionally. To bring back the workspace, click on the Aperture icon in the dock.
• Some Sony RAW images may not appear correctly.
• Dismissing certain dialogs may cause the workspace to become unresponsive and require a force quit and relaunch.
• Aperture may quit unexpectedly when attempting to print photos. The Photos app can be used to print instead.
AVFoundation
Note
• In OS X v10.11 Developer Beta, AVQueuePlayer now supports a mixture of file-based media and HTTP Live Streaming media in its queue.
Bluetooth
Known Issue
• On pre-2009 Macs, Bluetooth may sometimes not show up after reboot or wake from sleep. Reboot the system to workaround.
Disk Utility
Note
• System file permissions are automatically protected, and updated during Software Updates. The Repair Permissions function is no longer necessary.
Known Issue
• Disk Image conversion and a RAID setup assistant are not available in Developer Beta 1.
Fast User Switching
Known Issue
• All users may be logged out unexpectedly when using fast user switching.
Garbage Collection
Note
• OS X v10.11 is the last major release of OS X that will support the previously deprecated garbage collection runtime. Applications or features that depend upon garbage collection may not function properly or will not launch when the runtime is removed. Developers should use Automatic Reference Counting (ARC) or manual retain/release for memory management. Xcode includes tools to aid in this migration.
iCloud
Known Issues
• If iCloud Keychain is enabled via a device running iOS 9 Beta with a Random iCloud Security Code, iCloud Keychain cannot be enabled on OS X v10.11 Developer Beta with that same Security Code. Approval from another device will allow iCloud Keychain to be enabled.
• New iCloud Mail Accounts may fail to be created.
iPhoto
Known Issues
• Sending emails from iPhoto may not work work correctly.
• Exiting Edit mode may cause iPhoto to quit unexpectedly.
• Location dropdown menus in the Places view may not work correctly.
• Faces may not be detected in newly-imported photos.
iTunes
Known Issues
• Local Contacts & Calendars may not sync via iTunes.
• Some iPod models may not be visible in iTunes or Finder when connected.
• Devices running iOS 9 Beta may not connect to iTunes on OS X v10.11 Developer Beta 1. To resolve install Xcode 7 beta.
Java
Note
• OS X v10.11 is the last major release of OS X that will support the previously deprecated Java 6 runtime and tools provided by Apple. Applications or features that depend upon Java 6 may not function properly or will not launch when Java 6 is removed. Developers should move to a newer version of Java as provided by Oracle. For more info on Java from Oracle: http://www.oracle.com/technetwork/java/javase/overview/
Logic Pro
Known Issue
• Logic Pro 9 may exit unexpectedly.
Mail
Known Issues
• Mail may fail to upgrade an existing account when OS X v10.11 Developer Beta is installed over Mac OS X Snow Leopard.
• Mail may take a longer than expected time on initial launch after upgrading.
• Gmail & Yahoo! accounts may fail to connect after several days. To resolve, quit and relaunch Mail.app.
• Time Machine cannot selectively restore deleted messages in Mail in OS X v10.11 Developer Beta 1.
• You may not be able to send email from an iCloud account after upgrading to OS X v10.11 Developer Beta 1. Sign out of your iCloud account, and sign back in to resolve this.
Metal on OS X
Known Issue
• The performance of some benchmarks may be less than expected on some 2015 systems.
Numbers
Known Issue
• Numbers.app may fail to print to a printer or save to a PDF. Export to PDF can be used as a workaround.
Photos
Note
• Photos libraries are not backwards compatible. Once a library has been opened in the OS X v10.11 Developer Beta, it will no longer be openable in OS X Yosemite or earlier.
Known Issues
• Photos must be launched once in OS X v10.11 Developer Beta 1 in order for services including iCloud Photo Library, iLife Media Browser to work correctly.
• Photos may occasionally become unresponsive when attempting to quit if the library contains certain MPEG video files.
Preview
Known Issue
• Images may become corrupted after rotation.
Safari
Known Issues
• Images and video may not load on some webpages.
• Content blockers with invalid JSON will not be loaded.
USB
Known Issues
• USB storage devices, including internal SD card readers, may become unavailable after system sleep and require either re-plug or restart to recover.
• USB input devices may become non-functional on some Macs after several days.
• USB 1.0, 1.1 and older 2.0 devices may not function.
Language
Known Issues
• Some text may not be localized to the selected system language.
• Some languages may have clipped or misaligned layout.
Auto-Submission of Diagnostic and Usage Data
By default, OS X v10.11 Developer Beta builds automatically send anonymous diagnostic and usage data back to Apple. This includes information about crashes, freezes, kernel panics, and information about how you use Apple and third-party software, hardware, and services. This information is used to help Apple improve the quality and performance of its products and services. The preference is cleared in this seed. This will allow the collection of anonymous diagnostic and usage data to help deliver a high quality release for our customers. If necessary, this setting can be disabled in the Privacy tab in the Security & Privacy preferences pane.
Legal Notices
The pre-release software identified above is Apple Confidential Information and your use of such software is subject to your Apple Developer Agreement and Apple Developer Program License Agreement. Distributing such pre-release software to anyone other than another Apple Developer who is working for the same entity as you is considered a violation of your agreement with Apple and is damaging to both Apple and those who develop for the Apple platform. We sincerely appreciate your efforts to keep this pre-release software Confidential. You agree that you will not export or reexport any of the software or Confidential Information received from Apple (a) into (or to a national or resident of) any U.S. embargoed countries (currently, Cuba, Iran, North Korea, Sudan, or Syria) without first obtaining proper authorization from the U.S. Government; or (b) to anyone on the U.S. Treasury Department’s list of Specially Designated Nationals or the U.S. Department of Commerce Denied Person’s List or Entity List or any other restricted party lists. You also agree that you will not use said software for any purposes where prohibited by United States law, including, without limitation, the development, design, manufacture, or production of nuclear, missile, chemical, or biological weapons.

Xcode Release Notes

About Xcode 7 beta
Supported Configurations
Xcode 7 beta requires a Mac running OS X 10.10.
Xcode 7 beta includes SDKs for watchOS 2.0, iOS 9 and OS X version 10.11. To develop apps targeting prior versions of OS X or iOS, see the section “About SDKs and the Simulator” in What's New in Xcode available on developer.apple.com or from the Help > What's New in Xcode command when running Xcode.
Installation
To install Xcode 7 beta, double-click the downloaded DMG file, and drag the Xcode-beta.app file to your Applications folder.
From within Xcode, you can launch additional developer tools, such as Instruments and FileMerge, using the Xcode > Open Developer Tool menu. You can keep the additional tools in the Dock for direct access when Xcode is not running.
Installing Xcode on OS X Server
To use Xcode’s Continuous Integration service with this Xcode beta, you need OS X 10.10.4 or greater with OS X Server 4.1 or greater
Once you have installed OS X, OS X Server and Xcode, point OS X Server to this Xcode beta with these steps:
1. Install Server app and Xcode
2. Launch Xcode, accept Xcode license agreement and install additional components if necessary
3. Launch Server app, initialize the server
4. Once Server is initialized, go to Xcode tab, click on Choose Xcode and select Xcode 7
5. Once Xcode Server is initialized, turn Xcode Service on
© 2015 Apple Inc. All Rights Reserved.
Technical Support and Learning Resources
Apple offers a number of resources where you can get Xcode development support:
http://developer.apple.com: The Apple Developer website is the best source for up-to-date technical
documentation on Xcode, iOS, and OS X.
http://developer.apple.com/xcode: The Xcode home page on the Apple Developer website provides information on acquiring the latest version of Xcode.
http://devforums.apple.com: The Apple Developer Forums are a good place to interact with fellow developers and Apple engineers, in a moderated web forum that also offers email notifications. The Developer Forums also feature a dedicated topic for Xcode developer previews.
Use http://bugreport.apple.com to report issues to Apple. Include detailed information of the issue, including the system and developer tools version information, and any relevant crash logs or console messages.
Deprecations and Removal Notices
• OS X 10.11 is the last major release of OS X that will support the previously deprecated garbage collection runtime. Applications or features that depend upon garbage collection may not function properly or will not launch when the runtime is removed. Developers should use Automatic Reference Counting (ARC) or manual retain/release for memory management. (20589595)

© 2015 Apple Inc. All Rights Reserved.
Xcode 7 beta — New Feature Highlights Platform Support
• Xcode 7 Beta includes SDKs for watchOS 2.0, OS X version 10.11, and iOS 9.
Swift Language
• Error Handling. Throw, catch, manage, and handle errors in Swift. Interoperate seamlessly with NSError.
• Availability. Adopt new APIs while still deploying back to older OS versions, with compile-time errors to catch situations when you’ve used API that isn’t available on the deployment target.
• Protocol extensions. Add methods and properties to any class that conforms to a protocol. Re-use more of your code.
• Testability. Write tests of Swift 2.0 frameworks and apps with access to all your public and internal routines.
• Swift 1.2 to 2.0 Migrator. Helps you upgrade your existing Swift source code to take advantage of Swift 2.0.
Objective-C Updates
• Generics. Specify type information for collections, simplifying the code you write. • Nullability. Indicate in Objective-C source when to expect nil or non-nil results.
Playgrounds
• Rich-text comments. Explain what is going on in the Swift code with a markdown-like syntax.
• Inline results. Show your code’s results directly below the code that produces them.
• Resources. Add resources like images to your playground using the project navigator.
• Auxiliary Sources. Keep additional support code separate from the playground itself.
• Pages. Bundle related concepts together with multiple, targeted to structure a playground.
App Thinning
Three complementary technologies designed to deliver optimized installation by the App Store.
• Bitcode. Archive for upload to the App Store in an intermediate LLVM binary representation that the store can then optimize into the 64 or 32-bit executable to be delivered to customers.
© 2015 Apple Inc. All Rights Reserved.
• Slicing. Artwork incorporated into the Asset Catalog and tagged for platform needs allows the App Store to deliver only what is needed for installation.
• On Demand Resources. Host additional content for your app on the iTunes App Store repository, allowing the app to fetch resources as needed using asynchronous download and installation.
Debugging
• Energy Gauge for iOS. Track energy usage with iOS 9 on a per-process basis.
• Address Sanitizer. Build instrumented Objective-C and C code to trap the sources of memory corruption problems.
Testing
• User interface testing and recording. Test applications at the user interface surface with elements, queries, and simulated events. The UI recording feature enables capture of UI actions into source to facilitate creating tests.
• Code coverage. Provides report information to evaluate a test suite for completeness. Free Provisioning
• Develop on your own device. Streamlined mechanism to provision and install development project on physical devices for testing and evaluation.
Crash Logs
• Test Flight and Crash Reports. Enhanced to allow using crash data from OS X apps as well as
watchOS and iOS apps.
© 2015 Apple Inc. All Rights Reserved.
New Features in Xcode 7 beta IDE Swift in Xcode
• Playgrounds support multiple pages. You can add a new page to any playground by selecting File > New Playground Page. In the navigator and jump bar, you'll see all pages in the playground. You can add navigation between pages with the new page navigation markup (20192277):
Navigation relative to pages in the playground: [Go to First Page](@first)
[Go to Last Page](@last)
Navigation relative to the current page: [Go to Next Page](@next)
[Go to Previous Page](@previous)
Navigation to a specific page: [Go to Overview](Overview) [Go to Sorting](Sorting)
• You can use the assistant editor to get a summary of the interface of your Swift classes. When viewing a Swift file in the primary editor, the Counterparts assistant will show a summarized version of the class that includes declarations (but not implementation) of the methods and functions in your file along with documentation comments. (17684981)
• A migrator is available to help migrate your code from Swift 1.2 to Swift 2.0. Select Edit->Convert->To Latest Swift Syntax. The migrator is fully effective when it is applied on Swift 1.2 projects. If the migrator detects that the code is fully or partially migrated to Swift 2.0, it will only perform simple changes to correct certain compiler diagnostics. (19653306)
• "Generated Interface" of the assistant editor can be used to get the Swift interface of an Objective-C header file in your own project. (19320817)
• Xcode 7 has a optimization-level menu for Swift under ‘build settings’. It is possible to select Whole-Module optimization from the optimization-level menu. Previously, unchecked build were an optimization level.
• Use the “disable safety checks” build setting to disable runtime checks.
• Compiling Swift projects in Whole Module Optimizations mode will parallelize some compilation phases, which reduces compile time.
Interface Builder
• Default keyboard shortcuts for zooming in Interface Builder have been changed to match the rest of Xcode. (15057238, 16530809)
• Interface Builder adds the ability to edit auxiliary objects belonging to a storyboard scene. (9478187)
© 2015 Apple Inc. All Rights Reserved.
• Interface Builder supports the new NSCollectionView API in 10.11, using dataSource and layouts like on iOS. (18997303)
Workaround: It is not possible to configure prototype items in Interface Builder. Use -[NSCollectionView registerClass:forItemWithIdentifier:] or -[NSCollectionView registerNib:forItemWithIdentifier:] in code.
• Notes from Interface Builder’s Identity inspector are included in --export-strings-file output and XLIFF files exported using the project editor’s Export For Localization feature. (18023555)
• Interface Builder supports placeholder references for scenes in other storyboards, and segues that cross storyboard boundaries. (9565583)
• Interface Builder can set multiple left/right bar button items in iOS projects. (10293104)
• Interface Builder enables setting the accessiblityIdentifier property of AppKit and UIKit views, via the Identity inspector. (8913778, 20377226)
• Interface Builder adds authoring support for the new UIStackView (iOS 9) and exposes a distribution property for NSStackView (OS X 10.11). Access this with the "Embed In Stack View" button at the bottom right of the canvas. (18420765)
• Background placeholders on custom views and other containers can be hidden on the Interface Builder canvas with the option "Editor->Canvas->Show Background Placeholders".
• Resize knobs for views on the canvas are interactable outside the canvas frame (15864964)
• Background placeholders on custom views and other containers can be hidden on the Interface Builder canvas with the option "Editor->Canvas->Show Background Placeholders”. (20580948)
• Interface builder adds additional constraint types, including proportional width and height constraints in superviews (such as the content view of a window, or view of a view controller). (17011782)
• Interface Builder documents with a development target Find Selected Symbol in Project" menu item. (15573153)
• Find navigator shows caller hierarchy. Select a function or method, and right-click to “Find Call Hierarchy” (15716883)
• The Find navigator also displays the language for .strings files containing matches. (18372154)
Schemes
• Users can toggle all the checkboxes in a column in the Manage Schemes sheet by holding down the option key when clicking a checkbox. (8096575)
© 2015 Apple Inc. All Rights Reserved.
Resolved Issues in Xcode 7 beta — IDE Interface Builder
• Interface Builder allows setting an identifier for an auto layout constraint, to assist in debugging unsatisfiable constraints. (13645911)
• Holding the Command (⌘) key while dragging to move a view will keep the dragged view in the same container, rather than making it a subview of a view it is dragged over. (18683271)
• Additional types of constraints can be created in Interface Builder including proportional width and height constraints to any superview such as the content view of a window or view of a view controller. (17011782)
Build System
• Fixed an issue which could cause Xcode to occasionally fail to rebuild some source files when their imported headers changed. (13697791)
• Improved the heuristic used to throttle the build system's parallelism under memory pressure. (20245603)
• Fixed an issue which could cause Xcode to use less parallelism when building than it should. (17665160)
• Xcode performance when reloading .xcconfig files from disk is significantly improved. (14136335)
• Fixed an issue which caused stopping a build to sometimes take much longer than it should. (10233505)
• A "Copy Files" build phase on a framework target with a destination of "PlugIns" will now copy its contents to the "PlugIns" directory in the framework rather than the "Resources" directory. (11488493)
• "Other Code Signing Flags" (OTHER_CODE_SIGN_FLAGS) build setting properly handles spaces. (18977465)
Instruments
• With iOS 9.0 devices, Leaks recordings should no longer get stuck "Analyzing Process." (18215045) • When profiling Swift Apps, standard library symbols should be correctly symbolicated. (21131543)
General
• Run Script scheme actions take the run destination into account when passing environment variables, such as SDKROOT, that depend on the run destination. (19652312)
• When opening a workspace with more than 80 targets for the first time, Xcode prompt you to ask if you want Xcode to autocreate schemes for those targets instead of doing so automatically. (20877091)

© 2015 Apple Inc. All Rights Reserved.
Known Issues in Xcode 7 beta — IDE Projects
• If you have accepted Xcode's "Upgrade to recommended settings" project modernization to adopt the new Product Bundle Identifier (PRODUCT_BUNDLE_IDENTIFIER) build setting, the Bundle Identifier field in the General tab of the target editor will no longer be editable. (20888003)
Workaround: You can edit your bundle identifier in the Build Settings tab with the Product Bundle Identifier build setting.
• Sometimes projects may fail to build because a storyboard fails to compile with the error “A file with the name “IB” already exists”. (20771842)
Playgrounds
• Opening a Playground that was previously displaying the Version Editor may present an alert stating, “The file “MyPlayground.playground” couldn’t be opened because you don’t have permission to view
it.” (20623808).
Workaround: Dismiss the alert dialog and show the Standard Editor (Command-Return).
• Playgrounds sometimes show a window with no editor if they are opened as part of Xcode launching (20694143)
Workaround: Close and re-open the playground.
• Executing an iOS Playground for the first time may take longer than subsequent executions. (21163503)
• For old-style playgrounds, the menu item Edit->Convert->To Latest Swift Syntax... is greyed out. (20902099)
Workaround: Upgrade the playground before attempting to convert to Swift 2.0 by choosing Editor- >Upgrade Playground...
• Playground pages may recompile each time they are navigated to, even when there are no changes. (21177662)
• Playgrounds live views may not show images when using the timeline slider. (21261310)
Source Editor
• Xcode may crash when editing source code while also viewing the generated interface in the assistant editor. (21211565)
Workaround: Don’t edit sources while also viewing the generated interface.
© 2015 Apple Inc. All Rights Reserved.
Compiler
• dsymutil may print warnings about unresolved external types when compiling C++ projects with precompiled headers. (21170404)
Workaround: Avoid using precompiled headers in cases where you see this problem.
Build System
• If you change the value of the PRODUCT_BUNDLE_IDENTIFIER build setting and then rebuild, the Info.plist will not regenerate. (21066965)
Workaround: Perform a clean after changing the PRODUCT_BUNDLE_IDENTIFIER build setting.
• Deployment of 64-bit-only iOS apps to devices running iOS versions earlier than 8.0 does not work; it will fail with an error that the app "specifies device capability requirements which are not met”. (21195657)
Workaround: Configure your project to build for more than one architecture, as the problem only occurs when building *only* for arm64: Make sure that your target(s) have their Architectures build setting set to build for multiple architectures, and turn off Build Active Architecture Only for the target+configuration in question.
Simulator
• Xcode 7.0 beta does not support iOS 8.4 and earlier simulator runtimes. (20699475)
• When launching an app for the first time in the Simulator, the launch may hang. (20940542)
Workaround: Stop and re-run the app.
• Background upload/download using NSURLSession will complete, but notifications will not badge the app to show completion when the app is in the background. (16532261)
Workaround: Test on device to confirm works as expected.
• Printing from Simulator does not work with the iOS 9.0 beta runtime. (19754468)
Workaround: Test printing from a device with iOS 9.0 beta.
• When launching an app in the sim, the launch screen will sometimes be in the wrong orientation. (20876494)
• On first launch of the Simulator, a ServerFileProvider crash will appear in the User/Library/Logs/ DiagnosticReports folder. (20985383)
Workaround: This crash is benign and should not effect production of any kind.
• iPad Air Simulator should have limited multi-tasking capabilities (overlay and PiP only). There is no difference in the iPad Air and iPad Air 2 simulators. (21051850)
• Playing video to a simulated external display does not function correctly with iPad Simulators. (17979778)
© 2015 Apple Inc. All Rights Reserved.
Workaround: Use an iPhone Simulator.
• Video playback is often incorrectly cropped or translated when playing back on a TVOut display in Simulator. (19394195)
Workaround: Test video playback on a physical device
• Playing back video to a 1080p external display in Simulator will actually render at a lower resolution (18296724)
Workaround: Play video at a lower resolution or test 1080p playback with a physical device
• If an External Display is open when you switch simulators, the sim will get stuck at the Apple Logo. (21224352)
Workaround: Disable external display and reboot the simulated device.
• Restoring from TimeMachine backup after running Xcode 7 will result in no simulator devices listed in Xcode by default. (21215747)
Workaround: Either create your desired devices from Xcode's Devices Window or delete ~/Library/ Developer/CoreSimulator prior to running Xcode after a reboot.
• Simulator target are missing on first launch, after a clean install. Workaround: Quit Xcode and relaunch.
• Downloads for old Simulators are not available. (21060833)
Debugger
• When debugging your view hierarchy, the inspector will not update when selecting views in the debug navigator. (20748069)
Workaround: Click on the view in the editor area.
Address Sanitizer
• There are known problems with using the address sanitizer on app extensions on iOS devices (21118074).
GPU Debugger
• Shader profiling is disabled when capturing a frame from Metal applications using Nvidia GPUs. (21165399)
Instruments
© 2015 Apple Inc. All Rights Reserved.
• Launching Instruments without first launching Xcode.app and installing required components suggested by Xcode may result in Instruments.app crashing on launch. (20844043)
Testing
• Xcode does not show code coverage information for source files in static libraries. (15605406) Workaround: Add the source files directly to application or framework targets.
• Code coverage does not work with UI testing. (20966994)
• Long assertions in the test report are truncated. (21083089)
Workaround: The full text of assertions can be found in the Logs tab.
• The side bar of a source editor for a test class will not always reliably show or update test indicators when the Test navigator is not showing. (20553093)
Workaround: Revealing the Test navigator should resolve this issue.
• UI testing cannot identify elements using information from their accessibility title element. (20409319)
Workaround: Set an accessibility identifier instead.
• UI testing may fail to find elements with names containing decomposable Unicode characters. (20804391)
Workaround: Use NSPredicate to explicitly match against key paths including precomposedStringWithCanonicalMapping, e.g. title.precomposedStringWithCanonicalMapping.
• UI testing cannot record or interact with popovers on OS X. (21162677)
• Recording UI tests do not work if the device or simulator is in landscape orientation. (21096781) • UI tests do not support key modifiers on iOS. (21033224)
• Auto-correct interferes with UI tests that type text, making results unpredictable. (21106884)
Workaround: Disable auto-correct on devices and simulators used for UI testing.
• The “Record UI Test” button sometimes causes Xcode to hang if the applications is not already running. (21224350)
Workaround: Launching the application before clicking the “Record” button should resolve this.
• The “Edit ▸ Convert ▸ To XCTest...” command will fail with an error that SenTestingKit.framework cannot be found. (21251738)
Workaround: Use an older Xcode to convert tests written using OCUnit to XCTest.
• The OCUnit to XCTest migrator leaves test targets still linking against SenTestingKit.
Workaround: Manually remove the SenTestingKit linkage.
© 2015 Apple Inc. All Rights Reserved.
• After running performance tests within Xcode, the ability to inspect results and edit target criteria is missing. (21252208)
Workaround This functionality is available in the Source Editor. After running the performance tests, open the test class in the Source Editor and click on the Performance Result near the right side of the editor. This should reveal the Performance Result and allow editing of the Baseline and Max STDDEV values.
• UI recording’s generated code for Swift is incorrect for multiple modifiers. (21183420)
Workaround: Re-write option sets to be surrounded with [] brackets instead of parentheses and delimited using commas ','
• API and data needed to automate complex controls such as sliders and date pickers is not available. (20577276)
• The Automation Instrument may hang when starting capture in the Simulator. (21196158) Workaround: Quit the Simulator and re-try.
Interface Builder
• Distance guides, which are displayed when holding the Option key while hovering over a view hierarchy in Interface Builder, may not appear when using Xcode 7.0 on Mac OS X 10.11. (20758551)
• The Interface Builder Connections Inspector does not show a view outlet for Swift ViewController subclasses if they are marked with @objc but do not have an exported class name(20909753)
Workaround: Add the exported class name in parens, such as @objc(MyClass)
• Xcode crashes when searching in a project that has an OS X Storyboard with a Custom Segue. (21154156)
Workaround: Use a Find scope to filter out Storyboards or remove the Custom Segue.
• Items in Xcode's Find Navigator scope picker outline view are invisible on 10.11 (20275994)
Workaround: Moving the Xcode window will cause the outline view to redraw.
• Storyboard References do not work with WatchKit storyboards. (21191010)
On Demand Resources
• Adding or removing tags for On Demand Resources content may not take effect. (21169688)
Workaround: Delete the app from the device or simulator and then re-install the app.
• Xcode may emit a warning that "Application Slicing is disabled for this seed of Xcode if size classes are
used.” (21278829)
Workaround: Set ENABLE_ONLY_ACTIVE_RESOURCES to disable the warning.
© 2015 Apple Inc. All Rights Reserved.
Localization
• During XLIFF export or import, NSLocalizedString macro issues or empty strings files may result in an error "The data couldn’t be read because it isn’t in the correct format”. (21101899)
Workaround: Remove empty strings files from your project, or use the following command to find NSLocalizedString macro issues in your project.
find -name "*.m" -exec xcrun extractLocStrings {}
\;
• Localization stringsdict files may result in an error "failed to read strings file" during XLIFF export or import. (21113196)
Workaround: Remove the stringsdict files from your target's copy files phase.
Source Control
• When committing a removed file to a Git repository, the file will be deleted on disk but not removed from the Git repository. (21222457)
Workaround: Commit deleting files from a released version of Xcode or from Terminal. The files will remain missing from the local repository after the commit in Xcode 7 and can be committed from another Xcode or Terminal.
• Existing Source Control accounts may appear with empty passwords after launching. Workaround: Re-enter the password.
Xcode Server
• Continuous integration bot email notifications may not send by default on some networks. (21189162)
Workaround: Configure a custom SMTP relay server using `sudo xcrun xcscontrol --configure-email- transport server`.
• Existing Xcode Server instances upgraded to Xcode 7 may take some time to migrate and update bot history data. (21252055)
Core Data
• The mapping model template assistant is not available. (20267140) Workaround: Use an earlier version of Xcode to create a mapping model.
• Generating NSManagedObject subclasses for multiple entities crashes Xcode. (20638023)
Workaround: Repeat operation until it works or generate a subclass for each entity individually.
© 2015 Apple Inc. All Rights Reserved.
Free Provisioning
• Accounts with expired Apple Developer Program memberships may not be able to use free provisioning. (20486606)
Workaround: Create a new Apple ID and enter it into Xcode's Accounts preference pane.
• The list of teams displayed within Xcode's Accounts preference pane may not update to show your new free provisioning team. (19775448)
Workaround: Remove your Apple ID and add it again in Xcode's Accounts preference pane.
• When logging in via the Preferences window’s Accounts pane, any standard Apple ID will allow you to log in and use Free Provisioning. Such logins will not be subject to the Apple Developer Program License Agreement. (21243707)
• You may be asked to select between a free membership and your company team membership when configuring apps for distribution. (20276021)
Devices
• An error message incorrectly states “To fix this issue, you need to add an Apple ID account that is enrolled in the Apple Developer Program.” (21245164)
Workaround: Users can fix problems without an Apple ID account that is enrolled in the Apple Developer Program.
watchOS
• There are known performance issues developing watchOS 2 applications on devices. Significant delays during Watch app installation and launching with the debugger are also known and will be addressed in future seeds.
• You may experience installation errors and issues when deploying your app to a watchOS 2 device or Watch simulator.
Workaround: Try the following methods.
1. IfanerrorsheetlistingsomeFBSerrorshowsup,justrunagain.
2. DeletetheiOSappanrunagain.
3. Ensurethatthe‘ShowApponAppleWatch’isselectedintheAppleWatchappfordevice.
4. RestartXcode,theWatchandtheiPhonedevices/simulators.
5. Reset the Simulator and Simulator (Watch). To reset the simulators, select the menu, Simulator ->
Rest Content and Settings. Then quit them and let Xcode restart them when you Run.
6. Restartyourcomputeraftertryingthestepsaboveifnecessary.
• The Watch simulator may stop taking input after a reset or reboot. If it doesn’t respond to the Home button, quit and restart the Watch simulator application. (21135676)
© 2015 Apple Inc. All Rights Reserved.
• If the watch never displayed the trust dialog or don't trust was selected then when you try to Build & Run on the watch, the Debug Navigator will remain empty and not show the '(e) com.xxx.xxx waiting to attach' item.
Workaround: Disconnecting the iPhone from the Mac and reconnecting it should cause the trust prompt to appear on the Apple Watch. If it still doesn't show then reboot the Apple Watch. A last workaround would be to un-pair the Apple Watch and re-do the pairing with the iPhone.
• When building and running your iOS app containing a WatchKit 2 app, the full WatchKit 2 app may be transferred to your Watch and installed each time even if nothing has changed. (21126483)
• The Debug->Attach To Process menu in Xcode doesn't list processes on the Watch. (20962546)
• When performing the Profile action from Xcode on a WatchKit App the first time, Instruments will show the iOS companion device instead of the watch in the device and process chooser control. Instruments will fail to launch the WatchKit App properly. (21241660)
Workaround: Launch the Profile action from Xcode again.
• When performing the Profile action from Xcode on a WatchKit App, Instruments may report ‘The document “pbxperfconfig.plist” could not be opened.” (21161649)
Workaround: Leave Instruments open, and try running the Profile action from Xcode again. Ensure that the iPhone paired with the Apple Watch is connected to the development OS X system by USB cable.
• When Instruments launches a WatchKit App in System Trace and Time Profiler, Instruments will not get symbols for any system frameworks, instead only displaying addresses. (21259392)
Workaround: Run the WatchKit App through Xcode, then have Instruments Time Profile attach to the already-running process.
• Storyboard References do not currently work with WatchKit storyboards. (21126778)
• For WatchKit storyboards on OS X 10.11, the glance interface controller attributes inspector may fail to open the popover for selecting a glance template type.
Workaround: Resize the Xcode window and try again.
• If your home directory is on a case-sensitive filesystem, WatchKit 2 app debugging is not supported. (21123503)
• Building and running as glance will not work if glance isn't enabled in the WatchKit 2 app.
Workaround: Once you build and run your app for the first time, launch the Apple Watch app and enable the glance for your app. After that, build & run as a glance from Xcode should work.
• When using Xcode or Instruments, there may be times when an Apple Watch device is listed as offline even though the companion iPhone is attached to the computer. (21104615)
Workaround: Restart Xcode or Instruments.
• Address sanitizer is not supported on watchOS and the watch Simulator (19789677).
© 2015 Apple Inc. All Rights Reserved.
• If your home directory is on a case-sensitive filesystem, native watch app debugging is not supported. (21123503)
• When developing on Apple Watch with Xcode, ensure that Automatically Download Apps is enabled under Apple Watch->General->Automatic Downloads, so that WatchKit Apps are automatically installed on the Watch and available for debugging, when building/running from Xcode. (21171436)
• Unable to debug WatchKit 1 app extensions in a project that also has WatchKit 2 apps. (21173814)
Workaround: There isn't currently a way to select the WatchKit 1 app as the one to launch when both exist in the same host iOS app. You need to thin it to the watchKit 1 app for it to work by removing the Watch directory in the host iOS app. Alternately, duplicate the iOS build product and only include the WatchKit 1 app.
General
• Devices running iOS 8.4 beta software are not supported with Xcode 7 beta. (21107693)
• Submitting an archive built with BITCODE_ENABLED=NO will fail during upload. (21247555)
Workaround: Build the archive with BITCODE_ENABLED=YES and then uncheck the “Include bitcode” option when distributing the archive (functionally equivalent).
© 2015 Apple Inc. All Rights Reserved.
New in Swift 2.0 and Objective-C Swift Language Features
• Error handling. You can create functions that throw, catch, and manage errors in Swift. You can surface and deal with recoverable errors, like “file-not-found” or network timeouts. Swift’s error handling interoperates with NSError. (17158652)
• Availability checking. Swift reports an error at compile time if you call an API that was introduced in a version of the operating system newer than the currently selected deployment target. To check whether a potentially unavailable API is available at run time, use the new #available() condition in an if or guard statement. (14586648)
For example:
if #available(iOS 8.0, OSX 10.10, *) {
// Use Handoff APIs when available.
let activity =
NSUserActivity(activityType:"com.example.ShoppingList.view")
activity.becomeCurrent()
} else {
// Fall back when Handoff APIs not available.
}
• You can specify availability information on your own declarations with the @available() attribute. (20938565)
For example:
@available(iOS 8.0, OSX 10.10, *)
func startUserActivity() -> NSUserActivity {
... }
indicates that the startUserActivity() method is available on iOS 8.0+, on OSX 10.10+, and on all versions of any other platform.
• Protocol extensions. Extensions can be written for protocol types. This allows methods and properties to be added to any type that conforms to a particular protocol, allowing you to reuse more of your code. This leads to more natural caller side “dot” method syntax that follow the principle of “fluent interfaces” and makes the definition of generic code simpler (reducing “angle bracket blindness”). (11735843)
• Protocol default implementations: Protocols can have default implementations for requirements specified in a protocol extension, allowing “mixin” or “trait” like patterns.
• New defer statement. This statement runs cleanup code when the scope is exited, which is particularly useful in conjunction with the new error handling model. (17302850)
For example:
func xyz() throws {
let f = fopen("x.txt", "r")
defer { fclose(f) }
try foo(f)
let f2 = fopen("y.txt", "r")
// f is closed if an error is propagated.
© 2015 Apple Inc. All Rights Reserved.
 defer { fclose(f2) }
try bar(f, f2) // f2 is closed, then f is closed if an error is propagated. } // f2 is closed, then f is closed on a normal path
• New guard statement: This new statement allows you to model an early exit out of a scope. For example: guard let z = bar() else { return }
use(z)
The else block is required to exit the scope (e.g. with return, throw, break, continue, etc) or end in a calltoa@noreturnfunction. (20109722)
• Improved pattern matching. switch/case pattern matching is available to many new conditional control flow statements, including if/case, while/case, guard/case, and for-in/case. for/in statements can also have ‘where’ clauses, which combine to support many of the features of list comprehensions in other languages.
• New do statement: Scopes can be introduced with the do statement.
For example:
do {
//new scope
do {
//another scope
}
}
• Testability. Tests of Swift 2.0 frameworks and apps are written without having to make internal routines public. Use @testable import {ModuleName} in your test source code to make all public and internal routines usable. The app or framework target needs to be compiled with the "Enable Testability" build setting on. The "Enable Testability" build setting should only be used in your Debug configuration, as it will prohibit optimizations that depend on not exporting internal symbols from the app or framework. (17732115)
• Native support for C function pointers: C functions that take function pointer arguments can be called using closures or global functions, with the restriction that the closure must not capture any of its local context. (16339559)
For example, the standard C qsort function can be invoked as follows:
var array = [3, 14, 15, 9, 2, 6, 5]
qsort(&array, array.count, sizeofValue(array[0])) { a, b in
return Int32(UnsafePointer(a).memory - UnsafePointer(b).memory)
}
print(array)
• Improved diagnostics: A new warning has been introduced to encourage the use of let instead of var when appropriate, a warning has also been introduced to about unused variables (15975935), invalid mutation diagnostics are more precise, unreachable switch cases cause a warning, and the switch statement exhaustiveness checker is smarter (20130240).
• SIMD Support:Clang extended vectors are imported and usable in Swift, enabling many graphics and other low-level numeric APIs (e.g. simd.h) to be usable in Swift.
• Enums support multiple generic associated values. (15666173)
© 2015 Apple Inc. All Rights Reserved.
For example:
enum Either {
case Left(T), Right(U)
}
• Printing values of certain enum types shows the enum case and payload, if any. This is not supported for @objc enums or certain enums with multiple payloads. (18334936)
• Public extensions of generic types are permitted. (16974298) For example:
public extension Array { ... }
• Non-generic classes may inherit from generic classes. (15520519)
• Concatenation of Swift string literals, including across multiple lines, is a guaranteed compile-time optimization, even at -Onone. (19125926)
• Failable convenience initializers are allowed to return nil before calling self.init. (20193929) Designated initializers still must initialize all stored properties before returning nil, which is a known limitation.
• Nested functions can recursively reference themselves and other nested functions. (11266246)
• if statements can be labeled, and labeled break statements can be used as a jump out of the matching if statement. Note that an unlabeled break does not exit the if statement, it exits the enclosing loop or switch statement, or is illegal if there is none. (19150249)
• A new x? pattern can be used to pattern match against optionals as a synonym for .Some(x). (19382878)
• A new @nonobjc attribute is introduced to selectively suppress ObjC export for instance members that would
otherwise be @objc. (16763754)
• A new readLine() function has been added to the standard library. (15911365)
Swift Language Changes
• The OS X 10.11, iOS 9, and watchOS 2 SDKs have adopted modern Objective-C features like nullability, typed collections, and others to provide an improved Swift experience.
• The standard library moved many generic global functions (such as map, filter, and sort) to be methods written with protocol extensions. This allows those methods to be pervasively available on all sequence and collection types and allowed the removal of the global functions.
• Methods and functions have the same rules for parameter names. You can omit providing an external parameter name with _. To further simplify the model, the shorthand # for specifying a parameter name has been removed, as have the special rules for default arguments. (17218256)
Declaration
func printFunction(str: String, newline: Bool)
func printMethod(str: String, newline: Bool)
func printFunctionOmitParameterName(str: String, _ newline: Bool)
© 2015 Apple Inc. All Rights Reserved.
Call
printFunction(“hello”, newline: true)
printMethod(“hello”, newline: true)
printFunctionOmitParameterName("hello", true)
• NS_OPTIONS types get imported as conforming to the OptionSetType protocol, which presents a set-like interface for options. (18069205)
Instead of using bitwise operations such as:
// Swift 1.2:
object.invokeMethodWithOptions(.OptionA | .OptionB)
object.invokeMethodWithOptions(nil)
if options & .OptionC == .OptionC {
// .OptionC is set
}
Option sets support set literal syntax, and set-like methods such as contains: object.invokeMethodWithOptions([.OptionA, .OptionB])
object.invokeMethodWithOptions([])
if options.contains(.OptionC) {
// .OptionC is set
}
A new option set type can be written in Swift as a struct that conforms to the OptionSetType protocol. If the type specifies a rawValue property and option constants as static let constants, the standard library will provide default implementations of the rest of the option set API:
struct MyOptions: OptionSetType {
let rawValue: Int
static let TuringMachine = MyOptions(rawValue: 1)
static let LambdaCalculus = MyOptions(rawValue: 2)
static let VonNeumann = MyOptions(rawValue: 4)
}
let churchTuring: MyOptions = [.TuringMachine, .LambdaCalculus]
• The do/while loop is renamed to repeat/while to make it obvious whether a statement is a loop from its leading keyword. (20336424)
In Swift 1.2:
do {
...
} while
In Swift 2.0:
repeat {
...
} while
© 2015 Apple Inc. All Rights Reserved.
• println and print have been merged together into a single print function with a default argument (20775683)
In Swift 1.2:
func print()
func println()
In Swift 2.0:
func print(, appendNewline: Bool = true)
• Swift documentation comments use a syntax based on the Markdown format, aligning them with rich comments in playgrounds. (20180161)
Outermost list items are interpreted as special fields and are highlighted in Xcode's QuickHelp.
There are two methods of documenting parameters: parameter outlines and separate parameter fields. You can mix and match these forms as you see fit in any order or continuity throughout the doc comment. Because these are parsed as list items, you can nest arbitrary content underneath them.
Parameter outline syntax:
- Parameters: - x: ...
- y: ...
Separate parameter fields:
- parameter x: ... - parameter y: ...
Documenting return values:
- returns: ...
Other special fields are highlighted in QuickHelp, as well as rendering support for all of Markdown
• The CFunctionPointer U> type has been removed; C function types are specified using the
new @convention(c)attribute. Like other function types, @convention(c) T -> U is not nullable unless made optional. The @objc_block attribute for specifying block types has also been removed and replaced by @convention(block). (16339559)
• Type annotations are no longer allowed in patterns and are considered part of the outlying declaration. (20167393)
This means that code previously written as:
var (a : Int, b : Float) = foo()
needs to be written as:
var (a,b) : (Int, Float) = foo()
if an explicit type annotation is needed. The former syntax was ambiguous with tuple element labels.
© 2015 Apple Inc. All Rights Reserved.
• Deprecated enum elements no longer affect the names of non-deprecated elements when an Objective-C enum is imported into Swift. This may cause the Swift names of some enum elements to change. (17686122)
• All enums imported from C are RawRepresentable, including those not declared
with NS_ENUM or NS_OPTIONS. As part of this change, the value property of such enums has been renamed rawValue. (18702016)
• find has been renamed to indexOf(). sort has been renamed to sortInPlace(), and sorted() becomes sort().
• String.toInt() has been renamed to a failable Int(String) initializer, since initialization syntax is the preferred style for type conversions.
• String no longer conforms to SequenceType, to prevent non-unicode correct sequence algorithms from being prominently available on String. To perform grapheme-cluster-based, UTF8-based, or UTF-16-based algorithms, use the .characters, .utf8, and .utf16 projections respectively.
• Generic functions that declare type parameters not used within the generic function’s type produce a compiler error. For example:
func foo() { } // error: generic parameter ’T’ is not used in function
signature
Objective-C Language Features
• Lightweight generics allow you to specify type information for collection classes like NSArray, NSSet, and NSDictionary. The type information improves Swift access when you bridge from Objective-C and simplifies the code you have to write. (6294649)
For example:
NSArray *images;
NSDictionary *resourcesByName;
• A kindof type is introduced. Objects declared as __kindof types behave like a mix of ‘id’ and a specific object type: they specify an upper bound (e.g., must be UIView or a subclass thereof) but allow implicit downcasting to any subtype of that upper bound. (19589424)
For example, if we assume that -[UIView subviewWithTag:] produces a kindof type UIView *, then:
UIButton *button = [view subviewWithTag:0]; // okay: UIButton is a UIView
[[view subviewWithTag:0] setTitle:@"Bounded" forState: UIControlStateNormal]; //
okay: method found in UIButton
UIResponder *responder = [view subviewWithTag:0]; // okay: UIView is a
UIResponder
NSString *string = [view subviewWithTag:0]; // error: UIView is unrelated to
NSString
© 2015 Apple Inc. All Rights Reserved.
• C functions that return Core Foundation objects via out-parameters can describe whether the object is returned at +0 or +1. (18742441)
OSStatus MyCFGetImportantValue(CFDictionaryRef data, CFStringRef __nullable *
__nonnull CF_RETURNS_NOT_RETAINED outImportantValue);
OSStatus MyCFCopyImportantValue(CFDictionaryRef data, CFStringRef __nullable *
__nonnull CF_RETURNS_RETAINED outImportantValue);
• The NS_SWIFT_NAME macro can be used to control the imports of enumerations whose constants don’t map cleanly to Swift. (19240897)
For example:
typedef NS_ENUM(NSInteger, DisplayMode) {
DisplayMode256Colors NS_SWIFT_NAME(With256Colors),
DisplayModeThousandsOfColors,
DisplayModeMillionsOfColors
};
is imported into Swift as
@objc enum DisplayMode : Int {
case With256Colors
case ThousandsOfColors
case MillionsOfColors
}
The macro can also be used to control whether factory methods are imported as initializers. For example,
@interface MyController : UIViewController
+ (instancetype)standardControllerForURLKind:(URLKind)kind
NS_SWIFT_NAME(init(URLKind:));
@end
will be imported into Swift as
class MyController : UIViewController {
init(URLKind kind: URLKind)
}
even though its name does not follow the convention for automatic factory method importing.
© 2015 Apple Inc. All Rights Reserved.
Resolved Issues Swift 2.0
• Generic type requirements print correctly in the generated module interface for Swift instead of showing up as “T == T”. (19963093)
• Various problems involving protocol conformances not being visible across different Swift files have been fixed (18405215). Additionally, duplicate symbol errors due to protocol conformances being distributed across several Swift files have been eliminated (18448811).
• The compiler produces a warning in cases where a method of a non-NSObject-derived class is very close to an optional protocol requirement but does not match because it is not exposed to Objective-C (20219297). For example:
class MyController : UIWebViewDelegate {
func webViewDidStartLoad(v: UIWebView) { ... } // warning: non-@objc
method ‘webViewDidStartLoad’ cannot satisfy optional requirement of @objc
protocol ‘UIWebViewDelegate'
}
• Adding @objc(propertyName) on a Swift property affects the Objective-C name of the property as well as
the default Objective-C getter and setter names (19408726). For example:
class MyClass : NSObject {
@objc(theProperty) property: String // Objective-C property is named
“theProperty”
// Objective-C getter is named “theProperty”
// Objective-C setter is named “setTheProperty:”
}
• The implicit “self” argument to methods is passed as a +0 value instead of a +1 value, leading to significant performance increases for recursive methods (15729033).
© 2015 Apple Inc. All Rights Reserved.
Known Issues Swift Migrator
• “Convert to Latest Swift” may generate build errors when run. These errors can be safely ignored and don’t affect the source changes that are produced. (19650497)
• If the migrator is run on code that already migrated to 2.0 and it fails to detect Swift 2.0 syntax, the migrator may perform an unnecessary transformation of a print(argument) call to print(argument, appendNewline: false). (20882092)
• Call sites affected by SDK nullablity changes are not transformed comprehensively by the migrator. (20984190)
Swift
• Extended documentation for the Swift standard library is not included in the QuickHelp popover. (21234431) View the comments embedded in the Swift standard library.
Swift Language & Compiler
• “indirect” enum elements are not implemented yet in this beta, they will be added to a later update.
• A miscompilation or compiler crash may occur when a class inherits an instance of a generic class, overrides
its methods, and the overridden method is invoked on the subclass. (20874966)
For example:
class GenericSuper {
func foo() -> T? {
return nil }
}
class GenericSub: GenericSuper {
override func foo() -> Int? {
return 6502 }
}
func foo() {
GenericSub().foo() // miscompiles
}
Workaround: Mark the override as final if appropriate, or coerce the object to the generic superclass before invoking the method.
func foo() {
(GenericSub() as GenericSuper).foo() // OK
}
© 2015 Apple Inc. All Rights Reserved.
• When extending a Core Foundation type to conform to a protocol, checked casts to the protocol type will fail at runtime in optimized builds. (20882882)
For example:
extension CFSet: Fooable {
func foo() { print("CFSet") }
}
import Foundation
protocol Fooable {
func foo() }
func fooify(x: T) {
if let foo = x as? Fooable {
foo.foo()
} else {
print("not fooable")
}
}
fooify(CFSetCreate(...))
Workaround: If the Core Foundation type has a toll-free-bridged Objective-C equivalent, extend the Objective-C class to conform to the protocol instead of the Core Foundation type.
• Classes that conform to ErrorType will cause a runtime crash if you try to bridge them to NSError in a catch clause. (21116814)
For example:
class MyError: ErrorType {
let _domain = “”; let _code = 0
}
do {
throw MyError()
} catch let error as NSError {
print(error.description)
}
Workaround: Use enums to conform to ErrorType instead of classes or make your error classes inherit from NSError instead of conforming to ErrorType.
• The guard statement does not bind variable names properly at the top level of a playground, script file, or in main.swift. (21110580)
• Several global generic functions in the standard library have not yet been moved to be methods.
• Class-constrained protocol types will cause the compiler to crash or emit invalid code if the protocol type is
bound to a generic parameter that conforms to AnyObject. (18378390)
For example:
© 2015 Apple Inc. All Rights Reserved.
 func foo(x: T, y: T) {}
protocol CP: class {}
class C: CP {}
class D: CP {}
let x: CP = C(), y: CP = D()
foo(x, y) // T == CP, causes crash
Workaround: If possible, use the AnyObject type instead of the generic constraint: func foo(x: AnyObject, y: AnyObject) {}
or make the protocol @objc:
@objc protocol CP {}
• The compiler may fail to parse a throwing function type in a generic parameter list. (21254633) For example:
let array = Array ()>(count: 1, repeatedValue: {})
Workaround: Declare the function type in a typealias:
typealias MyCallback = () throws -> ()
let array = Array(count: 1, repeatedValue: {})
© 2015 Apple Inc. All Rights Reserved.

Скриншоты



Скриншоты окна About

[only-soft.org].t26639.torrent
Торрент: Зарегистрирован   [ 2015-06-10 04:00 ]

96 KB

Статус: проверено
Скачан: 0 раз
Размер: 9,59 GB
Оценка: 
(Голосов: 0)
Поблагодарили: 0  Спасибо
[RUS] OS X 10.11 El Capitan (15A178w) + Xcode 7 beta [PRE-RELEASE] [Intel] скачать торрент бесплатно и без регистрации
[Профиль] [ЛС]
Форум Тема Автор Размер
Mac OS (для Macintosh) [RUS] OS X 10.10 Golden Master Candidate 1.[Intel] [Demo] iPhone 12,4 GB
Mac OS (для РС-Хакинтош) [RUS] OS X 10.10.3 [Установленная система, для HP 450 G1] 14D131 [Intel] [K-ed] Скачать Windows 13,99 GB
Mac OS (для РС-Хакинтош) [RUS] OS X Capitan 10.11.2 flah for Win 10.11.2 [Intel] [K-ed] Скачать Windows 5,91 GB
Mac OS (для РС-Хакинтош) [RUS] OS X Capitan 10.11.2 rdr 10.11.2 [Intel] [K-ed] Скачать Windows 6,05 GB
Mac OS (для РС-Хакинтош) [RUS] OS X El Capitan 10.11.1 (15B42) [Intel] (Флешка для установки) MBR. 10.11.1 (15B42) [Intel] [Demo] Скачать Windows 6,38 GB
Mac OS (для РС-Хакинтош) [RUS] OS X El Capitan 10.11.2 for win 10.11.2 [Intel] [K-ed] Скачать Windows 7,47 GB
Mac OS (для РС-Хакинтош) [RUS] OS X El Capitan 10.11.6 (15G31) [Intel] (Образ флэшки) Legacy 10.11.6 (15G31) [Intel] [Demo] Скачать Windows 7,33 GB
Mac OS (для РС-Хакинтош) [RUS] OS X El Capitan 10.11.6 [Intel] [Demo] Скачать Windows 7,23 GB
Показать сообщения:    
Ответить на тему

Текущее время: Сегодня, в 09:38

Часовой пояс: GMT + 4



Вы не можете начинать темы
Вы не можете отвечать на сообщения
Вы не можете редактировать свои сообщения
Вы не можете удалять свои сообщения
Вы не можете голосовать в опросах
Вы не можете прикреплять файлы к сообщениям
Вы можете скачивать файлы