Where can I find a list of all the error codes for Facebook's FacebookApiException class? I found 2 such lists, both of which are outdated: https://developers.facebook.com/docs/reference/api/errors/ and http://www.fb-developers.info/tech/fb_dev/faq/general/gen_10.html
From debugging my own script, I found out that error #2500 is "An active access token must be used to query information about the current user." and error #3501 is "User is already associated to the article object on a unique action type Read." Neither error codes are in the links posted above.
This might help you. Most probably Login related error.
https://code.google.com/p/facebook-actionscript-api/issues/detail?id=453
Related
How can I force TYPO3 to display 404 page instead of displaying technical errors?
Example if TYPO3 can not resolve given url to property I am getting following error:
Oops, an error occurred!
Exception while property mapping at property path "": The identity
property "dfgdfgdfgdfgdfgdfgdfg" is no UID.
More information regarding this error might be available online.
I already tried to resolve it by configuring
$GLOBALS['TYPO3_CONF_VARS']['FE']['pageNotFound_handling'] =
'USER_FUNCTION:.....';
$GLOBALS['TYPO3_CONF_VARS']['FE']['pageUnavailable_handling'] =
'USER_FUNCTION:.....';
but this does not seem to have any effect on those types of errors.
Have you tried from here
I hope this will help you!!
Recently I get temporary errors from Facebook API after user is trying to share a post through "me/feed" route.
The error message is :
"message":"Service temporarily unavailable",
"type":"FacebookApiException",
"is_transient":true, "code":2,
"error_subcode":1609010,
"error_user_title":"URL Not Found",
"error_user_msg":"We had trouble using the URL you provided. Please try again later.",
"fbtrace_id":"DgSULoXJMfK"
Anyone know what could be the reason for this?
I'm pretty confident this is a bug. We're finding that the exact same post will fail when published to some pages, but succeed on others. This sort of inconsistency along with the feedback of others (see below) suggests that this behavior is due to a bug.
https://developers.facebook.com/bugs/1571642049794292/
I've the same error when try to use Facebook OAuth2 with scope=email name
Fixed by setting scope=email
This question was asked already, but the accepted answer is not helpful as the poster seems to have figured it out themself and left out how they got the access token.
Posting on Facebook wall from Codeigniter app
Anyhow, it seems that I can redirect to the login url and log in , but its not finding the auth token. Throwing this error:
Fatal error: Uncaught OAuthException: An active access token must be
used to query information about the current user. thrown in
/home/howekevin/biologicalfinder.com/dev/application/libraries/base_facebook.php
on line 1040
Also, if you use the example on the SDK and var_dump $user, I'm getting int 0 even after I'm logged in. I notice it's using a lot of $GET array stuff, and CodeIgniter doesn't jive with that. Has anyone solved this issue?
Ahh, so you found Elliot's broken code. Give my oauth library a spin:
http://getsparks.org/packages/codeigniter-oauth/versions/HEAD/show
Or Phil Sturgeon's:
http://getsparks.org/packages/oauth2/versions/HEAD/show
Our code should actually work ; )
Mind you mine and Phil's libraries only handle auth, but seems that's what you're having trouble with at the moment (and it's the hardest part). Check out the Facebook developer docs for the rest (if you can make a POST request, you can do this).
Does anyone know where can I find all the error code and error type for FBGraph? While handling error, I want to check what error FBGraph throws (like: duplicate post error, access token expire error) and take action accordingly. (I a working on Ruby On Rails 3)
I referred the documentation, but it doesn't list out the code and type of all the errors. Where can I find these error codes?
Thanks... :)
This has long been a problem with using the Graph API. There's no documentation anywhere as to all the possible errors that you can receive. Additionally there are errors that you receive randomly that don't occur when you make the same request again (ie bugs).
A lot of the Graph API seems to have an underlying structure that makes FQL queries. So, when those FQL based queries throw an error you can find the code here: http://fbdevwiki.com/wiki/Error_codes#FQL_Errors
I'm looking for a list of all Facebook can return when you try to fetch infos using Graph API. Can anyone help?
Facebook returns a 400 HTTP error, and a JSON content like:
{
"error": {
"type": "OAuthException",
"message": "Invalid OAuth access token signature."
}
}
I'm searching the different returns of the same kind it is possible to get.
Facebook used to have this published somewhere, but for whatever reason it was removed. But you can find the full list here:
http://www.takwing.idv.hk/tech/fb_dev/faq/general/gen_10.html
There seems to be a list now for the errors.
I posted answer for the same question here: Facebook Graph API error code list
(I found the list here https://developers.facebook.com/docs/graph-api/using-graph-api/error-handling)
In case Takwing's copy ever comes down, here's another copy: http://fbdevwiki.com/wiki/Error_codes
These codes were primarily for the REST API, but they do also come up with the Graph API. Some of the Graph API calls have underlying FQL calls that return the FQL error codes. And the direct FQL queries are still part of the currently accepted API.
Update: I'm trying to keep this list up-to-date. Please feel free to make changes as you encounter new errors.
I am trying to keep an updated list of error codes based on previous outdated information.
You can find the repo here http://github.com/phwd/fbec and it has been updated with Test User and Credit Error codes from the Facebook Documentation.
Currently looking for the constant name for "Error Code 2500" and some error descriptions may have changed. I hope to keep on top of this.
There is an official error code page, now:
https://developers.facebook.com/docs/marketing-api/error-reference/
It still doesn't look comprehensive...