Support for Xcode 7

[Neil3079]

Running tests for project built with the latest xcode yields the following error

Unable to read build settings for target 'UITestingCucumberExampleProjectTests'. It's likely that the scheme references a non-existent target

I can build the tests fine just not run them, testing using xcodebuild test does work however.

[ExtremeMan]

I am working on this. I have bunch of commits that will add support of Xcode 7. I will keep this issue open until Xcode 7 is released. Also I will post updates here.

[ExtremeMan]

I have landed experimental support of Xcode 7 beta on master!

[Neil3079]

It worked for me thank you!

[schwa]

Anything stopping this from getting released?

[ExtremeMan]

@schwa please use master for now. I am not sure when we will make new release.

[brendanjc]

I pulled the latest from master after hitting the same "Unable to read build settings for target" issue above. Now I'm seeing something slightly different, see below. This is on Xcode 7 Beta 5. Vanilla 'xcodebuild test' still works for me.

=== RUN-TESTS ===

  [Info] Collecting info for testables... (1317 ms)
  run-test AppTests.xctest (iphonesimulator9.0, iPad Air 2, application-test)
    [Info] Installed 'APP.ID'. (1296 ms)
    [Info] Launching test host and running tests ... (0 ms)
2015-08-10 16:25:58.304 xctool[8012:59460] [MT] DVTAssertions: Warning in /Library/Caches/com.apple.xbs/Sources/DVTFrameworks/DVTFrameworks-8176.5/DVTFoundation/PlugInArchitecture/PlugInManager/DVTPlugInManager.m:257
Details:  Requested but did not find extension point with identifier Xcode.DVTFoundation.DevicePlatformMapping
Object:   <DVTPlugInManager: 0x7fc4cc841bb0>
Method:   -extensionPointWithIdentifier:
Thread:   <NSThread: 0x7fc4cb422760>{number = 1, name = main}
Please file a bug at http://bugreport.apple.com with this warning message and any useful information you can provide.

[nikolaykasyanov]

Tried current master, initial issue is gone, but I'm having a crash during test run:

2015-08-10 18:48:31.948 xctool[11311:1946874] *** Assertion failure in -[OCUnitIOSAppTestRunner testEnvironmentWithSpecifiedTestConfiguration], /tmp/xctool20150810-10639-jw4a5r/xctool/xctool/OCUnitTestRunner.m:333

2015-08-10 18:48:32.084 xctool[11311:1946874] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'XCTestConfiguration isn't available'
*** First throw call stack:
(
    0   CoreFoundation                      0x00007fff8c0cf03c __exceptionPreprocess + 172
    1   libobjc.A.dylib                     0x00007fff9840e76e objc_exception_throw + 43
    2   CoreFoundation                      0x00007fff8c0cee1a +[NSException raise:format:arguments:] + 106
    3   Foundation                          0x00007fff95f2c8cb -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 195
    4   xctool                              0x000000010e445e1f -[OCUnitTestRunner testEnvironmentWithSpecifiedTestConfiguration] + 204
    5   xctool                              0x000000010e443496 -[OCUnitIOSAppTestRunner runTestsAndFeedOutputTo:startupError:otherErrors:] + 1654
    6   xctool                              0x000000010e444f4d -[OCUnitTestRunner runTests] + 195
    7   xctool                              0x000000010e45293e __158-[RunTestsAction blockForTestable:focusedTestCases:allTestCases:testableExecutionInfo:testableTarget:isApplicationTest:arguments:environment:testRunnerClass:]_block_invoke + 311
    8   xctool                              0x000000010e454691 __56-[RunTestsAction runTestables:options:xcodeSubjectInfo:]_block_invoke404 + 336
    9   xctool                              0x000000010e453dc7 -[RunTestsAction runTestables:options:xcodeSubjectInfo:] + 4998
    10  xctool                              0x000000010e451e12 -[RunTestsAction performActionWithOptions:xcodeSubjectInfo:] + 1234
    11  xctool                              0x000000010e4666e3 -[TestAction performActionWithOptions:xcodeSubjectInfo:] + 106
    12  xctool                              0x000000010e43db6d -[XCTool run] + 3334
    13  xctool                              0x000000010e43c49c main + 1064
    14  xctool                              0x000000010e439464 start + 52
    15  ???                                 0x0000000000000010 0x0 + 16
)
libc++abi.dylib: terminating with uncaught exception of type NSException

