Xcode 8 beta fails to build #704
Comments
|
Getting the same error in an objective-c framework. Works fine with xcode 7.3.1, but once I switch to 8 I get this: |
|
I am getting no response travis build fails after 10 mins This worked xcode 7.3.1 |
|
Looks like |
xctool isn't yet compatible with Xcode 8: facebookarchive/xctool#704
|
Unfortunately Facebook doesn't have any plans to support xctool in Xcode 8. I will keep you updated if something changes. Sorry, folks. |
Does this mean just right now or even after Xcode 8.0's final release? If latter, is this project somewhat deprecated & we should look for something else to run the tests? |
We haven't decided yet but it would be safer for you to look for something else. May be we will ship Buck with some simple test utility or extend FBSimulatorControl. I am here though if our community wants to actively work on xctool and support future releases of Xcode. |
|
@ExtremeMan Does this mean that facebook is not internally using xctool for running Xcode tests anymore? |
|
@cezheng we use it for Xcode 7 builds. |
|
@ExtremeMan Thanks for the information. Wish facebook will ship an even better tool for Xcode 8 then:) |
|
Thanks for the heads-up, @ExtremeMan. That's too bad, but I appreciate the work that went into it and the opportunity to use it for free all these years. Might I suggest updating the README to mention that |
|
@emaloney, I will update README as soon as we are sure we deprecate it. Also we will move it to Facebook archives if so is decided. |
xctool won't support Xcode 8 facebookarchive/xctool#704
|
To clear up the error message that you're seeing here, in Xcode 8 added "Increased What's happening with |
|
There is still a way to workaround added Xcode restrictions by resigning it. People are going to that to run Xcode plugins and I would expect CI system to do that as well in order to continue using such tools as |
|
@ExtremeMan Can you please give some more details on how that resigning would work? That sounds interesting! |
|
I found all the details here: alcatraz/Alcatraz#475. But I haven't tried myself. |
|
Thank you! |
|
I have some good news to share :) All you need to make xctool work again is use https://github.com/steakknife/unsign to unsign the XCTest binary in /Applications/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/Frameworks/XCTest.framework Then xctool just works @plu @ExtremeMan |
|
@oliverhu without any patches to the tool? What about application tests? |
|
@ExtremeMan it seems you just need to wipe out all the signatures around all dependent dylib/binaries. I also wiped xcodebuild. Prior to wiping: After wiping, all warnings are gone, however, I was celebrating too early, not fully working yet, now I get: |
|
Last one looks fine because it is at least xctool failing, not Xcode tools. Thanks for the info. Probably it is worth investigating further. |
|
Did a bit more research today, was able to launch simulators by removing DTiPhoneSimulatorSystemRoot from dependencies (DTiPhoneSimulatorSystemRoot class is removed in the new SDK :\ by dumping the DTFramework) Got some new errors this time, seems Apple did learn from the Malicious Xcode incident: After disassembling the I guess even if after I have fixed this, something else will pop up... here is my understanding of the shim.dylib, correct me if wrong:
To resolve all these hassle, is that possible that instead of injecting dylibs, we tackle this by IPC with the app, for example, when XCTest is loaded in the app, we sent a distributed_notification/xpc message out and then we swizzle in the xctool side? @ExtremeMan |
|
Yah, I used |
|
I'm using xctool 0.2.10 (from master) and Xcode 8.1 Beta 1 and got this error:
using this command:
anyone with the same problem? |
Also switch from xctool to xcodebuild since xctool isn't supported on Xcode 8: facebookarchive/xctool#704.
Also switch from xctool to xcodebuild since xctool isn't supported on Xcode 8: facebookarchive/xctool#704.
|
@cegonya I've seen similar with our own projects, also on 0.2.10 and Xcode 8.1 beta 3. I'm new to reverse engineering Xcode frameworks, but from my debugging with Where before there was: There is now: The class can be initialized with something like this: |
Note: xctool is currently incompatible with Xcode 8. See facebookarchive/xctool#704
xctool doesn’t support building anymore since Xcode 8. See facebookarchive/xctool#704 for details.
|
xctool doesn't support building for Xcode 8 and later. Please, update to xcodebuild or other build tools. xctool will still support running tests. 0.3 release is pending approval and should be soon available via homebrew. |
|
I have updated xctool to version 0.3.1 via homebrew, xcode 8.1 final There is my command line : that worked well in xcode 7 Script Build: |
|
xctool now supports only running tests. Replace in your script |
|
Or even better xcodebuild + xcpretty for nicer output https://github.com/supermarin/xcpretty |
|
@ExtremeMan when I change xctool to xcodebuild - I have error "xcodebuild: error: invalid option '-reporter'" |
|
@LavrL pipe to xcpretty for that |
|
@fabb any other solution ? |
|
@LavrL oops, i meant xcpretty, not xctool. |
* Swift 3.0 * Indention * Replaced travis xctool with xcodebuild See facebookarchive/xctool#704 * Travis build check
|
Still met the same problem. Is this issue closed? |
|
@guoyingtao yes follow what @ExtremeMan said replacing |
and others
I have a swift project that runs tests on travis-ci, and once I created the swift 3 branch and tried to run the tests it failed on an assertion. The tests themselves are fine since I have successfully run them locally.
https://travis-ci.org/cezheng/Fuzi/builds/140457732
The text was updated successfully, but these errors were encountered: