I have a app with some permissions that only exist on API V1.0 (I'm working on migrating them to V2.2),
but in the meantime I need a new permission "publish_actions". If I send a review to Facebook I can still use the API V1.0 permissions or I can't? how can keep my permissions "read_stream" of API V1.0 and add a new one?
Best,
You send in specific permissions, so you can just send in publish_actions without read_stream and it should be no problem. Just keep in mind that you will lose access to read_stream completely after April 2015. I assume you know that it will only get approved for platforms without a Facebook client.
Related
I'm trying to make an app that will allow blog posts from my website to be published to a Facebook page which I am the admin of.
Obviously I need the publish_pages and manage_pages permission to do this and I need to provide a screencast showing how these permissions will be used.
From my understanding, I can still publish a post from my website to my Facebook page while the app is in development mode as long as I am the admin of the page (which I am) but the posts won't be visible to the public.
So I complete the authentication process here (see below).
Finally I add my blog post. However, I then get the following as an error message
"(#200) The permission(s) publish_actions are not available. It has been deprecated. If you want to provide a way for your app users to share content to Facebook, we encourage you to use our Sharing products instead."
Would this be an issue with the system I am using, making a depreciated API call?
Deprecation:
The publish_actions permission will be deprecated. This permission granted apps access to publish posts to Facebook as the logged in user. Apps created from today onwards will not have access to this permission. Apps created before today that have been previously approved to request publish_actions can continue to do so until August 1, 2018. No further apps will be approved to use publish_actions via app review. Developers currently utilizing publish_actions are encouraged to switch to Facebook's Share dialogs for web, iOS and Android.
From now on you can only publish to your own facebook profile not facebook page. For more information you can visit their official documentation
I'm working on a notification web-app that has a Post-to-Facebook feature. Until the (Graph) API v2.0, it worked great. A user would authenticate with their Facebook account, put their token into our app, and we'd use that to make posts to their wall/page for them when a new notification was sent.
We have applied for the permissions we need to use on Facebook's new API (publish_pages, publish_actions, manage_pages). We received a notice that our application was rejected, so we re-worded the same application for permissions to try to clarify what we use the permissions for, resubmitted it, but have been rejected again.
An app that does almost exactly the same thing we hope to do was granted these permissions (we know, because we both work with- and compete with- that app). Until we found out that that app can still publish posts to Facebook, we believed that all requests to repost/automatically post on users' behalfs were being denied because of a Facebook policy change.
We can't figure out who to contact or where to appeal the denial of these permissions. This probably isn't the right forum (since this isn't specifically a technical question about the API), but I can't see where to take this issue next.
Did you have a look at the Login Review FAQs:
https://developers.facebook.com/docs/facebook-login/review/faqs
or otherwise refer to
https://www.facebook.com/groups/fbdevelopers
In an Unity Game, i use the facebook scores api, so i need the publish_actions permission (https://developers.facebook.com/docs/games/scores).
Despite of i tested my functionality and made requests with test users and real users, when i go to submit to review the app in order to get approved the permission, i have an issue, "it looks like you haven't made any API requests to publish content with the publish_actions permission...", so i can't submit to review de app on facebook.
Somebody have any idea? i only use publish_actions for score managements.
Thanks
it looks like you haven't made any API requests to publish content with the publish_actions permission...
They telling you did not made any API call with that permission. But by telling your steps seems you did API call, so Just try again. Make sure you are passing the publish_action while requesting access token.
I created facebook app for my website & To enriches the user's experience i need extended permissions from facebook for my app ( which includes read_stream with some other permission ) , i have submitted the app for reviews with valid description but submission were not approved and i could not find any valid reason for that.
I noticed this description in read_stream -- Android and iOS apps will not be approved for this permission. In addition, Web, Desktop, in-car and TV apps will not be granted this permission. , can you please explain meaning of this ?
Here is my reference site - https://hootsuite.com/ , they are using read_stream as well.
Hootsuite is using a v1.0 App created before v2.0 was introduced. It will stop working for them after April 2015, when they have to go through the review process too. You will not get read_stream approved for your website, as you can read in the quote you posted.
Meaning, you can only use read_stream in an App created before end of April 2014, and only until end of April 2015. Not worth using it anymore imho.
It's all in the docs:
https://developers.facebook.com/docs/facebook-login/permissions/v2.2#reference-read_stream
This permission is granted to apps building a Facebook-branded client on platforms where Facebook is not already available. For example, Android and iOS apps will not be approved for this permission. In addition, Web, Desktop, in-car and TV apps will not be granted this permission.
So, I strongly doubt that you'll receive this permission during app review.
Now someone can use "user_posts" permission - This new permission allows an app to access the posts on a person's Timeline. This includes the someone's own posts, posts they are tagged in and posts other people make on their Timeline.
This is a useful alternative to News Feeds.
Previously, this content was accessible with the read_stream permission. The user_posts permission is automatically granted to anyone who previously had read_stream permission.
Facebook Platform Changelog
Getting some conflicting information from Facebook currently on whether or not the read_stream permission is actually deprecated for non-Facebook branded apps moving forward. I know recently the change was made to require app-specific access tokens for read-stream permissions.
In the Facebook graph explorer it looks as though my existing application which was already granted an app-specific access token for the read_stream persmission is still providing access to the [user-id]/posts endpoint, although I also noticed that searching for this endpoint in the reference takes you now to [user-id]/feed, which also requires the read_stream permission.
When searching the read_stream permission in the reference however, it now reads:
This permission is granted to apps building a Facebook-branded client on platforms where Facebook is not already available. For example, Android and iOS apps will not be approved for this permission. In addition, Web, Desktop and TV apps will not be granted this permission.
Blockquote
Wondering if anyone from Facebook or outside can actually confirm that this endpoint is now closed to 3rd-party apps, and if there is any explanation whatsoever for why?
Now someone can use "user_posts" permission - This new permission allows an app to access the posts on a person's Timeline. This includes the someone's own posts, posts they are tagged in and posts other people make on their Timeline.
This is a useful alternative to News Feeds.
Previously, this content was accessible with the read_stream permission. The user_posts permission is automatically granted to anyone who previously had read_stream permission.
Facebook Platform Changelog