There have been a lot of issues lately related to iOS UI tests and new kinds of xcodebuild exit code 65. Some of them are related to you switching to Xcode 8 some are probably unrelated.
I do not have a sane explanation at this point for any of your issues, nor do I have a solution for you but I have a couple of ideas and the more data we gather the faster I can resolve this for you.
I will update this post tomorrow with further information for you and maybe some stuff for you to try.
Thank you for your patience, I want to resolve this as fast as I possibly can for you.
Sorry for not updating in this in the last two days but I was in the process of setting up a controlled area within CircleCI in which we can test. Iām almost done preparing everything and will update this again as soon as I have more information and things to try for you.
I have been really sick all week so Iām a bit behind schedule, please excuse that. I have great colleagues though and they helped out getting a sandbox ready for us to test and play in and get all you back to green builds.
If you can contact me directly via a support ticket, please use the DM function in discuss or @ me here.
Iāve started testing some of your projects but ran into issues, those are not related to you at all and I think weāll get them resolved today. If you run into issues with your builds please let me know!
Sorry for the missed update yesterday but I was finally able to get to work. Our system is not setup to serve the tasks I ask it to do so I have to hop through all kinds of weird hoops.
As a heads up I will have to create an API token with for your account. It will be called something along the lines of CIRCLECI_EMPLOYEE_TESTS.
I will gather information all day today and update this thread again tomorrow morning with the things Iāve found. My current hunch is that you are running into issues with code signing dependencies. If youād like to share it either here or through your support tickets, please let me know what kind of dependencies you have and how you get them (CocoaPods, Carthage, direct install into the project).
Thanks for the update. Our dependencies are React Native (downloaded via npm and then built directly from Xcode), a big bundled JS file, and a custom Go library also incorporated directly into the Xcode project.
Hi Constantin, I registered a support ticket too, but I would very much like to get this looked at with our builds too. Our dependencies are gym/deliver/match for deployment/provisioning, bitbucket for the match certificate repository, TTTAttributedLabel via Carthage and the following pods:
pod 'BlocksKit', '~> 2.2.5'
pod 'IGHTMLQuery', '~> 0.8'
pod 'AFNetworking', '~> 3.0'
pod 'AFNetworkActivityLogger', git: 'https://github.com/AFNetworking/AFNetworkActivityLogger.git', branch: '3_0_0'
pod 'OHHTTPStubs'
pod 'BKPasscodeView', '~> 0.1.2'
pod 'UICKeyChainStore'
pod 'UIColor-HexRGB', '~> 1.0.1'
pod 'Masonry', '~> 0.6.2'
pod 'Stencils'
pod 'ReactiveCocoa', '~> 2'
pod 'RMStore', '~> 0.7'
pod 'RMStore/AppReceiptVerificator'
pod 'RMStore/TransactionReceiptVerificator'
pod 'RMStore/KeychainPersistence'
pod 'RMStore/NSUserDefaultsPersistence'
pod 'Underscore.m', '~> 0.3'
pod 'OCMock', '~> 3.1.2'
pod 'Specta', '~> 1.0.3'
pod 'Expecta', '~> 1.0.2'
we have the same error sometimes with Xcode 8 on circle with those dependecies:
target :'XXX Tests' do
pod 'Specta', :git => 'https://github.com/specta/specta.git'
pod 'Expecta', '~> 1.0.5' # expecta matchers
pod 'OCMock', '~> 3.3' # OCMock
end
target :'XXXUITests' do
pod 'Specta', :git => 'https://github.com/specta/specta.git'
pod 'Expecta', '~> 1.0.5' # expecta matchers
pod 'OCMock', '~> 3.3' # OCMock
pod 'Bugsnag'
pod 'FMDB'
end
Thanks a lot for the little insight into your stacks.
Iām in the process of preparing our OS X image that has Xcode 8.1 beta 3 in it and Iād like to ask everyone to set aside a branch named e65-tests which tests again Xcode 8.1. In order to do so please just change your circle.yml to look like this:
machine:
xcode:
version: "8.1"
If you have the branch I will find it and take a look at your builds. I will look for it
Sorry for not being as explicate as I should have been. As @pavel-zdenek correctly stated we do not have this version Xcode deployed to any of our production servers. My private machine incorporates into our system but everything is more of a hack than anything else at this point since we never tried to run such a test before. I will turn on the Xcode 8.1 feature setting on shortly and will update you on further progress
Thanks for your patience, Iām working as fast as I can.
We would love to take a look at the root cause(s) here. Can you file radars with sysdiagnose, ~/Library/Logs/CoreSimulator, and ~/Library/Developer/Xcode/DerivedData/[project-subfolder]/Logs
Even if they are duplicates extra logs help a lot.
sysdiagnose requires root so I assume end users canāt run it themselves but it might be worth having a setting to collect this data on failure so people can more easily file bugs in the future.
@russbishop ~/Library/Developer/Xcode/DerivedData/ does not contain subfolder āLogsā and ~/Library/Logs/CoreSimulator contains an EMPTY subfolder structure āsome-uuid/CrashReporter/DiagnosticLogsā. Somewhat logically empty, as the simulator did not even start due to failed framework loading (insisting on having a signed one - for a simulator run?). Does it still make sense to fill a radar with sysdiagnose?
,
