-
Notifications
You must be signed in to change notification settings - Fork 737
Support for Xcode 7 #528
Comments
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. |
I have landed experimental support of Xcode 7 beta on master! |
It worked for me thank you! |
Anything stopping this from getting released? |
@schwa please use master for now. I am not sure when we will make new release. |
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.
|
Tried current master, initial issue is gone, but I'm having a crash during test run:
|
hey, @ExtremeMan, I'm hitting the same issue as @Corristo. Any pointers? |
so, I investigated for a while and I'm pretty sure this is caused by I've run What brought me to my conclusion is that changing
I have no idea how the resolve this issue. |
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? |
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.
In addition, we also tried setting |
Could any of you try rebuilding xctool with Xcode 7 and then running it? I am wondering if it could be a problem. |
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
Here is the stack trace from the crash report:
From this callstack, it seems that building xctool with Xcode7 beta 6 does help get past line 209 here: and then crashes on line 219 here |
So the crash is in |
re: xcode7 xctool not able to find XCTest:
Compare this against v0.2.5 binary distribution presumably built with xcode6:
This line is in xcode7beta6 built xctool, not in xcode6:
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:
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 :( |
I can also confirm that recompiling xctool with Xcode 7 b6 does fix the |
Thanks for confirming. FYI: |
Interestingly, it doesn't in my case! My full xctool invocation is
which does crash in xctool. Replacing it with:
does make them run without any (apparent) problem. I suspect the inner workings of |
same as @jklausa - xcodebuild for xc7b6 does NOT crash with that assert, with same arguments as xctool.
And test runs are affected- since there is a Segmentation fault: 11, tests won't run against ios9 using xctool :( |
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. |
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. |
I've looked into it. Here are the details of what I've found.
Workaround if next release of Xcode 7 doesn't fix it: swizzle |
Have we filed a radar? |
Radar filed: 22542632. |
Xcode 6 -> 7 transition fixed in 70b5e53. Now binary built with Xcode 6 is usable under Xcode 7. |
Would this fix this error I'm getting with xctool 0.2.5 w/ Xcode 7b6 when running tests (which compile fine):
|
No. |
Upgraded the test project. Rolled back part of 69cf6ed to work around facebookarchive/xctool#528.
@connork26 latest xctool master should support Xcode 7 GM. I need to make a new release so it is available via homebrew. |
I am not looking into Xcode 7.1 beta currently. I will wait for GM before doing that. |
Upgraded the test project. Rolled back part of 69cf6ed to work around facebookarchive/xctool#528.
since Xcode 7 GM support is not officially released on Homebrew—yet. facebookarchive/xctool#528
Is it the same issue? |
@ExtremeMan when do you think the new release will be available? |
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. |
See Travis CI fix for example: lazytype/FingerTree@6cdd45a. Thanks @lazytype for a finding =) |
I put in the line to remove and install xctool --HEAD but now it just stalls at the run tests step. (on CircleCI) |
@szweier I have tests running successfully on CircleCI using the following circle.yml:
|
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: |
It seems that |
Made a new release: Homebrew/legacy-homebrew#44090. |
Seems
Xcode 7.0 (7A220) |
I will need a sample otherwise I don't know where to look at =/ |
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. |
Upgraded the test project. Rolled back part of 69cf6ed to work around facebookarchive/xctool#528.
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.
The text was updated successfully, but these errors were encountered: