Yesterday I received in one of my Facebook apps this message:
Tried to look for documentation about it but couldn't find it. What does it mean? I can't request READ/WRITE permissions anymore? I must do it sepparately?
As someone cited out in other question, it looks like it is not your fault and you cannot do anything about it.
Quoted from Fabrice Lefloch in what am I going to do with this Facebook alert? about the permissions
It seems that it is a mistake from Facebook developpers.
Someone has asked the same question here, and a facebook engineer answered:
The alert went out by mistake and we are working on cleaning it up. You can ignore it.
Related
I'm trying to link my website to my page but when it's clicked it brings up this error:
Possible problem with this link We have detected that this link:
viqtory.win may be malicious. To keep your account and device secure,
only follow links you trust.
I have an SSL and ran the facebook debugger. All the documentation regarding this questions is from 3 years ago. Is there an updated solution for this problem? Is it because my website ends in a .win?
Found a work around.
Using a bitly link (bitly.com) and posting that seems to do the trick. Still don't understand why my website is being blocked but for the time being this works.
I have a site and wanted to share it into facebook. However, upon posting I got a notification from facebook saying:
The content you're trying to share includes a link that our security
systems detected to be unsafe:
markleobongcasan.com
Please remove this link to continue. If you think you're seeing this
by mistake, please let us know.
I checked into sucuri site check and it is 100% safe.
I checked my site using facebook debugger as what one of their support member suggested and I got this:
http://screencast.com/t/4nTfGhNd0fq2
Anybody here who has the same experience/problem? How did you fix it?
"let us know" is a link. You need to click that link and appeal to Facebook. After that, all you can do is wait.
You can also try asking in the official Facebook Developers group: https://www.facebook.com/groups/fbdevelopers/
...or you could file a bug, because it could be a bug too: https://developers.facebook.com/bugs/
I have done much searching but not able to find a solution.
Trying to get my Twitter to Facebook feed setup but getting this error:
"Facebook reported an error. The error has been reported to our engineering team. Please try again as it might be a temporary problem"
From what I can gather it may have something to do with an old account that has been deleted, but I have no idea how to resolve this and nor do a lot of other people.
First up: this is not a programming question since it's not related to the Twitter API but to the Twitter interface. Therefore, it's actually to be regarded as "Off-Topic".
To give you a helping hand nevertheless:
What you are describing is a known bug Twitter bug. Check https://www.facebook.com/help/community/question/?id=110412992466716 and https://dev.twitter.com/issues/998
The problem comes up when your Twitter account was previously connected to another Facebook account that you deleted/deactivated without removing the Twitter app first. Now that you try to connect to a new Facebook account, Twitter still tries to authorize using the old credentials of that other account.
Currently, your only hope is to ask Twitter to manually remove the old account credentials from your Twitter profile's backend. From what I've been reading, Twitter frequently fails being cooperative in that point... you can only ask and hope someone at Twitter is able and willing to manually correct their bug.
I have created a Facebook application that I don't want to use anymore. I deleted it from my developer account and from the related Facebook page more than a week ago but it still appears in the Facebook search engine.
I know similar questions have been posted, but I have no longer access to the admin of this application, meaning I can't change the user accessibility of the app.
How can I avoid this?
Sounds like a bug by Facebook. You might want to post a bug report here. A solution which might help next time: Switch on the sandbox mode, then delete the app.
Came into the office today to do some more work on my nearly completed Facebook Connect website application.
And i have discovered for some reason, the "onlogin" event of the fb:login button FBML control is no longer getting fired!!?!
To anyone else that has a Facebook Connect FBML app (and using the JavaScript API for authentication), i would advise you test your application to make sure it's still working.
A friend of mine's app (which is live) has also stopped working as of today.
What's happening is you click on the "Connect to Facebook" button, it shows the FB login dialog, you log in.
Yes, they are being logged in to Facebook correctly (thankfully), but the "onlogin" callback event is not getting fired anymore, so the page just sits there (where before the "onlogin" event would redirect to the homepage, for example).
Of course if you refresh, you are logged into Facebook.
Seriously, WTF - what have those developers at Facebook done now?!?!.
Any ideas? Has anyone read any updates/threads on this issue?
UPDATE:
8 hours and still no fix in place. I've tried to do some workarounds (there is also an onclick event of the FBML Login Button), but it's all too early in the authentication cycle.
We need to be able to hook into a post-login callback to do things like redirects, permission popups, authentication logic, etc.
Nothing we can do without Facebook fixing this.
I just hope when i come in the office tomorrow this will be 'magically' fixed, much like this issue 'magically' appeared.
Well judging by the comments here i'm not alone. It's obvious at this point that Facebook have made a change somewhere, without telling us.
I just hope they rectify this issue ASAP as there is no workaround i can see for this.
UPDATE 2
Yep - (drum roll), its yet ANOTHER bug from that team of world-class developers at Facebook: (thanks Anon for finding link) http://bugs.developers.facebook.com/show_bug.cgi?id=11733
I love it how the comment from the FB guy Marc says "Only seems to be happening on old Facebook Javascript SDK", well, enable us to do server-side authentication with your Graph API (instead of just for retrieving user details/posting), and we wont have to use the old JavaScript API!
Fun and games.
FINAL UPDATE
Facebook have (seemingly) fixed this.
Let's hope it stays fixed.
Given the 'correct' answer to Anon (as he found the link).
Please confirm and vote on this bug... this should be fixed asap!!
http://bugs.developers.facebook.com/show_bug.cgi?id=11733
if in FB.getLoginStatus you are passing second parameter as true, pls make it to false.
I resolved callback issue using this trick.
Thx
This is a bug and they are about to fix it