List of known Xcode issues

Feel free to add your comments to this list.

You can do it directly on GitHub, by clicking this link, just don't forget to send it as a Pull Request ;)

Note: mainly affects UI tests.

The root cause of the issue is that Xcode / the iOS Simulator has issues in performance limited environments. This included Virtual Machines (which is how your builds are running on bitrise.io), MacBook Airs, Mac Minis with HDD storage, ...

It can happen even if you use Apple's Xcode Bots CI server on non SSD Mac Mini.


  • UI Tests fail to start
  • One or more UI Test case hangs

Related links & reports:

Possible solutions

Flaky UI tests, UI test cases failing randomly

This can happen with a really simple project too. Even something as simple as:

func testAddAnItemGoToDetailsThenDeleteIt() {
        // Use recording to get started writing UI tests.
        // Use XCTAssert and related functions to verify your tests produce the correct results.

        let app = XCUIApplication()
        let masterNavigationBar = app.navigationBars["Master"]

        let tablesQuery = app.tables
        let firstElemQuery = tablesQuery.cells.elementBoundByIndex(0)



        XCTAssert(tablesQuery.cells.count == 0)

can trigger this issue.

Possible solutions

We could reproduce this issue with the code above, using Xcode 7.3. The exact same code worked perfectly with Xcode 7.2.1 while it randomly failed with 7.3. The solution was to use a different iOS Simulator device. The test failed 2 out of 3 on average with the "iPhone 6" simulator device using Xcode 7.3, while it worked perfectly with Xcode 7.2.1.

Changing the simulator device to "iPhone 6s Plus" solved the issue with Xcode 7.3.

Xcode Unit Test fails without any error, with exit code 65

This can be caused by a lot of things, Xcode or some other tool simply omits / does not present any error message.

You can find a long discussion, with possible reasons & solutions here.

A quick summary:

  • First of all, if you use xcpretty to format the output try a build without it (if you use the Xcode Test step you can set xcodebuild as the "Output Tool" option/input to not to format the log produced by xcodebuild). The cause is: xcpretty sometimes omits the error message in it's output. Related GitHub issue.
  • If you don't use our Xcode Test step to run your UI Test you should try to run it with our Xcode Test step. We always try to improve the reliability of the step, implementing known workarounds for common issues.
  • If you use our Xcode Test step: make sure you use the latest version, as it might include additional workarounds / fixes.
  • Try another Xcode version, there are issues which are present in one Xcode version but not in another one.
  • Make sure your desired Xcode scheme is shared. Don't forget to commit and push the changes if you just enabled it.
  • It might also be a project configuration issue in your Xcode project, or a code issue in your tests, or a multi threading issue in your code.
  • We received reports that this might also be caused by Code Coverage report generation, you can disable the Generate code coverage files? option of the Xcode Test step to not to generate Code Coverage files.
  • If the previous steps did not help, you should check the whole discussion and suggested solutions at: https://github.com/bitrise-io/bitrise.io/issues/5

Segmentation fault

The error is:

clang: error: unable to execute command: Segmentation fault: 11

This is usually due to Xcode version mismatch - that you use a different Xcode on your Mac than the one you use on bitrise.io. Commonly occurs with Xcode 7.2 (if you have the Xcode 7.2 stack selected on bitrise.io), if you're already on a newer version of Xcode locally on your Mac.

The solution is simple, just make sure that you use the same Xcode version everywhere.

Issues which occur with the Xcode Command Line Tools (xcodebuild), but not with Xcode.app

xcodebuild hangs when a test causes EXC_BAD_ACCESS kernel exception

xcodebuild hangs when a test causes EXC_BAD_ACCESS kernel exception

Note: this can happen only on specific iOS Simulators / iOS versions too, e.g. if the app only crashes on iOS 8, but not on iOS 9

Xcode 8 - xcodebuild .. test hangs at the very end of the tests

xcodebuild .. test hangs at the end of the tests (after it printed the summary of the tests) if the output of xcodebuild .. is piped / redirected in any way. This means that xcodebuild .. test .. | xcpretty or even tee can be used to reproduce this issue.

  • Affected Xcode versions: so far it seems to be an Xcode 8 beta only issue, and it was fixed in Xcode 8 beta 4.
  • Related radar and xcpretty issues.
  • Workaround: use a Script step instead of the Xcode Test step, and copy paste the xcodebuild command from the hanging Xcode Test step's log, without | xcpretty etc. Of course, with this you won't be able to use the built in features the Xcode Test step provides, but the base xcodebuild command should be able to run, if the output is not redirected / piped.

Every/Any Xcode command hangs

This is a rare issue, caused by running a non shared Scheme.

xcodebuild can only work with shared Schemes and user schemes (auto created by Xcode.app). xcodebuild, unlike Xcode.app, does not auto create user schemes, it can only work with shared schemes and already existing user schemes (Xcode.app creates the user scheme when you open the project in Xcode.app on the specific Mac machine the first time, for schemes which are not marked as shared). If you try to run a command on a missing / non shared Scheme it usually manifests in a "scheme not found" error, but we saw projects where it resulted in xcodebuild hanging, instead of an error message.

If this is the case then any xcodebuild command will hang, even something as simple as xcodebuild -list.


Make sure that you marked the Scheme as shared, and that you actually committed & pushed it into your repository.

Build hangs

Simulator reset

As reported here, if you do a simulator reset during the build, e.g. with a pre-action Build Phase Script xcrun simctl erase all, it can cause Xcode / the Simulator to hang.


It might also not be Xcode related, but might be caused by something in your project when it runs in an Xcode step (Xcode Test, Xcode Archive, ...). For example if you have a Run Phase Script in your Xcode project, that will run during Xcode build/test/archive, and that script hangs for some reason (e.g. it waits for a user input).

You can find pointers to identify and solve these kind of issues on our old DevCenter.