Xcode 8 b3 won't load libswiftCore.dylib

I have the same problem.

I'm also seeing this, everything was fine until b3. Swift 2.3/ObjC mixed project. I've tried a number of the proposed solutions to this, but found no resolution yet.

Another thread covering this problem: https://forums.developer.apple.com/thread/52139

Ditto, also run into this today.

I have a Swift based library which I use Carthage to build and then embed into my application. Everything was fine using Xcode8b2, but now it doesn't work

I've also had it display:

@rpath/libswiftAVFoundation.dylib

and

@rpath/libswiftContacts.dylib

I put a VERY simple project together last night which works with b2, it has a single dependency which is managed by Carthage, it does nothing more then instantiates a class from the dependent library and calls a method on it which prints a message to the console, like I said, really simple.

Using b3, it crashes with

dyld: Library not loaded: @rpath/libswiftCore.dylib
  Referenced from: /..../Library/Developer/CoreSimulator/Devices/267A7C7F-1AC3-4D2D-A041-46990226EF7A/data/Containers/Bundle/Application/11005A59-9ABB-4C4A-9FA1-F71E5A67F066/TestBaseApp.app/TestBaseApp
  Reason: image not found

https://github.com/RustyKnight/TestBaseApp

I can am seeing this too.

What is weird is that I'm making a set of Frameworks for iOS, macOS and tvOS. The iOS and tvOS Frameworks fail to be tested with this error. However the macOS Framework and its tests have no such problem.

My message with links in the other thread is being moderated but if you want the answer you can google for:

github carthage issues 1394 abi mismatch.

Would be great if some other people could verify this for me and post in the Carthage issues page or here about it.

I'm about to try figure out watchOS now which is the last bit of the puzzle I need to keep working.

Definitely file bugs on this at http://bugreport.apple.com/

Please definitely file a bug report on this as rsharp says and comment with the bug number. Please attach a small sample project that is exhibiting the issue.

Someone else already filed a Radar for this problem (including a temporary workaround):

rdar://27459058

I can't link to it, but this radar is also copied to OpenRadar for anyone outside of Apple who would like to take a look at the workaround 🙂