Hi I try to make the "publish_actions" feature of my web app approved but I cannot get it approved cause facebook approval system keeps asking me to include screenshot of working features.
However, I cannot provide such screenshot because the "publish_actions" feature is not approved yet.
How is it called? A catch 22 or an Chicken-Egg-dilema? Anyways...
Where should I start?
(I already tried with a test user and a developper account, both in live or developper mode)
Thanks to anyone that can help
You can create test users, or add users as "Testers" or above in your App's "Roles" tab in the developer area of Facebook.
If your app is interacting with a test user or any user with an assigned role in your app, it may request permissions that have not been granted yet by Facebook for public use. There's no trick or workaround; just simply request the permissions like you normally would for any other user.
Related
I'm using Facebook api to post news on my page.
The process is as follow :
Edit the news on my website
Put the news on a pool, waiting to be published on my Facebook page
A cron is runing and take one news from the pool and post it on my Facebook page.
I'm not using any Facebook's button, everything is done in the background.
So do I have to make a screencast for Facebook approval ? (If yes I really don't know how to make it)
Someone can help please ?
So do i have to make a screencast for Facebook approval ?
In general, that depends - on whether you are able to grant all necessary permissions, when your app is in “live” mode.
You are going to need manage_pages and publish_pages permissions for this. For newer apps, Facebook does not allow to grant publish_pages any more, when the app is “live”, but the permission has not been approved yet in review - even for users with a role in the app.
So you will need to submit for review and get this approved, otherwise you won’t be able to grant this permission in live mode. (Your app needs to be in live mode; in dev mode all content created through it would only be visible to people with a role in the app, but hidden from normal users - not what you want.)
https://developers.facebook.com/docs/apps/review/server-to-server-apps gives instructions on how to submit an app that does not have a normal, public facing login implementation.
Make sure to describe to them very clearly that this app is not for public use.
I want to use the facebook Login for a school project.
Apart from his/her public profile, I also need to get his/her likes.
The only way facebook lets you do that, is by submitting a review form in which I have to enter information that I don't know. I can't even fill out the URL of my website since I only host it locally.
Is there a way that you can access those permissions without having to submit those review forms for educational purposes?
Thanks.
It's possible to use the extended permissions even without Login Review, but only if
People listed in the Roles section of your App Dashboard - including Admins, Developers and Testers - can grant any permission without review. If only people in these Roles will use your app, you don't need to submit it for Login Review.
See
https://developers.facebook.com/docs/apps/faq#login_review
Is there a way for me to test permissions that are not yet granted to my app by Facebook like the "user_status" permission? I need to test "user_status" for a future app that is not yet in develop since I need to prove that what the client wants is possible.
As long as you are testing with an app admin/tester/developer, everything should work, even if the app didn't pass the facebook Review yet.
See
https://developers.facebook.com/docs/apps/review/login#do-you-need-review
However, in order to help you craft your Facebook Login experience, your app's developers will be able to see, and grant, any permission without requiring review by Facebook.
Note: People who are listed in your app's Roles tab will have access to extended permissions without going through review (e.g. publish_actions or manage_pages). For example, if you use the Facebook Plugin for Wordpress to publish your blog posts to your Facebook Page or Profile, you do not need to submit for review so long as all your publishers are listed in your app's Roles tab.
Also, if you're the developer of an app and are the only person using it, then your app doesn't need to go through review. Since you're the developer, all app capabilities should be available. You will still need to take your app out of developer mode, but you should be able to do that without going through review.
I'm in the early stages of building a complex application that will tie into Facebook to customize a story using a Facebook user's personal information. I've successfully been able to request basic permissions, grab their name, and include it in the story.
I'm at the point now where I'd like to include some of the user's photos as well, but I'm running into problems with permissions. When I try to get an access_token using user_photos, I'm told that:
"The following permissions have not been approved for use and will not be shown to people using [APPNAME]: user_photos. Submit them for review or learn more."
If I have a look at my Facebook app settings page, I'm told the approval process can take up to 7 days and requires screenshots, and instructions how a reviewer can test my implementation of the desired permissions.
I don't understand how this is supposed to work. It seems like a chicken and egg situation. How can I build my application if I don't have permission to access any photos through the API? How can they test and determine if they want to give me permissions if I can't build the app they need to test?
Is there some testing or development mode I'm missing? Is there a test user I can use? I've tried creating a testing/development version of the application and granting permissions with an admin user, and still no dice.
Thanks for any help.
That is just a warning. You can always ask any user that have a role on the app for any permission
Since I created a new (Facebook) App last week, I get an OAuthException whenever I want to comment on a post.
"(OAuthException) (#200) You do not have sufficient to permissions to perform this action".
With the old App, my application works fine.
Now I found out that Facebook has changed the login policy recently. I also found the following remark on https://developers.facebook.com/docs/facebook-login/permissions/v2.0:
"If your app asks for more than than public_profile, email and user_friends it will require review by Facebook before your app can be used by people other than the app's developers".
So if I post with the same account with which I created the App, it should work, right? Only it doesn't...
Remark: if I use the new App with another Facebook-account, I have even less permissions (e.g. cannot access the account's pages). So I have more permissions if I use the same account, but still I cannot post!
I use Graph API via .NET Facebook-Client; my App is a native app (desktop app).
Could someone please tell me how to post with a new App? This is the main use-case of our application! Thank you very much!
Here is a screenshot of what I see instead of the login-screen when I use extended permission "publish_action" instead of "publish_stream"
You must be able to post with your own account since you are the admin of the application. - since only the admins/developers/testers will be able to test the app with the publishing functionality before it gets approved by facebook.
If you still are not able to, you must have not granted the permissions to the app. Things to check-
You are using publish_actions and not publish_stream
Check in your application settings whether or not you can see the publishing permission is granted for that app.
If not granted, go through the login process again and grant the publishing permission (may be by removing the app from settings and then authorizing again OR logout the app and then login again with publish_actions)
Problem solved - it was a stupid typo: I wrote publish_action instead of publish_actions (should be plural)! Thanks again to CBroe who pointed it out in this thread!