You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"In March, we're making a security update to your app settings that will invalidate calls from URIs not listed in the Valid OAuth redirect URIs field below.This update comes in response to malicious activity we saw on our platform, and we want to protect your app or website by requiring a new strict mode for redirect URIs. Learn More"
The text was updated successfully, but these errors were encountered:
The purpose behind making your app public in the "App Review" tab is so that other people can see content that you've posted via the app.
I authenticated an app without setting it public, and @Moogert has confirmed that he can't view a post that I published with facebook-cli to my timeline with the app in development mode.
I'd like to investigate this a little further, but if we can't find a way to authenticate an app that can effectively publish content, then I might officially deprecate the content publishing functionality, namely post, postlink and postvideo.
Any help documenting and/or overcoming this roadblock would be greatly appreciated.
It looks like you can use a policy created and hosted somewhere like Free Privacy Policy. I was able to create a policy and authorize my app in a few minutes, pretty handy!
In the App Review tab, when flip the switch, Facebook give me the follow message:
"Invalid Privacy Policy URL
You must provide a valid Privacy Policy URL in order take your app Live. Go to App Details and make sure it is valid."
I put the URL: http://localhost:3333/
In App Details show the message:
"In March, we're making a security update to your app settings that will invalidate calls from URIs not listed in the Valid OAuth redirect URIs field below.This update comes in response to malicious activity we saw on our platform, and we want to protect your app or website by requiring a new strict mode for redirect URIs. Learn More"
The text was updated successfully, but these errors were encountered: