I recently got Facebook developer alert that the app is receiving large number of API errors from POST user/external_edge. I looked into facebook developer documentation and tried googling it but I dint any valuable information.
Did anyone face similar problem ?
What permissions might be causing this issue?
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 been trying to send notifications to my users via Graph API.
But I was facing with "An unknown error has occurred." error. There wasn't any further information. I was have SSL, Canvas Page and also Website integration with my App but it didn't worked.
Also Google couldn't help me.
After couple of hours later, I decided to try it with another App. Voila! It worked. And then I started to look differences between them. Finally I found the source of error.
Here:
If this switch is "Yes" then you can't send notifications and get "An unknown error has occurred." error. I think it's because app_secret is not anymore safe if you embedded it in a mobile application. So, if someone reach it, will be able to send notifications to your users.
What is point of this I don't know but this is the solution. If somebody can explain it, I'd be happy.
I know it's kind of repeated but I've looked here and others forums trying to find a reason to this error.
I've found the cause but I really would like to see the explanation in Facebook's API, and other informations for my app about the limits and the limit of time necessary to 'back to normal', but I couldn't find it anywhere.
Do you know where can I find these informations directly on Facebook?
Thanks for your help.
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.
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.