New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extended permissions not working #7
Comments
Can you provide some specifics? What parameters are you trying to use in the authorize method? |
I am running into the same issue, while trying to run the FacebookSDK Example application |
i tried it with the permissions in the example (publish_stream and offline_access). i tried it with various parameters but it was only working with none. |
I had tried running the FacebookSDK example, a few hours ago. I still ran into the same issue with Extended Permissions. I am using the correct APP_ID of an application that I have registered with Facebook. Is there any other attribute that needs to be setup besides APP_ID? Thanks. |
Are the following 2 issues related to this particular issue.
Please let me know. Thanks. |
The "an invalid next or cancel parameter was specified" error can be fixed by migrating your application to the New Data Permissions. This can be done by going to http://www.facebook.com/developers/apps.php then select the application you are testing with, and click "Edit Settings" (the third item underneath Total Users) On the settings page, click on Migrations (bottom of the left menu), then set New Data Permissions to "Enabled". Let me know if you still have trouble. |
Awesome...it works. Thanks a lot for helping me out of the Facebook maze. |
yes thx a lot this worked for me aswell! |
I don't have "New Data Permission" option? I only have "JSON Encoding Empty Arrays", "Stream post URL security" and "Canvas Session Parameter" 3 options. Any pointer? |
Android 4.11.0
I'm getting "an invalid next or cancel parameter was specified" when I try to get extended permissions. When I only use the authorization without any parameters it works. This also happens in the example app.
The text was updated successfully, but these errors were encountered: