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).
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.
While trying to submit an OpenGraph action to Facebook, the feedback we receive states that we should use mention tagging instead of action tagging:
The Action Tagging additional property can only be used when the tagged user is also performing the real action. Otherwise use the Mention Tagging additional property to include another user in the story.
But in our instructions on how to reproduce the action, we clearly state we implement "mention tagging", and as far as I can tell, the app complies with the requirements as listed in the documentation.
What could cause FB to believe we use action tagging instead of mention tagging?
Is there a way to receive more specific information on the failed submission?
I had the same problem and it was a pain in the backside for weeks as I kept resubmitting my open graph action for approval and it was continually rejected. My solution was to:
a) update the description to ensure that I made it clear that the app was using mention tagging rather than action tagging.
b) I used a timeline screenshot that clearly showed the words "FB friend" was mentioned in your profile (where "FB friend" is the name of the friend you have chosen for the mention tag).
As Facebook doesn't actually review and approve the iOS app, its reviewers can only go on the description and screenshots you provide. So, if it's not getting through, you need to make it absolutely clear in idiot-proof steps, exactly what your app does. If you continue to get rejections, ask the reviewers for help within the submission text - sometimes that gets a better response that will help direct you!
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.
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.