NSFail

XCUI testing presently requires relaunching the application for every single test in a suite rather than once per suite. This is a giant pain for applications with larger UI hierarchies.

If I need to test a screen that is displayed to the user after I’ve registered and added a credit card but before I get into my main application, I have to go through getting to the registration page, filling out the registration form, filling out the credit card form just to get to the screen I need to test for every. single. test.

This exponentially increases how long each test takes to run, and makes it impossible to test multiple things which share similar state without just resorting to convenience methods and manual cleanup rather than individual tests.

I'm currently porting a kind of bigger UI-test from KIF (https://github.com/kif-framework/KIF) to Xcodes UI testing (it will take about an half an hour to finish). It seems like that the test is not able to finish, as the RAM gets eaten up by the UI testing process. In the attached zip is a project that contains a UI-test. When you start it and observe the memory-consumption, you will see that it is steadily growing. In a bigger app like ours, it grows much faster. I also attached a trace-run i made with instruments of the attached project and some screenshots of the memory-consumption that Xcode showed to me.

Expected Results: I expect to be able to <cmd>+highlight or <cmd>+<a> or <shift>+click or <cmd>+click items from the Get Info window and paste the contents into any other application.

Actual Results: Only one row is highlighted at a time and then it's not even copyable at that. Useless this new Disk Utility.app is compared to the previous incarnation.

SVG is becoming more widely used throughout OS X. For example, it’s used as the format for the new icons on pinned tabs in Safari.

These graphics can be viewed in Safari, but that makes it hard to see when there is transparency (which is important when the graphic is used as a mask as in the example above.) Using QuickLook to preview the graphic also defaults to a white background.

If you drop a SVG file on the Preview icon in the Dock, nothing happens. It would be great if the file was opened and displayed like a PNG or any other common web graphic that supports transparency.

Disk Utility.app in El Capitan should support multiple windows like previous versions of Disk Utility so that parallel operations can be conducted.

Steps to Reproduce: 1. Open Disk Utility 2. Initiate a long-running disk operation, such as a zero write format 3. While the long-running disk operation is active, try to do another operation on a different hard drive.

UIAlertAction’s init method takes a String? for “title” in Swift, but the documentation states “This parameter must not be nil”

The new disk utility in 10.11 does not allow the creation of two partitions on one drive anymore as the previous versions did.

Steps to Reproduce: 1. Open disk utility 2. Try to create a second partition

Expected Results: Not having to use the CLI to create two partitions on one drive as it was possible in the legacy disk utility before 10.11.

When an Objective-C protocol is extended by a Swift protocol, the class does not properly conform to the parent protocol. This is language independent.

Steps to Reproduce: 1. Create a Swift protocol 2. Make that Swift protocol extend an Objective-C protocol 3. Implement a class that conforms to the Swift protocol 4. Check conformance to the Objective-C protocol

Expected Results: The model (or class) conforms to the protocol.

Actual Results: The model does not conform to the protocol. This fails using Swift’s `is` and `as` operators, as well as `conformsToProtocol:` in Objective-C.

The Disk Utility App in El Capitan is practically useless. It is less user friendly and less functional. It is a major step back from previous versions of Disk Utility in OS X.

Steps to Reproduce: Example: 1. Attach a disk with an encrypted JHFS+ filesystem * Close the auto-prompt for password if asked 2. Open Disk Utility and try to mount the encrypted volume

Expected Results: I expect it to be easy to mount this volume. The "unlock" function should be in the toolbar by default when applicable. I expect there to be a right-click context menu to allow the appropriate actions when I right-click on a drive or volume.

Actual Results: The application is pure useless. I might as well throw OS X UI away and do everything from the command line from the start.

The -Swift-h file in a mixed project does not update to include an edited version of a Swift initializer (even after a clear of derived data.)

