I want to access the Group section of the Facebook API. However, it’s blocked behind requiring App Review. According to FB, I should have a thoroughly tested app before putting it under review?
How am I supposed to have a tested app and be ready for release if I don’t even have the API endpoints? Am I understanding this correctly?
As of right now, if I query anything Group related I get an OAuthException code 1.
https://developers.facebook.com/docs/apps/review/
but we recommend that you begin a submission only after you have thoroughly tested your app in development mode and you are ready for release.
https://developers.facebook.com/docs/graph-api/reference/user/groups/
As of April 4, 2018, this edge returns empty data sets for GET operations unless the calling app has gone through App Review. This applies to GET operations using /me/groups as well. Please see the Groups API section of the Breaking Changes changelog for more information.
Related
I'm developing an app which must interact with Facebook API Graph and also use webhooks to get live updates. Now I'm facing a problem I can't receive a live webhook updates until my app is reviewed and is not in development mode.
I've found a thread on a Fecebook for developers site describing the same problem and it got official answer - it is not possible. Use Test button in app dashboard to test your webhook implementation they said.
The problem is the Test button sends only one predefined data packet for each of possible subscription with predefined set of fields with fake values, but documentation defines much more fields and little to none information about which fields are sent in different situations (i.e. post added, comment deleted, comment edited).
I'm wondering how other devs solving this? May be there are some community driven reference for a different webhook interaction cases or else.
For now I can't find any information on detailed webhook format except official documentation on available fields (but not supported payload shapes).
Our current workflow looks this way:
create test app
implement webhook handler using only documentation
prepare test payload and check it is working
create a screencast of the app functionality using test payloads
go through the review process
when app is approved
make it live and check your implementation against real webhook payloads
You need to create a test app for your existing Facebook app
Once you do this, just accept the permissions for your app and set the webhooks on your own Facebook account.
Since you are an admin of the test app, you will be able to set webhooks on yourself without having to get your app approved.
My code is working properly in dev mode, but I can not get approval to use publish_pages or manage_pages. I keep failing every review.
The problem is that the software is to be ran as a cron job and there's really no user interface. This is for an auction website and we want to post a summary of auctions for the next day in our feed.
For some reason they keep saying:
Your screencast doesn't show how the use of this permission directly improves the user experience in your app. Unfortunately we also weren't able to determine this from testing your app manually
Right now, if I have the app in dev mode the post submits successfully, but only my user account can see them, so I've been having to leave dev mode on, let the app post, and then turn the app live.
This is less than ideal. Is there any 3rd party application that has already been approved I can use to post to our facebook page?
It seems like the magic is making sure to mention "this is a server to server application with no user interface" is all that's required to get your app approved. After doing that, it went through without an issue.
My app needs to post as a user or one their pages. So to my understanding I need these scopes "publish_actions manage_pages publish_pages". It would seem that I need to submit for review to get them. Is it absolutely necessary that I do this or is there some exception to the rule. For example, using an older version of the graph api API, a specfifc SDK (php etc), older version of Oauth, wordpress plugin etc. Just want to make sure I need to before making the effort to go through that process.
Everything you need to know about Login Review can be found in the docs: https://developers.facebook.com/docs/facebook-login/review
Downgrading to an older API version is not possible, the lowest API version is the latest one by the time you created the App. You can´t avoid Login Review by using another API version or SDK, but permissions work without review for everything with a role in the App.
If you want to create an app just for yourself, there is no need for Login Review. If you want to go public with your App, you have to go through Login Review.
I see that Facebook has made a lot of changes in their API and working structure of those for creating the FB application for Web/IOS/Mobile.
I am creating a facebook app with my FB developer account to get the Test App's API secret credentials.
With this app I need to test the feature of Publish_ations (Ex:- Post on pages/wall,sharing),but that feature is not enabled for Test App API.And if we want to enable that then we may have to submit the review with some details.In those details they are asking for the steps to test the feature that we will provide in our Application.They need the snaps of pages where that FB feature will be and ETC of info.And that whole process will take upto 7 days.
I am confused that if my application is in progress and that FB feature we are planning to develope then How should I give the steps to test the Feature on our website before creation of that Feature.
Is there any information that I am missing from FB docs for testing enviornment with Publish Action permission.
Please help me I have already wasted 7 days (Tried the review submission process of FB and they have rejected that because of incomplete application and information)
Thanks in advance!!
You're confused. The login/permissions related things works as it was in v1.0 ; just the difference is that you need to submit for review after the app is ready. But that's the last step.
I think you're using the API for the first time, so you may not be aware how exactly to add the permissions in your app. The permissions are added using the scope parameter in the login code. See the details here..
For example, if you're using the JS SDK-
FB.login(function(response) {
// handle the response
}, {scope: 'email,user_likes'});
similarly its done for the other languages.
After adding the permission the admin/developers/testers of the app can test the application and publish posts; while app is in development mode. And this is just similar how we used to do in v1.0.
When your app is ready (the last step), submit your app for the login review (this step wasn't present in the v1.0, you just needed to make it live). After they approve your app with this permission, you can make your app live and everybody can publish post using your app. That's it.
Here is the notification I just received:
App, is currently using the following deprecated features:
Non-threaded comments. Please see the developer roadmap for more details about this change.
I looked all over the API and the developer roadmap and the settings but found no way to fix this issue. How do I fix this?
My hunch would be that they send out alerts based on the permissions your app uses - my app doesn't interact with any "comments" connections in the graph, but it does have the "publish_stream" and "manage_pages" permissions.
If someone knows otherwise please advise...
I have received the same notification for one of my apps. My app definitely does not read or create comments on Facebook posts or objects (Facebook rolled out the threaded comments Feature in April). Thus Facebook's message is not relevant to every app they send it to.
The change should only affect apps which read or publish comments.
Here is the link to the API documentation about comments:
http://developers.facebook.com/docs/reference/api/Comment/
Look at the settings page, in the "Migrations" section. Enable "July 2013 Breaking Changes" and your notification should have a green sign notifying: Your app, appname, is now compliant with the July 2013 Breaking Changes migration. No further action is required.
Be sure to read the complete roadmap at https://developers.facebook.com/roadmap/.
I have got the following message too:
MyApp, is currently using the following deprecated features:
The 'page_id' field in the checkin FQL table. Please use 'target_id' instead.
The 'version' field in the group FQL Table and on the Graph API.
Non-threaded comments. Please see the developer roadmap for more details about this change.
I am sure that in my case the warning derives from my Graph API Explorer and
my Django test code.
That means that Facebook logs every request sent by your App and send you a warning even if you used deprecated features only once.
Check it out