Alright, guys. I'm going freakin' crazy with this one. It is utterly ridiculous that the FacebookSDK causes so many issues. I know there are a couple questions on here regarding this issue, but they all seem to be outdated.
I pulled my Xcode project onto a new computer, and can't build it because I get the "FacebookSDK/FacebookSDK.h" file not found error. There are answers such as This one, but I've followed the steps in every single answer and haven't found one that works. I've just made a fresh pull from my working project from the original machine to the new one. I'll take some screenshots showing my current settings for various fields mentioned in other answers, and maybe I Just have something wonky that is interfering.
Here are the contents of the SDK that I just downloaded
Here are the contents of my Xcode project folder. There isn't anything else Facebook in here.
Here are the frameworks inside my Frameworks group and inside the Link Binary with Libraries section of Build Phases
There are a couple frameworks that are red, and that's OK for now. They were not in the repo, and are instead referenced from Documents or Downloads, and they played nice when I moved the files over and linked them. I just reset my repo to when I pulled it to make sure I didn't have anything from weird stuff I tried that prevents a proper solution from working.
Framework search paths. You can also see that my library search paths is empty. I labeled the stuff I wanted to hide, as it was identifying information
For some reason, my Documents for the new machine is already under the framework search paths. I did not add this myself.
Any ideas on what I can try? This is endlessly frustrating. I've wasted an entire day of development on trying to get Facebooks SDK re-integrated on a new machine.
I was also face the same problem every time I got the checkout for new version from svn.What I did was just removed the Facebook SDK and add again from the backup.It taken me out that time.Please try this might be it works for you.
Related
I have a Xcode project I got from another developer. Initially when I opened it it has a bunch of errors (most of which were un-updated frameworks). I got it to work after a while and I fixed it. I want pass it back to the manager since I'm leaving uni in a few months. I copied it over to my friends Mac to see what would happen if I just took the project and all it's folders and made it a zipfile. It didn't work for some reason. It gave me an error:
error: using bridging headers with framework targets is unsupported
But why did that come up? I mean it's the same code on the slightly different versions of Xcode (13.1 versos 14.1) but I doubt there was a massive change between the two that would cause this. I want to be able to pass these app later in the future without having to care about this stuff. I made a GitHub (link below) would cloning that work? Also the laptop I chose was just a fresh reset. Would it be due to not having coco-pods installed?
I feel like I could go through and fix it all on that laptop and document that but then I'm afraid that every time I put it on a new one it would come up with random errors every single time making my documentation moot.
https://github.com/AbdullahMSaid/SonicExperiment-Works
With big help this was Fixed.
Things that fixed it.
Having the correct version of Xcode
Turning everything from absolute path to relative
Lots of other code fixes. But those are my project specific.
You don't need bridging headers in framework. Use should have something like "YourFramework.h" where you can import your .h files.
I know that there must be a whole bunch of questions like this, but I tried everything, and nothing would work.
I'm creating a iOS app, and I use Google Ad Mob. I built my Xcode project from Unity, but when I tried to archive it in Xcode, there is this annoying error "GoogleMobileAds.h file not found"! I have the Google Mobile Ad Framework, but when I put it in the project, the error still shows! I looked up this problem, and tried to follow some of the people to fixed it, but the error still wouldn't go away.
Could anyone help please?
Here is the link to the project you can download.
Xcode project
I fixed this by going to Framework Search Paths in build settings, and putting in the GoogleMobileAd.framework!
as #SullyBully already correctly mentioned.
You have to add your folder with the Admob SDK to Framework Search Paths in Build Settings.
Additionally you have to include your GoogleMobildeAds.framework into your frameworks section in xcode (no ideas whats that called)
See screenshot 1 and 2 (I literally spent now hours because of it, hopefully this finds a soul helpful :P)
By the way it is completely neccessary just to include GoogleMobildeAds.framework.
You dont need to include the others like GoogleUtilities, or GoogleAppMeasurement etc.
After you build the the game in Unity.You also have to add google admob iOS library to your Xcode project. You can get from : [https://developers.google.com/admob/ios/download][1]
In my project I am having a problem with the fbsdk. Upon linking the fbsdkcore to my project in xcode using the rnpm as shown here: https://facebook.github.io/react-native/docs/linking-libraries-ios.html
My build now fails due to my RCTFBSDKCore cannot find the RCTBridgeModule.h, even though I think I have gone through all the neccessary steps to include this, even in the Header Search in build settings as shown below:
Linking Binary w/ Lib:
And the Header Search:
After this I am quite lost. I have also tried to update all of my packages without success. And as one can see in the picture below, I have two fbsdkcore, is this one too many, because it is only when I try to build the RCTFBSDKCore that it fails, it is successfull in the other case.
Ok, so to my question. Could it be that the library should not be included like that in the first place? If not, what have I done wrong/missed?
rnpm does not support linking multiple libraries at the moment. Check this article for setting up RN & fbsdk.
First of all, I've never worked on iOS, so this may or may not be a stupid question, I don't know :)
I have an iOS App, and I need to run it.
In the 'Project Navigator' I have a folder/package called 'Reuse and Platform Libraries'. Inside, I have another four folders but 3 of them seem like missing.
I am not sure if this is the case. I've tried googling their name but without results so I assume they are not some open source libraries.
Can someone clear this up for me? Do I need to install some XCode packages?
Thanks!
I suggest you search the folder of the project for those files, sometimes when copying a project the paths get screwed up because they were set as absolute paths and not relative paths.
If you can't find the files, it's most likely that the library is a private one used by the previous developers, and usually kept out of the project folder so they probably forgot to send it along. I'd suggest simply asking them to send the files over :).
There is also a slight chance they are not needed to run the file, in which case, just deleting them from the sidebar should make the project run.
I use DropBox and SkyDrive in my applications and they work like a charme with a very good documentation, but GoogleDrive is really hard to integrate (to be polite :) ).
I'm not talking about coding but integration in xcode.
i follow this tutorial.
In step 3 i have 8 point to do, the problem is in point n°7, there's no Sources path, i search in the svn folder i download and it's not there. and of course without linking headers i have this issue "GTMOAuth2ViewControllerTouch.h no such file or directory"(i think that compiler stop there but there's more error).
what can i do ?
I know this is really old, but I had this problem and found a solution.
When you add the "User Header Search Paths" to the source directory, you need to make sure you set it to recursive so it gets all of the contents of that directory. Hope that helps.
The Source directory is immediately under the trunk that you checked out.
There is a Google Developer video (embedded at the bottom of the tutorial) that shows all the steps listed in the tutorial. Unfortunately the presenter does skip some troubleshooting and the steps he's following are very slightly different to the current version of the tutorial, but it is still helpful.