Opening Import File for Module 'Swift': Not a Directory

unknown :0: error: opening import file for module 'Swift': File name too long

So I solve the problem. The issue when updated to Xcode7 was that the Framework Search Paths value $(SRCROOT) was set to recursive. For some reason this was not working for me in Xcode7. I have $(SRCROOT) set to recursive in Xcode6.4 where it was working perfectly fine but after the update to Xcode7 it start to show:
:0: error: opening import file for module 'Swift': File name too long
I deleted $(SRCROOT) value and add $(PROJECT_DIR)/... paths for every library and framework used within my app. I tried to just set $(PROJECT_DIR) with recursive value but I would get the same compiling time error so the solution was just to specify the path to every library and framework used.

Hope this helps to other folks that have the same issue.

Opening import file for module 'Swift' Permission denied

SO i figured out what was causing this issue. It was the 'Search Paths' under 'Build Settings' that was looking in the wrong location for my frameworks. Similar to the Apple Mach-O linker error fix

It was searching my for the frameworks on my macbook pro, I deleted the 'Framework Search Path' and then re-added my Parse.framework, Bolts.framework and FBSDKCoreKit.framework.

The project now builds and runs just as it should without any issues.

Getting error No such module using Xcode, but the framework is there

I'm not sure why this happens, but one way to solve your issue is to go into your build settings and defining the Framework Search Paths to a folder which contains the frameworks in question. If the frameworks are placed in your project directory, simply set the framework search path to $(SRCROOT) and set it to recursive.

---

Related Topics