search

pivotal-legacy / PivotalCoreKit

Shared library and test code for iOS and macOS projects
http://pivotallabs.com
Other
168 stars 85 forks source link

WatchKit specs fail to run in Xcode 8.3.2 / Xcode fails to run other specs thereafter #201

Open akitchen opened 7 years ago

akitchen commented 7 years ago

In Xcode 8.3.2, the WatchKit specs fail with the following:

dyld: Symbol not found: _SPHoldCompanionExtensionProcessAssertion
  Referenced from: /Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 10.2.simruntime/Contents/Resources/RuntimeRoot/Developer/Library/PrivateFrameworks/DVTInstrumentsFoundation.framework/DVTInstrumentsFoundation
  Expected in: /Users/akitchen/Library/Developer/Xcode/DerivedData/PivotalCoreKit-bwbtwtidhjdzglafroxsporifhot/Build/Products/Debug-iphonesimulator/WatchKit.framework/WatchKit
 in /Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 10.2.simruntime/Contents/Resources/RuntimeRoot/Developer/Library/PrivateFrameworks/DVTInstrumentsFoundation.framework/DVTInstrumentsFoundation
2017-05-19 20:01:25.273 xcodebuild[36015:478160] Error Domain=IDETestOperationsObserverErrorDomain Code=6 "Early unexpected exit, operation never finished bootstrapping - no restart will be attempted" UserInfo={NSLocalizedDescription=Early unexpected exit, operation never finished bootstrapping - no restart will be attempted}

Testing failed:
    Test target Specs encountered an error (Early unexpected exit, operation never finished bootstrapping - no restart will be attempted)
** TEST FAILED **

... and then the shared build output is unusable for testing the other non-WatchKit targets in the project, causing the tests to fail to bootstrap in the same way. Anyone working with the project will need to remove their DerivedData folder or "Clean Build Folder" in Xcode after running the WatchKit specs in Xcode 8.3 before any other test bundles from the project can be run again.

This means we're stuck on Xcode 8.2 on Travis for a while, and we'll need to figure out what's going on. This is worth filing a radar over, I think.

younata commented 7 years ago

I don't think it's radar-worthy. I'm of the opinion that it's because of WatchKit 1.0 support being removed (which we need for a watchkit storyboard).

akitchen commented 7 years ago

makes sense. Since one can't submit apps using those APIs anymore, our supporting functionality should also be removed in an upcoming release. This should allow us to move forward on Xcode versions.

Thanks @younata