facebook-ios-sdk

i have integrated Facebook sdk in Xcode 6 (with swift). During the login i request the public_profile permission: FBSession.openActiveSessionWithReadPermissions(["public_profile"], allowLoginUI: true, completionHandler: { ... ... So i request the user's information: FBRequestConnection.startForMeWithCompletionHandler { (connection, user, error) -> Void in ... ... Why the user object doesn't contain the profile picture? How can i get the user profile picture? It's not part of the public_profile? I get the following information: 2015-01-25 01:25:18.858 Test[767:23804] { "first_name" = xxx;

I am using Xcode 7.0, testing on iOS 9.0.2 and using Facebook SDK 4.7.0. When I am logging in a user, most of the time everything works as it should, however sometimes I keep getting this error and I have no idea why! The operation couldn’t be completed. (com.facebook.sdk.login error 308.) After researching I have seen that some people are getting the error when logging in with parse.com's FBUtils and the official FBSDK at the same time, however I am only using FBSDK in my project. So my question is, why am I getting this error and how do I get rid of it? Edit - Adding Code Here is my login

I'm new to app development, and I've been building a social iOS app that requires sending Facebook invites to join the app. Yesterday's release of Facebook Graph API 2.0 seems to have much stricter requirements on how to invite those not already part of the game. I'm trying to activate me/invitable_friends but I keep getting the same message: { "error": { "message": "(#15) This method is only accessible to Games.", "type": "OAuthException", "code": 15 } Their documentation mentions needing to be a Canvas app, so I added placeholder URL's as Canvas pages. Not sure if that's sufficient.

This question already has an answer here: FBSDKShareDialog cancels when it should post 4 answers I'm trying to share a post with the Facebook SDK, but sharerDidCancel is always called, either if I share or cancel the post. Here is my code - (void)shareFacebook { FBSDKShareLinkContent *content = [[FBSDKShareLinkContent alloc] init]; content.contentURL = [NSURL URLWithString:@"http://www.google.com"]; [FBSDKShareDialog showFromViewController:view withContent:content delegate:self]; } - (void)sharer:(id<FBSDKSharing>)sharer didCompleteWithResults :(NSDictionary*)results { NSLog(@"FB: SHARE

I was following the tutorial for facebook sdk for ios, specially using open graph to attach an image and tag friends (which social framework can't do directly). So I was following this tutorial and this sample app, FBOGSampleSD. https://developers.facebook.com/docs/ios/open-graph#sharedialog However my post button in the share dialog is always disabled. (grey out) Has anyone encountered this before? I am working with Xcode 5 and testing on ios7 device. Regards, Jin I think I figure this out. Your share button might be disabled because you didn't finish the Facebook app configuration, or it

I am using Facebook sdk 3.2 for iOS, There are various sample project available for iOS But my problem is how can i get the list of friends without opening FBFriendPickerViewController. In fact i want all my friends facebook id and there Any help will be appreciated. Thanks in Advance DharaParekh Try this: get friend list using **[FBRequest requestForMyFriends];** **FBRequest* friendsRequest = [FBRequest requestForMyFriends];** [friendsRequest startWithCompletionHandler: ^(FBRequestConnection *connection,NSDictionary* result,NSError *error) { NSArray* friends = [result objectForKey:@"data"]; .

The Facebook iOS SDK 3.0 Beta says "These new features work with iOS 4.0 and later." Does that mean that it won't work on iOS 3.x? Does that mean that if I have an app that supports iOS 3.x, I cannot use Facebook iOS SDK 3.0? Correct. Facebook iOS SDK 3.0 will not work with iOS 3.x. We felt that the productivity enhancements (e.g. blocks) in iOS 4.x were simply too useful. The SDK is open source, and we plan to maintain the history, which includes the existing code that does work with 3.x. In this way there is still an option for applications that need to continue to support older versions of