How to remove permissions offline_access and publish_stream in scope variable - facebook

I have error when I want login drupal 7 with facebook account and I use module hybridauth.
like this:
Invalid Scopes: offline_access, publish_stream. This message is only shown to developers. Users of your app will ignore these permissions if present. Please read the documentation for valid permissions at: https://developers.facebook.com/docs/facebook-login/permissions
From same question I found the answer and it is to remove permissions offline_access and publish_stream in scope variable but I don't understand how to do that?
anyone can help me?

The permissions offline_access and publish_stream are deprecated, thus cannot be requested anymore.
publish_stream can be replaced by publish_actions, offline_access is gone.
See
https://developers.facebook.com/docs/facebook-login/permissions/v2.4#reference
https://developers.facebook.com/docs/apps/changelog

If you have following Url request while login with Facebook authentication (1). Then you have to remove last parameter you are sending and try following url (2) request hope it will works.
https://www.facebook.com/dialog/oauth?client_id=113006002193070&redirect_uri=http%3A%2F%2Fyougagged.com%2Findex&scope=email%2C+offline_access (1)
https://www.facebook.com/dialog/oauth?client_id=113006002193070&redirect_uri=http%3A%2F%2Fyougagged.com%2Findex (2)

Related

Facebook api, business_management is invalid scope? Why?

I recently added business_management to our list of application scopes. Now when I go through the auth process I get the following error.
Invalid Scopes: business_management. This message is only shown to
developers. Users of your app will ignore these permissions if
present. Please read the documentation for valid permissions at:
https://developers.facebook.com/docs/facebook-login/permissions
I can't find anywhere any answers why this would be an invalid scope. I assume it's like manage_pages, but are there different requirements or is the auth url different?
This could also be due to your app not having been reviewed and approved for the required permissions. I would advise checking at the URL below:
https://developers.facebook.com/apps/[[appid]]/review-status/
And check if the required permissions have been reviewed and granted.
If they have not, you will continue seeing the above error.

Permissions: manage_pages vs pages_show_list

I'm using v2.5 of the Facebook Graph API.
What's the difference between manage_pages and pages_show_list permissions?
From the docs it seems that you need manage_pages to get a page access token. But I tried and I was able to get it with just the pages_show_list permission.
Is this a bug or am I missing something?
The docs are vague und not complete on this subject. Facebook says they grant pages_show_list to all apps (I can't confirm this, see this question), while manage_pages requires review by Facebook.
One import difference is the way the app is presented to the user. If you request manage_pages, the user will be told that your app wants to manage his/her pages before the user approves.
Besides that, the only difference I found in the docs is the fact that manage_pages combined with publish_pagesallows apps to, well, publish pages.
pages_show_list simply allows you to receive a list of the pages that the requesting user is an admin of.

Facebook v2.1 Obtain access token with permissions

I had a great way of obtaining an access token with the publish_actions, manage_pages, and photo_upload permissions. I followed the manual workflow from Facebook itself.
https://developers.facebook.com/docs/facebook-login/manually-build-a-login-flow/v2.1
I used the scope parameter to set these permissions. The problem only occurred recently when I was only getting access tokens that only had public_profile permission. I don't understand how it could work one week and then not the next.
Any ideas or advice.
Thanks
Ok so after a lot of research it seems that I had the wrong permissions. I ad been developing this application for the past 8 months or so and apparently in that time Facebook has changed the names of its permissions. So if your using a manual OAuth workflow for Facebook please make sure your permissions are valid.

Facebook Alers : Too Many Login Dialog Permissions

I have got this error message from facebook .
Your app asks for 4+ read permissions along with public profile and
friend list. Asking for too many permissions can lower conversion by
as much as 40%. To improve your conversion rate and give people a
great app experience, we recommend that you ask for fewer permissions.
Read our règles élémentaires for more details.
My App ASK For This permissions :
publish_stream, publish_actions, user_groups
So i dont know if i must ignore
publish_stream
permission or not because my app just need to post contents no more things.
You can safely ignore the publish_stream permission as it is already included with the publish_actions permission. Quoting from the blog post about the same issue
publish_actions will now include basic publish_stream permissions (including posting on a user's timeline, posting photos/videos, commenting on and liking content), which will appear on the first Auth Dialog screen. With this change, apps that were previously granted publish_stream do not need to request publish_actions.

Requesting certain extended permissions (read_stream) in facebook login not working

My goal is to have my app be able to read my users stream using the extended permission "read_stream" , however when requesting that permission the dialog doesn't show me having requesting that permission.
I have no trouble requesting the email, or publish_actions permissions, but read_stream is a no go as well as other various extended permissions. Here is an example of what I am using for the facebook login:
https://www.facebook.com/dialog/oauth?scope=publish_actions%2Cread_stream&redirect_uri=http%3A%2F%2Fwww.MYDOMAIN.com%2Fsocialregistration%2Ffacebook%2Fconnect%2F&display=popup&client_id=MYAPPID
Is there another permission I need to request when requesting read_stream ? Is there something I need to change in my facebook app settings specifically for the scope permission request? My goal is to be able to get permission for "read_stream".
Thank you for any input!
The method I describe does work! The issue was that there is a second facebook prompt for the extended permissions that occurs AFTER the initial prompt for permissions.
What is confusing is that facebook shows permissions for email and publish_actions on the first facebook dialog box instead of in a consistant manner for all the extended permissions....but that's facebook's choice!
So hopefully this helps anybody else that was confused like me!