Error Http Status Code 400 Facebook Sdk
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more http status code 400 . verify that the exchange mailbox server is working correctly about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users
Http Status Code 400 Returned By The Server
Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping http status code 400 reason request uri is too long each other. Join them; it only takes a minute: Sign up Facebook iOS SDK 3.1: “Error: HTTP status code: 400” up vote 17 down vote favorite 6 I am running the Facebook SDK 3.1 on Xcode 4.5GM with iOS6
Http Status Code 404
simulator. I connect to FB in the iOS settings and successfully FB connect in my app using the new iOS6 FBConnect UI. I have an access token, can see my friends, send app requests, post to my wall, etc. However, every time I initiate any sort of FBURLConnection is made, I see this printed to my console: Error: HTTP status code: 400 I went into the FB code and printed the reponse when this error is printed http status code 403 and I get: { body = { error = { code = 100; message = "(#100) The parameter 'attribution' is required for the 'mobile_app_install' activity"; type = OAuthException; }; }; code = 400; } Does anyone know how to resolve this? All functionality seems to work, but I keep seeing this spam my console. ios facebook facebook-graph-api facebook-ios-sdk share|improve this question edited Sep 26 '12 at 5:33 asked Sep 26 '12 at 5:16 stipe108 1,20511216 I can't even connect properly. I've even followed the guide at: developers.facebook.com/docs/tutorial/iossdk/… –Joakim Engstrom Sep 26 '12 at 16:23 add a comment| 6 Answers 6 active oldest votes up vote -2 down vote accepted This error reflected a bug on the server, which was fixed shortly after the 3.1 release was published. At this point there should be no more failures coming from this request. Hope this helps! share|improve this answer answered Oct 5 '12 at 3:21 Jason Clark 1,35368 7 I'm still seeing this in 3.1. It occurs the first time the app requests permissions (if I've deleted the FB app from the list of authorized apps in my settings). Subsequent requests work, however. This seems to only happen on the device, not in the simulator. –Senior Oct 16 '12 at 20:24 add a comment| up vote 18 down vote Right after the session is created do this: [FBSession setActiveSess
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more
Http Status Code 411
about Stack Overflow the company Business Learn more about hiring developers or posting ads
Http Status Code 500
with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow what does error 400 mean is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Facebook sdk - error: http status code 400 up vote 4 down http://stackoverflow.com/questions/12594965/facebook-ios-sdk-3-1-error-http-status-code-400 vote favorite So I'm trying to get facebook working with my new app, and I just cant figure this out. I got every thing done like in the tutorial docs on their website. And when I start the app, I get a "Error: HTTP status code 400"; and nothing more to it. I read all over the place that this is a serverside bug on facebook, but seriously? Some http://stackoverflow.com/questions/13291591/facebook-sdk-error-http-status-code-400 people have this working? This is my code anyway: FBSession* pFacebookSession = [[FBSession alloc] init]; [FBSession setActiveSession: pFacebookSession]; if (FBSession.activeSession.state == FBSessionStateCreatedTokenLoaded) { NSLog(@"openWithCompletionHandler start."); [FBSession.activeSession openWithCompletionHandler:^(FBSession *session, FBSessionState status, NSError *error) { NSLog(@"openWithCompletionHandler FINISHED!"); }]; } not sure if this is what it is exactly to look like. ios facebook share|improve this question edited Mar 7 '13 at 18:39 Stedy 3,865113355 asked Nov 8 '12 at 15:03 Tordin 30119 What tutorial did you follow, exactly? Because the code from the official tutorial looks completely different. –patric.schenke Feb 11 '13 at 13:31 developers.facebook.com/docs/tutorials/ios-sdk-tutorial try this tutorial its working in my app without any error –Naresh Apr 16 '13 at 7:34 add a comment| active oldest votes Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook. Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name Email Post as a guest Name Email discard By posting your answer, you agree to the privacy policy and terms of service. Browse other questions tagged ios facebook or ask your own question. asked 3 years ago
can use our debug tool, or you can use the API endpoint. To use the API, you can issue a Graph API request: GET /debug_token? input_token={input-token}& access_token={access-token}input_token: the access https://developers.facebook.com/docs/facebook-login/access-tokens/debugging-and-error-handling token you want to get information about access_token: your app access token or a valid user access token from a developer of the app The response of the API call is a JSON array containing a map of fields. For example: { "data": { "app_id": 000000000000000, "application": "Social Cafe", "expires_at": 1352419328, "is_valid": true, "issued_at": 1347235328, "scopes": [ "email", "publish_actions" ], "user_id": 1207059 } }Note that the issued_at http status field is not returned for short-lived access tokens.Handling Errors Facebook doesn't notify you that a previously issued access token has become invalid. Unless you have persisted the expiry time passed to your App along with the access token, your app may only learn that a given token has become invalid is when you attempt to make a request to the API. Also, in response to certain events that http status code are security-related, access tokens may be invalidated before the expected expiration time. In most apps, the best way to handle expired tokens is to capture the error messages thrown by the API. In each case, the API will return an HTTP 400 status code, a code and a subcode in a JSON body explaining the nature of the error. (These examples don't include a subcode, but subcodes are described in the error reference.) Expired or invalid access tokens Access Token has expired { "error": { "message": "Error validating access token: Session has expired at unix time SOME_TIME. The current unix time is SOME_TIME.", "type": "OAuthException", "code": 190 } }Access Token invalidated due to the person logging out or changing their password { "error": { "message": "Error validating access token: The session is invalid because the user logged out.", "type": "OAuthException", "code": 190 } }If the access token becomes invalid, the solution is to have the person log in again, at which point you will be able to make API calls on their behalf once more. The login flow your app uses for new people should determine which method you need to adopt. Person has de-authorized your app { "error": {