I'm using Shopify and I'm getting the following FB Pixel error on the browser console once the page loads:
[fbpixel] 599676484375870 is unavailable. Go to Events Manager to learn more error.
When I look at the Pixel in the Facebook Events Manager, I don't see any warnings or errors associated with this pixel. Has anyone encountered this error message before?
Related
I am getting developer alerts for Facebook api GET /picture is Unavailable in this version error from last week.
Still not able to understand what does it mean?
There are not many details of what's failing or from which platform it's affecting. I have many platforms(android, kindle, iOS, facebook) for the app.
I checked GET /picture is working good for facebook API for current platforms. Where it could be failing?
Is GET /picture deprecated for any version?
Anyone is getting this type of error?
https://developers.facebook.com/docs/apps/changelog#v2_3_changes:
Picture Error - For the Link, Post, Thread, Comment, Status, and AppRequest nodes, and other nodes which don't have a picture, the /v2.3/{object}/picture edge now returns an error message. Before, the API returned a placeholder image of a 'question mark' for the picture edge requested on these nodes.
Sounds like you are requesting /picture on a node type that doesn’t have this edge.
I'm following the tutorial for Publishing using the Share Dialog on the Custom Stories in iOS section.
https://developers.facebook.com/docs/ios/open-graph
When I want it too, it switches to the Facebook App, the Graph Object is presented to the user (image, title etc) for a few seconds and then disappears and Post button greys out. If I tap the Post button before it greys out, I get an error message logged:
Error publishing story: Error Domain=com.facebook.Facebook.platform Code=102
"The operation couldn’t be completed. (com.facebook.Facebook.platform error 102.)"
UserInfo=0x16d48640 {error_code=102, app_id=1435110413425124,
error_message=An error occurred during publishing.}
FYI, the standard share dialogue presentShareDialogWithLink:handler: is working fine and letting me post - it's just when I present one with a Graph Object attached to it.
I would post sample code, but it'm using the same code that's in the tutorial above. Besides, I'm pretty sure this is to do with settings in the App Dashboard, not the code I'm writing.
Per this question on Stack Overflow Facebook SDK - iOS - Fail to share URL (Error 102), I've confirmed that:
My App's Settings are set correctly in App Dashboard (including iPhone Store ID and Bundle ID)
By info.plist file is configured correctly.
This question facebook error code 102 with sdk 3.6 suggested using a real Facebook user who was an administrator of the app. I tried that, but the problem still occurred for me.
I also tried it with the App published, and with it unpublished and there was no difference.
I'm wondering if anyone else has any ideas for things I haven't checked yet?
I'm a numpty.
Despite the fact I said I'd checked the settings were correct in App Dashboard, I had misspelt the Namepsace.
If your Facebook app status is "development and unavailable to the public" will caused same result.
You may want to change it to public under "App Review" on the Facebook app menu. Or you need to login Facebook as role "Administrators", "Developers" or "Testers"
When I share my facebook Canvas App's link on my wall, I see the app image fine but then in the app description area I get Fatal Error: Uncaught OAuthException: An active access token must be used to query information about the current user...
Also when I debug the link the debugger says it's valid but when I try the Scraped URL I get the same error.
I understand that because I query the user in the index page of my app I get this error but how can I make facebook scraper to not give me this error.
The canvas app link is :
https://apps.facebook.com/warriorofnemesis
Thanks in advance.
I found the reason and I will answer my own question, in case somebody else faces the same problem. The reason I see this Oauth error message was , because the display_errors setting was set to true in my script. I had done it to find a error on my page and forgot that I had this setting True. After I turned it off , now it works ok.
I've been having issues recently with setting up links between Facebook and a website I've developed - www.newcarpromotions.co.uk. After some digging around, and advise on this forum, Ive used the following link to see what Facebook thinks of my domain:-
http://developers.facebook.com/tools/debug/og/object?q=newcarpromotions.co.uk
What it returns is as follows:-
"Error Parsing URL Error parsing input URL, no data was scraped"
Now Ive tried all my other domains which return all the correct information as you would expect.
Has anyone seen this before? It looks like Facebook doesn't think my domain exists! If that's the case any idea how I can get this resolved?
Nick
According to this post (Linter gives "Error parsing URL" error) it seems that the facebook object debugger can return that error if it fails to parse your page somehow. I'm suggesting that facebook can get to your website but is failing for a different reason. You may want to look at your request logs to verify that facebook is hitting your site.
If worse comes to worse you can open a bug here: http://bugs.developers.facebook.net/
I'm doing a facebook application for (WAP based)mobile browser. I need to show the post dialog. When i use the following code for wall post it show error.
http://m.facebook.com/dialog/feed?app_id='.$app_id.'&redirect_uri=$redirect_url&display=wap
The error is:
API ERROR CODE:3
API Error Description: Unknown Method
Error Message: This method isn't supported for this display type
While I give display type as 'touch' in the above mentioned URL it works fine in the touch devices. But no form displayed in the wap browser.
That's strange, because their documentation does mention that is the method to do it: http://developers.facebook.com/docs/reference/dialogs/
I notice an error in your PHP though (unclosed apostrophe):
It should be:
'http://m.facebook.com/dialog/feed?app_id='.$app_id.'&redirect_uri='.$redirect_url.'&display=wap'
Here is a similar issue on https://github.com/facebook/facebook-android-sdk/issues/177
Also, check out facebook's bug tracker: http://bugs.developers.facebook.net and perhaps file your bug there and then link to it from here.