Steps to Reproduce: 1. Have a project with Swift and ObjC 2. Create a class in Swift with a initializer 3. Create an instance of the class in ObjC using the initializer 4. Change the parameter list in the Swift file 5. Use the new argument list in ObjC. - Cannot find initializer with new parameter 6. Look in -Swift.h to see what initializers are available. 7. Old initializer is still there. 8. Wipe derived data to force a rebuild of the -Swift.h file 9. Now class has no initializer in the -Swift.h file

The Swift language supports many of the principles of functional programming, such as higher-order functions, immutable values, and pattern matching.  One gap in the functional support is for conditional expressions.  

Swift includes the ternary “? :” operator from C, but that operator does not support the “if let” test with binding that is so useful.  Swift only allows “if” or “if let” in a statement, not an expression.  Likewise, Swift only supports “switch” in a statement.

I propose adding syntax to Swift that allows conditional expressions with the full binding support of “if” and “let”.  As a strawman, the syntax could look like the following:

let result = (if let myValue = someOptional {myValue.calculateSomething()}              else {calculateSomethingElse()})

let result = (switch someEnum {    case let .Success(value): .Some(value)    case let .Error(error): nil })

I expect to be able to change the section insets when configuring a collection view contained in a storyboard. But IB does not let me.

Steps to Reproduce: 1. Open the attached demo project 2. Open the Main.storyboard in IB 3. Navigate to the collection view flow layout 4. To the the inspector tab with the ruler icon 5. Try to modify Top, Bottom, Left or Right Section Insets

Expected Results: You should be able to change the section inset values

Actual Results: You cannot change the section inset values

As described in http://qualitycoding.org/app-delegate-for-tests/, I have main() test for the presence of a test-specific application delegate. This is important for bypassing the regular app delegate during testing. This technique fails in Xcode 7 beta 4, presumably because the test bundle is being injected too late.

(still true in Xcode 7.0.1)

With third party applications sending push notifications with a quick reply field the keyboard does not activate then the phone is locked.

I have reproduced the same with Telegram messenger.

Steps to Reproduce: 1. Ensure the phone is locked 2. Receive a push notification from a third party app with a quick reply field 3. Use the quick-reply feature to reply to the notification

Expected Results: The keyboard pops up with the notification

Actual Results: The reply screen pops up, but no keyboard is displayed.

Our app with 62 dynamic frameworks (73 binaries when including libSwift* and the app itself) suddenly takes 3-4 seconds to load on iOS 8 and 9.

Here our observations: - Whenever we hit "pause" in the debugger during app start, we end up in ImageLoaderMachO::loadCodeSignature -> fcntl - Device log is spammed with entries like this: amfid[…] <Error>: SecTrustEvaluate [leaf IssuerCommonName SubjectCommonName] -> 73 times - surprise! - Subsequent app starts are a lot faster. Obviously something is cached. The device log also no longer shows the entries above on app start. - Few app starts later the cache seems to be purged. The app starts slow again, spams a lot in the device log and hangs in ImageLoaderMachO::loadCodeSignature most of the time.

While iOS devices are updated through OTA channel can sync with iTunes 11.4 (which is the last available version of iTunes for Snow Leopard) and iTunes 12.2.3 (which is the last available version of iTunes for Lion), devices that are updated through iTunes does not sync with these iTunes versions.

This makes no sense to the users. If iOS 9, updated through OTA, is perfectly compatible with iTunes 11.4 and 12.2.3, means iOS 9 is compatible with iTunes 11.4 and 12.2.3. The arbitrary limitation (or bug) feels strange and counter-intuitive.

[…]

Please treat iOS 9 devices, whether updated through OTA or iTunes, equally in terms of syncing.

When I am in two teams and have developer profiles for both teams installed, then my unit tests are not compiling anymore. The error "iPhone Developer: ambiguous (matches "iPhone Developer: Max M. (TeamA ID) and "iPhone Developer: Max M. (TeamB ID))" is shown.

As code signing identity for the unit test I selected "iOS Developer".

Expected Results: In the same way Xcode is able to select the right developer profile for building apps it should be able to select the right developer profile for building unit tests.