OAuthException (#368) The action attempted has been deemed abusive or is otherwise disallowed

前端 未结 4 6819
情歌与酒
情歌与酒 2021-02-20 15:53

I\'m trying to post a feed on my wall or on the wall on some of my friends using Graph API. I gave all permissions that this application needs, allow them when i make the reques

相关标签:
4条回答
  • 2021-02-20 16:15

    Just in case anyone is still struggling with this, the problem occurs when you put URLs or "action links" that are not in your own app domain, if you really need to post to an extarnal page, you'll have to post to your app first, then redirect from there using a script or something. hope that helps.

    also it's better in my opinion to use HTTPS links, as sometimes i've seen a behaviour where http links would be rejected, but that's intermittent.

    0 讨论(0)
  • 2021-02-20 16:16

    I started noticing that recently as well when running my unit tests. One of the tests I run is submitting a link that I know Facebook has blocked to verify that I handle the error correctly. I used to get this error:

    Warning: This Message Contains Blocked Content: Some content in this message has been reported as abusive by Facebook...

    But starting on July 4th, I started receiving this error instead:

    (#368) The action attempted has been deemed abusive or is otherwise disallowed'

    Both errors indicate that Facebook doesn't like what you're publishing.

    0 讨论(0)
  • 2021-02-20 16:17

    Had the same problem. I figured out that Facebook was refusing my shortlinks, which makes me a bit mad...but I get the point because its possible that shortlinks can be used to promote malicious content...so if you have shortlinks as part of your test, replace them w the full url...

    0 讨论(0)
  • 2021-02-20 16:40

    I believe this message is encountered for one of the two reasons :

    1. Your post contains malicious links
    2. You are trying to make a POST request over a non-https connection.

    The second one is not confirmed but I have seen that behavior. While same code in my heroku hosted app worked fine, it gave this #368 error on my 000webhost hosted .tk domain which wasn't secured by SSL

    0 讨论(0)
提交回复
热议问题