Why there is no twitter framework in xcode? - twitter

I am new baby to Xcode, was trying to learn twitter integration, downloaded sample twitter source code from sample code, but when i tried to run it, it says that there is no twitter framework, and when I try to add from 'Link Binary with Libraries' there is no twitter framework!!
I am using Xcode 4.2 with ios 5.
Is it possible to manually import twitter framework into my Xcode??
Please help me.

Forget about the "Twitter.framework" from now on.
Apple has switched to "Social.framework" which was delivered with OS X 10.8 (Mountain Lion) today.
This means "Twitter.framework" is deprecated now. It's very likely that "Twitter.framework" will be replaced by "Social.framework" in iOS 6, too.
All accounts are managed by "Accounts.framework" which is available on iOS 5 AND "Mountain Lion". If you need to implement "Twitter.framework" for iOS 5, keep this in mind to write "universal code".

It is easy to add the Twitter framework for an iOS 5 project. Please follow the instructions at https://dev.twitter.com/docs/ios/how-add-twitter-framework-your-ios-project

TwitterKit provides wrappers for accessing the Twitter REST API.
Get Fabric from here this will provide you wizard to add all appropriate frameworks for twitter.
https://get.fabric.io/

Related

The Facebook SDK for Swift 4 is outdated. Should I use Facebook SDK for iOS instead?

I found when installing the Facebook SDK with cocoapods that there were several errors in my Xcode project. Upon research I found that this is because the SDK for Swift hasn't been update in a while.
Can someone tell me the best way to implement the Facebook SDK into my Swift application so I can use Facebook Login?
Thanks,
Calum.
Although the errors are still present in Xcode, they do not affect the overall functionality of the program. Therefore, it is okay to simply ignore the errors and hopefully the Facebook SDK will be updated soon.

Facebook SDK Cocoapod isn't a framework?

I'm new to using Facebook & ios development, so I apologize if this is a really stupid question:
Aren't libraries used in iOS development usually in the form of .framework? Why are FBSDK libraries from Cocoapods just a directory full of .h's and .m's? Is there a way for me to convert them into a framework?
I'm using something called the Intel Multi-OS-Engine to enable iOS development using Java, and for it to generate bindings to third-party libraries, they must be in the form of .framework...
Thanks so much!
You can download latest from here
For more information look at quickstart
guide https://developers.facebook.com/docs/facebook-login/ios

need older version of Google Mobile Ads SDK iOS

I am in the need of older version of Google Mobile Ads SDK iOS may be 7.7.0 or older. Please share if anyone has it. I need to work on Xcode 6.3.2 and iOS 8.3. but latest version needs iOS 9 or later.
Thanks.
In case anyone is looking for the answer to this question, as I was today... Here is a solution that incorporates Nika's fine answer and gives you a standalone solution for closed-source frameworks like these.
The Cocoapods specs need to be public and if you go to where those specs are published, in this case: https://github.com/CocoaPods/Specs/tree/master/Specs/5/9/a/Google-Mobile-Ads-SDK
You'll find a list of all the versions of Google Mobile Ads published via Cocoapods.
Each spec contains a download link, so the spec for version 7.59.0 of the SDK / framework shows that link to be https://dl.google.com/dl/cpdc/de07064cf20bb7a6/Google-Mobile-Ads-SDK-7.59.0.tar.gz
You can solve your problem yourself mate:
Step 1: learn cocoapods. Cocoapods are used to integrate 3rd party libraries. It usually stores many many versions of the same libraries. There are plenty of tutorials on this under 10 minutes on youtube.
Step 2: import the version of google mobile ads library you need like this pod 'GoogleMobileAds', '~> 7.7'

facebook SDK with react-native: no framework search path

I was playing around with Facebook SDK with react-native generated ios app template. I was following the instructions here: https://developers.facebook.com/docs/ios/getting-started but somehow did not see Framework Search Paths mentioned in step 4.5. the react-native generated ios project seems to only have header search path, as shown below.
I was using latest Xcode version (9.3)
Try upgrading project templates - Upgrade guide
Or try to use RN wrappers available on the internet.
I personally like these two - this and this
Good luck!
You need to change Basic to All tab at the top of the menu
No need of upgrading anything

NSJSONSerialization crash with Facebook iOS SDK 3.5

After I updated Facebook iOS SDK from 3.2 to 3.5 I'm getting this error when running my app in a device with iOS older than 5 (eg 4.3.5).
dyld: Symbol not found: _OBJC_CLASS_$_NSJSONSerialization
...
Expected in: /System/Library/Frameworks/Foundation.framework/Foundation
I can avoid this crash if I set Foundation framework as Optional, but I don't think this is the best option.
Is there another way to make Facebook SDK works in devices with iOS previous to version 5?
From Facebook iOS SDK changelog v3.5:
http://developers.facebook.com/ios/change-log-3.x/
Removes support for iOS 4.* Facebook 6.0 dropped support for iOS 4.x. To stay in sync, the Facebook SDK is also does not support iOS 4.x.
So, if you update to Facebook SDK 3.5 you lose support for iOS 4.x
That class was not available until ios5 - look at the class reference in the Xcode documentation window. What you need to do is grab JSONKit, an open source class, and use it. Usage is mostly the same. You will need to build this class into your app then test dynamically if the apple class exists, then use the appropriate class, or just always use the open source class.
Note that JSONKit is not ARCified, so you need to set the appropriate compile flag for it if the rest of your app is ARC.
Edit: so you may be able to get clever and write your own stub that bridges calls to JSONKit in older releases. Conceptually you should be able to make this work, but my fear would be that if the FB code was developed for ios5 then there may be other Api problems lurking in the code too - and you old spend a lot of time continually trying to find and fix them.

Resources