external framework File/File.h (Parse/Parse.h) file not found

Question

So every time I update my app, Xcode claims not to be able to find a particular external framework even though it\'s there. It\'s happened again with Xcode 6 and my usual m

Answer 1

In my case, the error went away after I added the path to the directory where Parse.framework was to the Frameworks Search Paths Build Setting:

My project didn't even have an entry for that setting, so you may need to create it as well.

Answer 2

Ok, so I was having this problem as well. I uninstalled all my pods, reinstalled them again, and had no luck. So the good news (and bad news considering the time I spent trying to find the problem) is that I eventually managed to solve it. Apparently, you have to import Foundation/Foundation.h before parse. I don't know whether this will work for you or not, but I tried everything on the net, and only this seemed to work. If you have any instances of this:

#import <Parse/Parse.h>
#import <Foundation/Foundation.h>

flip it around so that Foundation is declared first:

#import <Foundation/Foundation.h>
#import <Parse/Parse.h>

I also read somewhere that some people had issues with Facebook SDK and Parse SDK import. Apparently, the two have Bolt.Framework in common or something, which causes error. I removed Facebook SDK as well, which at first didn't make any difference. I hope I could help.

Answer 3

I had this error also. I'm developing in Swift, so I added a "bridge header" as described in this Parse blog post.

The reason I got the "Parse.h not found" was that my project name contained spaces. (For project name I mean the Product Name you enter when creating a new project, which determines your folder's name.) The first day all went well, but after closing and opening Xcode, it turns out that Xcode interprets the words separated by spaces as different paths.

To fix this, you can go to Build Settings -> Search Paths -> Framework Search Paths and add an "\" before each space. (If you double click the path you'll see that Xcode shows each word separated by space as a different entry.)

Also note that the bridge header with #import <Parse/Parse.h> it's not compulsory: you can simply do import Parse.

Answer 4

Just to Share my findings in case if somebody might have the same issue:

Accidentally we had two references of Parse.framework inside our source code base at two different places. And a reference of Parse.framework was linked in Build Phases of the target, from the first place. But when the app is compiled, Xcode was not smart enough to get a reference and trowed an error: "Lexical or Preprocessor Issue" error when "Parse/Parse.h" is imported in .pch file. After spending couple of hours by trying various options, removed a reference of Parse.framework from the source base and kept only a single reference. This solved the issue.

And the app compiled successfully :)