[jklausa]

hey, @ExtremeMan, I'm hitting the same issue as @Corristo. Any pointers?

[jklausa]

so, I investigated for a while and I'm pretty sure this is caused by XCTest for some reason not being linked.

I've run class-dump on Xcode 7 b5, and the XCTestConfiguration is (obviously!) still there.

What brought me to my conclusion is that changing OTHER_LDFLAGS_7000 from $(OTHER_LDFLAGS_0600) -weak_framework XCTest, to not use weak linking, causes xctool to die on startup, with following error:

dyld: Library not loaded: @rpath/XCTest.framework/Versions/A/XCTest
  Referenced from: /Users/klausa/Library/Developer/Xcode/DerivedData/xctool-cqcudzllhwydmxcruxwlgnvaihrn/Build/Products/Debug/xctool
  Reason: image not found

I have no idea how the resolve this issue.

[ExtremeMan]

to not use weak linking, causes xctool to die on startup, with following error

This is expected. We can't hardlink because Xcode location could be changed after xctool is built. That is why we are updating fallback framework paths on xctool start up: https://github.com/facebook/xctool/blob/master/xctool/xctool/main.m#L66.

Do you mind debugging if the path with XCTest framework was correctly listed there?

[rlucero-okta]

We are also having similar problems with xctool 0.2.5. When you only have XCode 7 Beta 6 and specify the DEVELOPER_DIR to `/Applications/Xcode-beta.app/Contents/Developer/, this command causes a similar exception.

*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'XCTestConfiguration isn't available'

In addition, we also tried setting DYLD_FALLBACK_FRAMEWORK_PATH to point to /Applications/Xcode-beta.app/Contents/Developer//Platforms/MacOSX.platform/Developer/Library/Frameworks.

[ExtremeMan]

Could any of you try rebuilding xctool with Xcode 7 and then running it? I am wondering if it could be a problem.

[marcpowell-okta]

Seeing same issue as @rlucero-okta above with same error.

I rebuilt xctool with Xcode 7 beta 6 on OS X 10.10.5 with source from git clone frm latest commit 5557108
After building using xctool.sh and cp'ing the lib/libexec/reporters/bin directories, I have run into a different crash

$ xctool --version
0.2.6
$ xctool -workspace 'MyApp.xcworkspace' -scheme Debug -sdk iphonesimulator -destination "platform=iOS Simulator,name=iPad 2,OS=latest" test
// ...
  [Info] Collecting info for testables... (2257 ms)
  run-test MyAppTests.xctest (iphonesimulator9.0, iPad 2, application-test)
    [Info] Installed 'com.mytest.app'. (3716 ms)
    [Info] Launching test host and running tests ... (0 ms)
2015-08-26 12:07:53.788 xctool[72000:641311] [MT] DVTAssertions: Warning in /Library/Caches/com.apple.xbs/Sources/DVTFrameworks/DVTFrameworks-8194.5/DVTFoundation/PlugInArchitecture/PlugInManager/DVTPlugInManager.m:257
Details:  Requested but did not find extension point with identifier Xcode.DVTFoundation.DevicePlatformMapping
Object:   <DVTPlugInManager: 0x7f965bf24450>
Method:   -extensionPointWithIdentifier:
Thread:   <NSThread: 0x7f965bc22830>{number = 1, name = main}
Please file a bug at http://bugreport.apple.com with this warning message and any useful information you can provide.

Segmentation fault: 11

Here is the stack trace from the crash report:

Process:               xctool [72000]
Path:                  /usr/local/xctool-latest/bin/xctool
Identifier:            xctool
Version:               ???
Code Type:             X86-64 (Native)
Parent Process:        bash [37972]
Responsible:           iTerm [785]
User ID:               504

Date/Time:             2015-08-26 12:07:53.810 -0700
OS Version:            Mac OS X 10.10.5 (14F27)
Report Version:        11
Anonymous UUID:        5CC1C60D-6822-730B-9B6B-1184B5DC8928

Sleep/Wake UUID:       C5AD520D-A764-4D17-895D-70C3F7D0049E

Time Awake Since Boot: 78000 seconds
Time Since Wake:       950 seconds

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000050

VM Regions Near 0x50:
--> 
    __TEXT                 0000000100115000-0000000100172000 [  372K] r-x/rwx SM=COW  /usr/local/xctool-latest/bin/xctool

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libdispatch.dylib               0x00007fff97db77c0 dispatch_async + 63
1   com.apple.dt.DVTFoundation      0x0000000100425016 DVTDispatchAsync + 153
2   com.apple.dt.DVTFoundation      0x0000000100424e76 DVTAsyncPerformBlock + 55
3   com.apple.DVTiPhoneSimulatorRemoteClient    0x0000000100887668 -[SimDevice(DVTAdditions) dvt_notifyOfBootOnQueue:handler:] + 502
4   com.apple.DVTiPhoneSimulatorRemoteClient    0x0000000100885498 __62-[DTiPhoneSimulatorSession _startSessionInSimulatorWithError:]_block_invoke + 126
5   com.apple.dt.DVTFoundation      0x0000000100387bde -[DVTFuture initWithBlock:] + 107
6   com.apple.dt.DVTFoundation      0x0000000100387571 +[DVTFuture futureWithBlock:] + 57
7   com.apple.DVTiPhoneSimulatorRemoteClient    0x0000000100884d20 -[DTiPhoneSimulatorSession _startSessionInSimulatorWithError:] + 688
8   com.apple.DVTiPhoneSimulatorRemoteClient    0x00000001008842f5 __65-[DTiPhoneSimulatorSession requestStartWithConfig:timeout:error:]_block_invoke67 + 109
9   com.apple.dt.DVTFoundation      0x00000001003c2bf0 -[_DVTNotificationReceiver receiveNotification:] + 815
10  com.apple.CoreFoundation        0x00007fff88c7a45c __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
11  com.apple.CoreFoundation        0x00007fff88c37f8e ____CFXNotificationPostToken_block_invoke + 142
12  com.apple.CoreFoundation        0x00007fff88bda8ec __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 12
13  com.apple.CoreFoundation        0x00007fff88bcc9f5 __CFRunLoopDoBlocks + 341
14  com.apple.CoreFoundation        0x00007fff88bcc536 __CFRunLoopRun + 1814
15  com.apple.CoreFoundation        0x00007fff88bcbbd8 CFRunLoopRunSpecific + 296
16  com.apple.CoreFoundation        0x00007fff88c83671 CFRunLoopRun + 97
17  xctool                          0x0000000100125874 -[SimulatorLauncher launchAndWaitForExit] + 178
18  xctool                          0x0000000100133c6e +[SimulatorWrapper runHostAppTests:simulatorInfo:appLaunchArgs:appLaunchEnvironment:feedOutputToBlock:error:] + 459
19  xctool                          0x0000000100121554 -[OCUnitIOSAppTestRunner runTestsAndFeedOutputTo:startupError:otherErrors:] + 2256
20  xctool                          0x0000000100122f7e -[OCUnitTestRunner runTests] + 209
21  xctool                          0x0000000100130b98 __158-[RunTestsAction blockForTestable:focusedTestCases:allTestCases:testableExecutionInfo:testableTarget:isApplicationTest:arguments:environment:testRunnerClass:]_block_invoke + 311
22  xctool                          0x00000001001328ee __56-[RunTestsAction runTestables:options:xcodeSubjectInfo:]_block_invoke406 + 336
23  xctool                          0x000000010013202e -[RunTestsAction runTestables:options:xcodeSubjectInfo:] + 5030
24  xctool                          0x0000000100130042 -[RunTestsAction performActionWithOptions:xcodeSubjectInfo:] + 1211
25  xctool                          0x0000000100145294 -[TestAction performActionWithOptions:xcodeSubjectInfo:] + 106
26  xctool                          0x000000010011b46c -[XCTool run] + 3316
27  xctool                          0x0000000100119db2 main + 1064
28  xctool                          0x0000000100116a64 start + 52

From this callstack, it seems that building xctool with Xcode7 beta 6 does help get past line 209 here:
https://github.com/facebook/xctool/blob/master/xctool/xctool/OCUnitIOSAppTestRunner.m#L209
eg the call to testEnvironmentWithSpecifiedTestConfiguration

and then crashes on line 219 here
https://github.com/facebook/xctool/blob/master/xctool/xctool/OCUnitIOSAppTestRunner.m#L219
with the call to runHostAppTests:simulatorInfo:appLaunchArgs:appLaunchEnvironment:feedOutputToBlock:error:

[ExtremeMan]

So the crash is in DVTiPhoneSimulatorRemoteClient framework. I think I hit it once as well. It could be an Xcode bug, could be a bug in xctool.

[marcpowell-okta]

re: xcode7 xctool not able to find XCTest:
compiling with xcode7beta6 shows this shared library output:

$ otool -L /usr/local/bin/xctool
    @rpath/DVTFoundation.framework/Versions/A/DVTFoundation (compatibility version 1.0.0, current version 1.0.0)
    @rpath/DVTiPhoneSimulatorRemoteClient.framework/Versions/A/DVTiPhoneSimulatorRemoteClient (compatibility version 1.0.0, current version 12.0.0)
    @rpath/CoreSimulator.framework/Versions/A/CoreSimulator (compatibility version 1.0.0, current version 179.0.0)
    @rpath/XCTest.framework/Versions/A/XCTest (compatibility version 1.0.0, current version 8170.3.0)
    /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit (compatibility version 45.0.0, current version 1391.12.0)
    /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore (compatibility version 1.2.0, current version 1.11.0)
    /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation (compatibility version 300.0.0, current version 1229.0.0)
    /usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 228.0.0)
    /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 120.1.0)
    /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1225.0.0)
    /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1229.11.0)

Compare this against v0.2.5 binary distribution presumably built with xcode6:

$ otool -L /usr/local/xctool-v0.2.5/bin/xctool
/usr/local/xctool-v0.2.5/bin/xctool:
    @rpath/DVTFoundation.framework/Versions/A/DVTFoundation (compatibility version 1.0.0, current version 1.0.0)
    @rpath/DVTiPhoneSimulatorRemoteClient.framework/Versions/A/DVTiPhoneSimulatorRemoteClient (compatibility version 1.0.0, current version 12.0.0)
    @rpath/CoreSimulator.framework/Versions/A/CoreSimulator (compatibility version 1.0.0, current version 117.15.0)
    /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit (compatibility version 45.0.0, current version 1347.57.0)
    /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore (compatibility version 1.2.0, current version 1.10.0)
    /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation (compatibility version 300.0.0, current version 1153.20.0)
    /usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 228.0.0)
    /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 120.0.0)
    /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1213.0.0)
    /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1153.18.0)

This line is in xcode7beta6 built xctool, not in xcode6:

    @rpath/XCTest.framework/Versions/A/XCTest (compatibility version 1.0.0, current version 8170.3.0)

so presumably you could just add that rpath-derived shared library to xctool to work around the missing XCTestConfiguration symbol.

Update: I patched v0.2.5 of xctool using optool from https://github.com/alexzielenski/optool/releases to point to xcode7 beta 6's XCTest framework:

# install load command for missing dylib 
$ ./optool install -c load -p @rpath/XCTest.framework/Versions/A/XCTest -t /usr/local/bin/xctool

# install rpath pointing to Xcode7 beta 6
$ install_name_tool -add_rpath /Applications//Xcode-beta.app/Contents/Developer/Platforms/MacOSX.platform/Developer/Library/Frameworks/ /usr/local/bin/xctool

This fixes the 'NSInternalInconsistencyException', reason: 'XCTestConfiguration isn't available' issue for xctool v0.2.5 but still results in the same xcode assert in DVTPlugInManager as described above in the xcode7b6-compiled version of xctool.

currently xctool is unusable on Xcode7 beta 6 :(

[jklausa]

I can also confirm that recompiling xctool with Xcode 7 b6 does fix the XCTestConfiguration and I've also run into the Requested but did not find extension point with identifier Xcode.DVTFoundation.DevicePlatformMapping issue.

[ExtremeMan]

Thanks for confirming.

FYI: Requested but did not find extension point with identifier Xcode.DVTFoundation.DevicePlatformMapping is an Xcode bug, not xctool. And it doesn't affect test runs. If you run xcodebuild you will see the same "assert" fired.

[jklausa]

Interestingly, it doesn't in my case!

My full xctool invocation is

xctool -workspace "./script/../Clue.xcworkspace" -scheme "Clue Screenshots" -sdk iphonesimulator -destination 'name=iPhone 6 Plus,OS=9.0' run-tests

which does crash in xctool. Replacing it with:

xcodebuild -workspace "./script/../Clue.xcworkspace" -scheme "Clue Screenshots" -sdk iphonesimulator -destination 'name=iPhone 6 Plus,OS=9.0' test

does make them run without any (apparent) problem.

I suspect the inner workings of xcodebuild test might've changed?

[marcpowell-okta]

same as @jklausa - xcodebuild for xc7b6 does NOT crash with that assert, with same arguments as xctool.

# works:
$ xcodebuild -workspace 'MyApp.xcworkspace' -scheme Debug -sdk iphonesimulator -destination "platform=iOS Simulator,name=iPad 2,OS=latest" test

# crashes:
$ xctool -workspace 'MyApp.xcworkspace' -scheme Debug -sdk iphonesimulator -destination "platform=iOS Simulator,name=iPad 2,OS=latest" test

And test runs are affected- since there is a Segmentation fault: 11, tests won't run against ios9 using xctool :(

[ExtremeMan]

Well, Xcode 7 support is in beta. We don't have resources to support all betas, unfortunately, and it definitely worked with previous betas. I will be waiting for next releases since Apple is always changing something. Feel free to hack xctool meanwhile. I will be happy to review PR.

[marcpowell-okta]

Okay good to know- currently the workaround for xcode7b6 is to just use xcodebuild instead of xctool. Glad to know this works in previous betas! Thanks for investigating- I will file a radar for Apple.

[ExtremeMan]

I've looked into it. Here are the details of what I've found.

• -[SimDevice dvt_notifyOfBootOnQueue:queue handler:handler] calls DVTAsyncPerformBlock(queue, handler) if device state is "booted". Since xctool pre-opens Simulator app the device state is always "booted" here.
• -[DTiPhoneSimulatorSession _startSessionInSimulatorWithError:]_block_invoke calls [device dvt_notifyOfBootOnQueue:0x0 handler:__NSConcreteStackBlock];. So hardcoded nil queue is passed.
• DVTAsyncPerformBlock/DVTDispatchAsync invokes dispatch_async(queue, handler). Ooops. We can't pass nil as a queue to dispatch_async. Crash.

Workaround if next release of Xcode 7 doesn't fix it: swizzle -[SimDevice dvt_notifyOfBootOnQueue:handler:] and pass dispatch_get_main_queue() if queue is nil (checked locally and it works).

[LegNeato]

Have we filed a radar?

[ExtremeMan]

Radar filed: 22542632.

[ExtremeMan]

Xcode 6 -> 7 transition fixed in 70b5e53. Now binary built with Xcode 6 is usable under Xcode 7.

[williamsjj]

Would this fix this error I'm getting with xctool 0.2.5 w/ Xcode 7b6 when running tests (which compile fine):

  [Info] Collecting info for testables... (3224 ms)
  run-test ExampleAppTests.xctest (iphonesimulator9.0, iPhone 6, application-test)
    [Info] Installed 'com.company.exampleapp'. (3981 ms)
    [Info] Launching test host and running tests ... (0 ms)
2015-09-03 13:29:49.445 xctool[72887:1460212] [MT] DVTAssertions: Warning in /Library/Caches/com.apple.xbs/Sources/DVTFrameworks/DVTFrameworks-8194.5/DVTFoundation/PlugInArchitecture/PlugInManager/DVTPlugInManager.m:257
Details:  Requested but did not find extension point with identifier Xcode.DVTFoundation.DevicePlatformMapping
Object:   <DVTPlugInManager: 0x7fc6b34dbab0>
Method:   -extensionPointWithIdentifier:
Thread:   <NSThread: 0x7fc6b37057a0>{number = 1, name = main}
Please file a bug at http://bugreport.apple.com with this warning message and any useful information you can provide.

[jklausa]

No.

[ExtremeMan]

@connork26 latest xctool master should support Xcode 7 GM. I need to make a new release so it is available via homebrew.

[ExtremeMan]

I am not looking into Xcode 7.1 beta currently. I will wait for GM before doing that.

[tamastimar]

Is it the same issue?
https://forums.developer.apple.com/message/51922

[szweier]

@ExtremeMan when do you think the new release will be available?

[ExtremeMan]

NOTE: We've found a problem in Travis CI - if you just tell it to install xctool --head it doesn't actually install it =( You need to remove xctool and then request installation - it is a workaround for you currently.

@szweier, it is my todo list for today. Cross fingers I actually do that.

[ExtremeMan]

See Travis CI fix for example: lazytype/FingerTree@6cdd45a. Thanks @lazytype for a finding =)

[szweier]

I put in the line to remove and install xctool --HEAD but now it just stalls at the run tests step. (on CircleCI)

[adamsp]

@szweier I have tests running successfully on CircleCI using the following circle.yml:

machine:
  xcode:
    version: "7.0"
  environment:
    XCODE_SCHEME: "[scheme name]"
    # CocoaPods versions greater than 0.34 require
    # your terminal to be using UTF-8 encoding.
    LANG: en_US.UTF-8
dependencies:
  pre:
    - sudo gem install cocoapods --version 0.38.2
    # CocoaPods sometimes has issues using caches
    # between different versions of CocoaPods.
    - pod setup
    - pod install
    - brew uninstall xctool && brew install --HEAD xctool

[King-Wizard]

Basing myself on the @ExtremeMan 's answer above worked for me, using an Xcode 7 project + Swift + iOS 9 + the continuous integration tool available on travis-ci.org:

[ikesyo]

It seems that run-tests does not work: https://travis-ci.org/ikesyo/ReactiveCocoa/builds/80830588

[ExtremeMan]

Made a new release: Homebrew/legacy-homebrew#44090.

[PatrykKaczmarek]

Seems -freshInstall -freshSimulator doesn't resolve the issue:

 [Info] Collecting info for testables... (3648 ms)
  run-test Unit Tests.xctest (iphonesimulator9.0, iPhone 4s, application-test)
    [Info] Verified iOS Simulators... (5 ms)
    [Info] Shut down iOS Simulator... (36 ms)
    [Info] Stopped any existing iOS simulator jobs to get a fresh simulator. (31 ms)
    [Info] Uninstalled 'com.myapp.bundle.identifier' to get a fresh install. (12605 ms)
    [Info] Installing 'com.myapp.bundle.identifier' ...
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
The build has been terminated

Xcode 7.0 (7A220)

[ExtremeMan]

I will need a sample otherwise I don't know where to look at =/

[ExtremeMan]

Closing this issue. Please create separate issues if you have any problems with xctool and Xcode 7. I've pushed several commits on master that should help with xctool being stuck on running app tests. Please, try master before opening new issues.