I'm trying to get publish_actions permissions approved for an iPhone app and been denied twice. The first time was because, as the policy says not to, we were populating the message parameter automatically when posting to the user's wall using the graph api. So we removed the message field entirely and kept only the link parameter.
The app was rejected again with the same message so I figured I'd try to get a definitive answer here before I get three strikes on app submission.
Both the 2.3 platform policy video and written policy explicitly say do not pre-fill the message parameter but say nothing about the link parameter. Beyond simply not pre-filling any of the message parameter must we also provide a way for the user to enter a message? If so that is not clear in the policy.
Graph Api Publish Documentation:
https://developers.facebook.com/docs/graph-api/reference/v2.1/user/feed#publish
"Pre-fill" Video: https://developers.facebook.com/docs/apps/review/prefill
I was rejected three times with the same response - which was you can not pre-populate the message field. But with the second and third submission, I was not pre-populating the message field. Of course I was expecting the Facebook reviewer to operate the application according to my instructions to see this. They don't, and the refusal was because they could not tell from my submission that this was the case. The response they give is not hand typed, but a stamped response given when they click "REFUSE!".
The solution is not only to get the application to behave according to policy, but to provide clear pictures with the step by step instructions of how your application shows the user the post, allows for the user to input a message, and the finished post on his time line.
Related
We are having many users signing in (oauth) reporting issues where they email is not valid. Problem is that they do not have an existing account, but message displayed is very confusing.
It should do the following:
Instead of "The email cannot be recognized by Uber", it should have a clearer message that there is no account associated with their email.
Automatically redirect to sign up
Thanks for the improvement tip - we may consider it as a future request. However, this question is not relevant to SO - please use in the future Uber google groups (https://groups.google.com/forum/#!forum/uber-developers) or send post's on Twitter at #UberDevelopers or #Uber_Support.
I am following tutorial from https://github.com/jw84/messenger-bot-tutorial
I am getting this message "The Default answer block is your bot’s default response to any input from a user. Create messages in this block that will guide your users. You can add buttons that lead users to other blocks. Remember, you also can use “AI Setup” to choose what blocks to show based on users' input." everytime I write anything random in messenger
This response is generated automatically by chatfuel. Check to see if you have linked chatfuel to your bot. If you intentionally used chatfuel you can change its default response from the dashboard. If you were like me, I setup chatfuel initially but decided it wasn't robust enough for what I wanted to do, and then I used Howdy botkit, but the chatfuel ai was still linked so I got the chatfuel default message + howdy botkit responses. I had to delete the chatfuel link so that I could only get responses from Howdy.
I would need to write a script in order to automate this task:
Monitor new likes on a Facebook Page periodically.
When a new like is detected, identify the person who gave it
Send them a private message, thanking them and pointing them to additional resources that may be of their interest.
Would this be feasible using the Facebook API? The documentation strikes me as a little unwelcoming for the casual observer, and I'm not sure whether this is impossible or it's just that I haven't dived deep enough. Are the three steps above doable using the API?
You can use a cron job to get the number of likes of a Page with the /page-id endpoint.
You can´t get the fans of a Page with the API, and you can´t get the "last liker" either.
Auto-sending and message prefilling is not allowed (it would be spam anyway), and you can only reply to use messages as a Page. You can´t initiate a conversation.
While coding I have started wondering if there is a possibility to perform an action before the actual request is send.
For example I have a code:
FB.ui({method: 'apprequests',
title: 'The Challenge Game!',
message: 'I challenge you!',
}, challengeCallback);
And I would like my user to be able to challenge a friend only once - that means, If a challenge exists in DB connecting two users, there should not be another challenge created until the first one is finished or expired.
So between picking friends and sending requests there should be a function call.
However I know, that I won't get users fb_id before the request is actually send.
I can always prompt my user, after choosing friends, that the challenge for that particular person already exists and is pending. But what happens to request that is waiting for the challenged in his/hers inbox?
Is there something I can do not being made to create my own friend picker? Maybe alter FB.ui somehow?
When you look at the description of the Requests dialog, you’ll notice the parameter exclude_ids, by which you can specify user ids that will be excluded from the multi-friend selector.
So if you look up in your database which of their friends your user has already send a request to, you can put those ids in there.
Only cave-at: This parameter is not supported on mobile devices; so if you are targeting those, you might have to look for another solution (which would be most likely to create your own multi-friend selector) – but I’m not sure right now whether this restriction only applies to native mobile apps; maybe when using the JS SDK in a web-app it’ll work on those as well (the wording in the docs is not totally clear on that).
My action was approved with Action Tagging. However after some time, I got a message that action tagging is not valid for my app and to consider using mention tagging. Currently the status is:
Approval Status: Available to users (changes needed) This Action Type
is available to all users, but your most recent submission needs
changes.
Capabilities Status:
User Messages (Live) - Allow users to write a personalized message attached to this action.
Tags (Needs Change) - Allow users of my app to tag other users for this action.
Explicitly Shared (Live) - This action can specify the user explicitly shared an action.
So I implemented mention tagging, but each time I re-submit, I get the following response:
We are unable to tell which additional properties you are requesting.
Please specify if you are planning to implement action tagging,
mention tagging, or both. If you are requesting mention tagging you
must select both the user message and tags action properties when
submitting your action. If you are requesting both action tagging and
mention tagging we will need to be able to reproduce both action
properties. For further information, please see here:
https://developers.facebook.com/docs/opengraph/submission_criteria/action_properties/#mentiontagging
Of course on resubmitting I explain very clearly that I want mention tagging and I show the steps to reproduce. I also have selected both the user message and tags action properties. It just seems that the testers simply ignore the message I write in the re-submit dialog.
I also puzzles me that the re-submit dialog has only the first step that you type in how to reproduce the action. It lacks the extra edit boxes that the normal submit dialog had the first time where you explained about the additional properties.
Maybe some kind of bug in the resubmit dialog of an already approved action (that needs changes in the additional properties) does not allow me to write the message I need?