When debugging a website with a Like button here:
https://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fwww.arcosjapan.com%2Fscroll%2Fcaresox-hc.html
It throws a critical error:
"You must preload this data. TAAL[BLAME_file]".
I have installed hundreds of like buttons and have never run across this. Does anybody know what it means? I am aware of the other issue that it is pointing out on that page: "The app ID specified within the "fb:app_id" meta tag is not allowed on this domain." and I am pretty sure that is not the issue as my app is correctly configured.
Facebook Debugger is broken every once in a while. Now it seems to be working again. It gave the same error message just a couple of days ago.
Related
Some Time ago our users reported problems with sharing content from our page (text/image wouldn't show up in the share dialog), after some research we added the og:image:width and og:image:height-tags. To reduce loading time, the facebook-scraper receives the page with an empty <body> (we had troubles with timeout too).
Everything worked great until about a week ago. Pages that have already been scraped showed errors in the Object-Debugger:
Error parsing input URL, no data was cached, or no data was scraped.
This error shows up nearly everytime i click Show existing scrape information, eventually it would go away (without re-scraping the page) but then following error shows up:
The 'og:type' property is required, but not present.
The Sharing-Debugger additionally shows following error:
The parser's result for this metadata did not match the input metadata. Likely, this was
caused by the data being ordered in an unexpected way, multiple values being given for a
property only expecting a single value, or property values for a given property being
mismatched. Here are the input properties that were not seen in the parsed result:
'fb:admins, og:type, og:description, og:title, og:site_name, og:image:url, og:image:width,
og:image:height'
Sometimes it also says that our images are too big and couldnt be downloaded, but the image is shown in the preview. Sometimes it even goes as far as showing
Could not scrape URL because it has been blocked
What doesnt add up here is that if i click on See exactly what our scraper sees for your URL it shows me the source of our page with empty <body> and <og:...>-tags in the <head>
The debugger shows me the correct og:url, og:type, og:title, og:description and og:image, the preview is alright, response code is 206 and last scraping was somewhere in August.
After rescraping a few times, most of the time the error messages are gone, but that cant be the solution. It seems as if the debugger sends random errors for whatever reason
So what do these error messages really mean? Are they wrong? What am i missing here?
(Note: a 3rd pary is having trouble sharing our pages in their application due to those error messages, everytime they appeared in the debugger, their data seems to be somehow broken)
After some back and forth with one of facebooks supporter in the developer forum, they acknowledged my problem as a bug and assigned a team for further investigation. However, a few days later my bug report was closed with following message:
Those messages are due to a bug in our Debugger when you scrape no-canonical URLs. On that case, the information about your URL is updated asynchronously so it takes a little while for the error messages to go away.
If you input the canonical URL in the debugger, the error messages will go away after the first scrape.
Unfortunately, due to the way our systems works, we are not planning to fix that error in the near future.
Last week suddenly the XFBML login button stopped working on our site. Instead of showing a nice FB login button, it just shows the button text. In Firebug, I'm getting an error:
TypeError: k.root is null
Strangely, the problem occurs on our production environment, test environment and my own development environment. The production environment hasn't been updated or changed for quite some time so it's not code changes on our end. All three environments also connect to separate Facebook apps, each with a different appID, so it also can't be a (accidental) configuration error with the Facebook app.
Does anyone know if it's perhaps possible that this is an issue on Facebook's end? They did do a compatibility breaking update on 5th of September, but as far as I can see, the changes are not related to the login button.
Anyone know what could possibly cause this?
This was a bug that would occur if you called FB.init prior to document.body being defined, (as in the HEAD), this has now been resolved.
I started to face this issue last week as well. I managed to solve with one of the options below:
1) The app's 'App Domains' was misconfigured (it should be a domain name and not a full URL):
Source: https://developers.facebook.com/bugs/225729134220754
or
2) Just replace the div (containing class fb-login-button) with a regular button to call FB.login, and all the things will start to work again.
This question is similar to: Facebook Error 191 on canvas app using FB.ui() for the 'feed' dialog (worked before, stopped working last week) which was never answered.
Starting today, after the user likes the page and enters the contest, the share dialog which presented itself stopped working and gave:
API Error Code: 191
API Error Description: The specified URL is not owned by the application
Error Message: redirect_uri is not owned by the application.
when logged in as an admin and just an error occurred for other users. This tab has been running well for a while now. I have confirmed it with an associate of mine. They did make a change to another part of the app (yesterday and today) but the sharing was still working until this afternoon. They did not change the part that generates the dialog.
The tab is: https://www.facebook.com/MedjoolDates/app_355398587864294
Anyone have any insight? Feel free to use 'cancel' rather than sharing and fake data to sign up, then unlike the page if you wish.
Thanks in advance.
David
Same problem here, there is a bug posted on Facebook Developes here:
https://developers.facebook.com/bugs/273845842724431
Can't help much without seeing your code.
One thing to check, make sure your redirection_uri is exactly as your domain registered with FB and that you include a trailing / ie http://www.myurl.com/ rather than http://www.myurl.com
I can't answer why it changed, but I had that error fixed by the above change before.
I am having the same issue. Am developing a new app with FB.ui feed functionality, which worked OK yesterday and today it gives the same error as OP.
Went back and checked an > 1 year old app with the same functionality; same error. I cannot see any other solution, than the FB dev team has changed something and not given notice.
I have since two days trouble with a normal login/oauth(orization) via a facebook application.
It behaves as like the app never left Sandbox Mode (which is disabled):
Login Fails for (alot/some/not all) normal users however there's no problem for the page admins, developers etc. to authorize.
There's an error at the oauth page of facebook, not very helpful:
"An error occurred. Please try again later."
I made a stupid test app, that really does not much:
The app at facebook:
http://apps.facebook.com/mygeneraltesting/
The URL of the iframe (no https there): (I'm restricted to two urls in one post, so see it as a comment)
The minimal possible (IMHO) URL to the Oauth dialog:
(I'm restricted to two urls in one post, so see it as a comment)
It really seems like the error is caused by facebook, but it is hard to find someone else with this problem online. So I'd like to ask:
Is anyone else seeing the error message from above?
Is anybody out there with the same problems on their app?
If you like to make a code review, (see: http://graphicore.de/downloads/generaltesting.tar.gz ) is there anything suspicious?
Thanks alot, Lasse
(the German errror message for search the engines: "Es ist ein Fehler aufgetreten. Bitte versuche es später noch einmal.")
This question is very dated now. The answer is: Facebook made something wrong. The same code worked on another app created some time later (I don't even remember how much later) but never worked on that app, AFAIK. So it was just a broken app on facebook side.
I added a like button to my site pages. It seems to work, but the debugger is giving me errors. When I try out the URL in the Object Debugger it gives the error below:
Object Base Domain Not Allowed Object at URL 'http://www.gdiy.com/projects/visiting-paris/index.php' of type 'website' is invalid because the domain 'www.gdiy.com' is not allowed for the specified application id '279134608772109'.
When I try adding the domain name in the facebook developer apps settings (https://developers.facebook.com/apps/) it is not sticking.
I enter "gdiy.com" as the domain and press enter -> then save. If I refresh the page now the domain doesn't exist anymore.
Debugger results page:
http://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fwww.gdiy.com%2Fprojects%2Fvisiting-paris%2Findex.php
What's wrong here? I even tried "www.gdiy.com" and that didn't work either. I also waited a couple hours before trying.
I was having the same issue. I waited a day, came back, and it seemed to be fixed. I'm not sure if this was a Facebook bug that they fixed, or if there was something else weird going on. However, time seemed to do the trick this time.
I use Chrome and doesn't work, and I try with Firefox and work it!