Cyclic dependency error causes builds to fail with Cocoa Touch Framework

Originator:crspybits
Number:rdar://23218303 Date Originated:10/22/15
Status:Open Resolved:10/22/15
Product:Xcode Product Version:Xcode 7.0.1 and 7.1
Classification:Serious Bug Reproducible:Always
 
Description:
This problem has been ongoing for a couple of weeks now, ever since I created a Cocoa Touch Framework with both Swift and Objective-C code and incorporated that framework into my project. I have a work-around for this problem, so while this has been a hassle, until recently I’ve been able to make progress. However, I just tried to generate a .ipa to upload the app and learned that my work-around isn’t successful for production builds.

Steps to reproduce:
1) Do a clean of all Derived Data
2) Do a build of the project

Expected results:
The project is free of syntax and other errors and should build and run normally.

Actual results:
I get a cyclic dependency error causing build to fail.

Xcode Version/Build & OS X Version/Build
I have been primarily using Xcode 7.0.1, but have now seen this error in Xcode 7.1 (non-beta) just released.
OS X 10.10.5

Additional Notes
Note that for debug builds I have a work around to this issue. See “Second fix: A workaround” in http://stackoverflow.com/questions/32919285/ios-framework-with-swift-and-objective-c-where-the-objective-c-uses-swift-c

HOWEVER, if I do a production build (e.g., Product -> Archive), I have been unable to build without this error and thus am currently unable to submit this app to Apple.

Comments

Note that I resolved this myself and will be informing Apple shortly. See "final" solution part of http://stackoverflow.com/questions/32919285/ios-framework-with-swift-and-objective-c-where-the-objective-c-uses-swift-c

By crspybits at Oct. 23, 2015, 4:31 a.m. (reply...)

Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!