We are using the new Facebok Ads report endpoint.
https://developers.facebook.com/docs/reference/ads-api/adreportstats/
In some days, we are getting a weird error:
error:
{
message: "(#100) The parameter data_columns is required"
type: "OAuthException"
code: 100
}
When sending the exact same report on a different range it works.
This is done using async=true since the date range is 24-NOV-2013
If anyone from facebook is looking the report_run_id is 6013557375769.
Anyone encountered this issue?
You need to add the data_columns to your params when you ask for the report.
You can copy them from the original request you did, and this should solve this.
I had the same issue, again it only started happening today.
Adding the data_columns parameter as Tamar mentioned solved it for me:
act_XXXXXXXXXXXX/reportstats?report_run_id=XXXXXXXXXXX&data_columns=["campaign_id","placement","impressions"]
Related
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
I tried to get Data from Facebook Page with the graph of Facebook but I have a problem.
When I try to go on link like:
https://graph.facebook.com/ID-PAGE?access_token=MY_ACCESS_TOKEN
I always do this to have the Data from a Page but since today I have the error Message: "An unknown error has occurred".
Thanks for help.
EDIT:
The bug is fixed : https://developers.facebook.com/bugs/486654544831076/?search_id
Have a look at my answer at
How to get user email and birthday from Facebook API Version v2.4
You have to specify each field you want to query now with v2.4. If you want to explicitly use v2.3, you need to prepend your calls by /v2.3 like this:
/v2.3/{page_id}?access_token=MY_ACCESS_TOKEN
Seems like there's currently a bug regarding requests made with app access tokens instead of user access tokens:
https://developers.facebook.com/bugs/486654544831076/
At this moment, I pretty much figured out what is happening, and it looks like a bug in the Facebook API.
For v2.3 and lower:
The /PAGE-ID call will return an Unknown server error when you don't pass ?fields=username (for example). If you do pass the fields option, it will work. You can get it out of the docs.
For v2.4:
This will work, but you will miss a lot of data, so you'll also have to pass the fields options. But if you don't pass that, this version will give you back only the most basic of details. This is as described in the version release: https://developers.facebook.com/blog/post/2015/07/08/graph-api-v2.4/
So the solution for now, would be to add the ?fields= everywhere you need, or to wait for Facebook to maybe ever solve it.
(And while you're at it, you might as well upgrade to v2.4 ;-)
I have a Facebook application that has been retrieving pictures using the guidance found here: Using Pictures
This has been working up until recently, where now if I retrieve an item picture using the following:
/<id>/picture
I get this response:
{
"error": "Invalid response"
}
Is this a known issue? This has been working up until around this week.
Instead of picture, you should use profile_picture if you want the URL of the pic, just like-
<ID>?fields=profile_picture
Example
And if you want to use the image directly you can use:
http://graph.facebook.com/<ID>/picture
Example: http://graph.facebook.com/Shadowfax.sahil/picture
Using the /ID?fields=picture does not help when you'd like to get an arbitrarily large image. I have experienced Invalid Response when calling /ID/picture in the Graph API and found a solution that fixes it.
Try /ID/picture?redirect=false&width=800. The redirect=false option seems to fix the problem with invalid response from the API.
I get the following error when trying to query me/home
error: {
message: "An unknown error has occurred.",
type: "OAuthException",
code: 1
}
When I query me/feed it's working. And dev documentation says they need the same.
I'm running into the same problem, and guessing (hoping) it is a temporary bug. I noticed if I explicitly specify the fields I'm interested in, then I don't see the error. i.e.
/me/home?fields=from,created_time,description,id,link,message,name,picture,source,story,to,type,updated_time,caption,icon
If I add the "actions" field, the error comes back, so perhaps there is a problem there.
Starting around Friday night, and continuing as of this morning, we have been seeing errors for simple open graph queries for valid users.
For example: https://graph.facebook.com/833150354
Returns:
{
"error": {
"type": "OAuthException",
"message": "An unknown error has occurred."
}
}
But, the user is valid:
http://www.facebook.com/profile.php?id=833150354
It looks like at least one other person has run into this: http://bugs.developers.facebook.net/show_bug.cgi?id=20490
Has anyone else seen this behavior and, if so, found a work around? Thanks!
Experienced the same error with 2 of our app's users today. Their OG representation throws the error, but their regular FB profile works fine. Sounds like an OpenGraph bug, not sure of any possible workaround :\
Sometime between 7:50 and 8:50 PM EST on 9/13, this problem went away for us. All the other cases I've seen shared also appear to work now.
Love that Facebook never acknowledged the issue in any way I could find even though it was broken for 5 days.
I get the "unknown error" all the time, when I query the graph using the application's token. When I have the current user's token, that works. But the application token fails.
(The app's token worked before the oauth upgrade, BTW.)