How do you go about testing Facebook's Open Graph API when they don't allow you to? I've created a test app with some actions, to determine whether all of my actions will work correctly, and Facebook have rejected the action with the following message:
Thank you for your Open Graph submission. Please ensure your
submission was intentional and was not created for testing purposes
before resubmitting your action. You may view some guidelines in the
Submission Checklist:
https://developers.facebook.com/docs/opengraph/checklist/ Please make
changes below and re-submit for approval.
You can test all you want, just don't submit it for publishing.
Related
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.
99% sure my app is set up correctly, it requests the publish_actions permission and I can publish the action using the Open Test user as it states I must do, however when I go to review status my submit link isn't active and it just tells me I need to publish the action using the test user......which i've done. Going around in circles here, what am I missing? Or can anyone recommend a decent guide I can follow as the docs aren't helping me too much.
I am currently having a Facebook app which is already deployed in the production. Since, Facebook is going to remove the feature "Post to friend's wall" soon. So that, I have to submit the Open Graph action to Facebook to use Mention Tagging instead.
In the submission period, I have to deploy the new website and wait Facebook to review it.
The problem is:
During the time that I am waiting Facebook to approve the action, other users in my website will not be allowed to use mention tagging.
Since the site URL of Facebook App can be only one (which is now pointing to production). So I couldn't deploy the testing stage to another URL and point the site URL to it.
What should I do? Thanks.
Set the App-Domain to "yourapp.com".
Now have the regular, live app at www.yourapp.com or whatever, and put the new version, which is to be approved, at beta.yourapp.com. When submitting the action, point to the beta.yourapp.com-URL - the platform-team will follow your links.
The bottom line: setting the App-Domain allows you to run the app on a domain wildcard, *.yourapp.com.
My request for approval for a custom open graph like action keeps getting rejected without any specific reason as to why it has been rejected:
Your Action failed the criteria: We are unable to test this action
according to the usage instructions you provided. Pleas ensure the
steps you list are ones that a user must take in order to trigger the
action once the action goes live. Please provide thorough reproduction
instructions and link(s) to a specific URL where we can trigger the
action. You should also test your action to ensure you can
successfully publish actions back to the timeline of the test user
named Auth Dialog Preview User. Once you have made these changes,
re-submit your action.
I've supplied absolute idiot-proof instructions for testing the functionality and even tested them twice using the Open Graph Tester user for the app. I have honestly no idea what to change to get approved. Any ideas?
I'm also not sure what the following parts means for a pure AJAX application like mine:
Please provide thorough reproduction instructions and link(s) to a
specific URL where we can trigger the action.
Does that mean the Facebook testers do not want to test the action using the User Interface of the Application but want to fire a http request at an URL which will obviously not work for a pure AJAX app.
Facebook does not approve custom like actions any longer. Facebook recently introduced the "Built-in Like" as a built-in Open Graph action (see blogpost and documentation).
Is it possible that although I haven't submitted yet my open graph's actions to Facebook, the actions are being seen by users which are not developers/administrators?
If your application is in sandbox mode it can only seen by developers,tester etc...
But if sandbox mode disabled it can be seen by anybody who knows the url. The only difference is if your open graph objects and actions aren't submitted. They can't use them it will give error.